More the DNS and DNSSEC and the like. Whether or not there is actually an HTTP server responding is irrelevant to whether or not those securely point anywhere but a malicious system.
replyYeah there’s definitely a lot of sensitive data that gets sent to the domain just because of people not changing configs
replyI don't understand, what risk would there be if they chose _not_ to serve a site?
replySomeone else could
replyNo, because they can't register the domain, it's already taken, no matter if a web service is running behind it or not
replyIt's just part and parcel of owning the domain. It's one thing to have the domain, but the next step is offering an active website so that people that actually put that domain in a browser can see it's a placeholder.
replyThis is not the point discussed here.
reply> Someone else could
When you own a domain, you can choose not to serve anything on HTTP/S, and still nobody can come and serve some other website on your domain, because they don’t control the DNS records.
Why HTTP? Why not SSH? When I try to connect to it that way, I get no response. How will I know it's a placeholder?
replyHTTP is used by billions of people while SSH is not. It should be pretty apparent. Why do people answer my phone calls and texts but everyone is ignoring my smoke signals?
replyWhat is the smoke signal for “we’ve been trying to reach you about your car’s extended warranty“?
reply