Agreed. However, in this case they still own the domain, so GOTO is the way to go. In fact that's the rub. If they still have access to the original page's l

Agreed. However, in this case they still own the domain, so GOTO is the way to go. In fact that's the rub. If they still have access to the original page's location, then GOTO makes sense. If they don't have access, then how do you know you're getting what you hoped for? What happens if I say I used to be https://google.com https://google.com, and then through some disaster the Google homepage is inaccessible for 3 seconds? That's a lot of users that just filtered down to my potentially malicious site, no matter how low the conversion rate. If the web was still a network of documents, I think something like what you're suggesting would be a lot more viable, particularly with hashing and signatures helping do the heavy lifting. But as an application delivery platform that still looks and pretends to be a network of documents, suddenly that carries a lot more risk.