"Even more so when you attach any sort of DNS name to it, especially when you use TLS and the certificates, guessing because they end up in a big index that is

"Even more so when you attach any sort of DNS name to it, especially when you use TLS and the certificates, guessing because they end up in a big index that is easily accessible (the "transparency logs")." I have accessed websites that do not use ICANN DNS nor TLS, sometimes on ports other than common ones like 80, 443, etc. The term "website" to me means an IP address from which an operator publishes hypertext (HTML) and responds to HTTP requests But others might define "website" differently On home network for experimentation I create own TLDs in custom root.zone and use non-TLS per packet encryption to serve HTML over UDP instead of TCP The blog post refers to "safe haven" Usually "safe haven" means there is something that one is seeking protection from It is not clear from the blog post what the author believes "the internet" was previously a safe haven from Not to mention the www != the internet It's possible the broader internet, including many "unused" ports between 0-65536, could be a "safe haven" from the web what with "AI bots"