Hacker News Reader

It doesn't matter. Use anything fake/non-public.

On the contrary, it does matter. What if you used [random].com and someone registered it? Presumably you'd use a different TLD and the chances are slim, but it's still best to use a correct test URL.

The chances would not be slim. They'd be zero, because you'd be using a fake TLD.

.dev used to be a fake TLD, as did .local. Both now exist.

Don't assume what doesn't exist now won't exist in the future. ;)

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?

I 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.

There actually are correct fake TLDs, specifically reserved for this exact use case: https://tools.ietf.org/html/rfc2606

Reply on news.ycombinator.com