Some instances operate on an allowlist rather than just blindly being open, but honestly the number of problem instances is much lower than you might expect. Most are just wide open. Spinning up an instance will cost you some time and a domain, so it's not exactly a zero cost effort.
Honestly I have no idea what "chan" has to do with this, I only know it as the japanese honorific. Edit: Oh, chan like 4chan? That one didn't occur to me.
Via LA told Streaming Media that it contacted unlicensed media companies during 2025 to give them “a window to secure a license” under the previous terms, but the company didn’t go to the trouble of issuing a press release or public announcement, opting instead for direct outreach. Any company that didn’t respond or wasn't contacted now faces the new rate structure as its starting point for negotiations.
First, Wi-Fi keys that protect broadcast frames are improperly managed and can be abused to bypass client isolation. Second, isolation is often only enforced at the MAC or IP layer, but not both. Third, weak synchronization of a client's identity across the network stack allows one to bypass Wi-Fi client isolation at the network layer instead, enabling the interception of uplink and downlink traffic of other clients as well as internal backend devices.
Why are you relying on example.com as a health check? To be really blunt about it, if you're using it then you've misconfigured your stuff.
From their docs:
These web services are provided as best effort, but are not designed to support production applications. While incidental traffic for incorrectly configured applications is expected, please do not design applications that require the example domains to have operating HTTP service.
Oomox