4 ms·
I agree that's it not really a big deal, but there are unforeseen consequences that can be mitigated by simply using the correct domain. So why not, what's to l
by Sevrene 10y ago
I agree that's it not really a big deal, but there are unforeseen consequences that can be mitigated by simply using the correct domain. So why not, what's to lose?
- smt88 10y agoI don't know what "correct" means. There's no "correct" fake TLD. People use different things. If you mean "correct" as in the production domain, then you're introducing a security risk for no reason. Never use a public (or potentially public) domain for testing or development.
- Viper007Bond 10y agoThere actually are correct fake TLDs, specifically reserved for this exact use case: https://tools.ietf.org/html/rfc2606 https://tools.ietf.org/html/rfc2606