Because it's started showing as closed/unconnectable for me from outside, and I'm not showing any changes or issues at my end.
(Not trying to run a web server from home here in any but the most technical sense; it's for smart home integration, and Alexa skills have to run on the standard https port...)
-c
Celebrate,
I haven't seen any announcements around blocking port 443. the article at https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html outlines what ports are blocked and why.
Hrm. It's very odd, then.
I suspected something was up because I can see the other blocked ports on a quick scan (most ports show up as closed, but the ones Cox blocks generate no response at all to a connection attempt), whereas what I see with this is that 443 is showing up as closed. (Suddenly, after months of successful operation.)
Fiddling with the static NAT mappings on my router, though, other ports work just fine when mapped to the same home-automation endpoint: 442, open and responsive, 444, open and responsive, but 443, nothing.
Thanks,
-c
