Comment by krackers 1 day ago I don't understand, what risk would there be if they chose _not_ to serve a site? 7 comments krackers Reply dylan604 1 day ago Someone else could altermetax 1 day ago No, because they can't register the domain, it's already taken, no matter if a web service is running behind it or not dylan604 1 day ago It'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. 4 replies →
dylan604 1 day ago Someone else could altermetax 1 day ago No, because they can't register the domain, it's already taken, no matter if a web service is running behind it or not dylan604 1 day ago It'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. 4 replies →
altermetax 1 day ago No, because they can't register the domain, it's already taken, no matter if a web service is running behind it or not dylan604 1 day ago It'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. 4 replies →
dylan604 1 day ago It'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. 4 replies →
Someone else could
No, because they can't register the domain, it's already taken, no matter if a web service is running behind it or not
It'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.
4 replies →