2 ms·
"foo.int/ernal" lookalike attacks in 3… 2… 1… (to be fair, you generally can't get an .int domain registered. "int is considered to have the strictest applica
by eqvinox 3y ago
"foo.int/ernal" lookalike attacks in 3… 2… 1…
(to be fair, you generally can't get an .int domain registered. "int is considered to have the strictest application policies of all TLDs, as it implies that the holder is a subject of international law.")
… now that I think about it, "foo.in/ternal" makes so much more sense …
- GTP 3y agoBut you could do that with any domain, what's special in this case?
- eqvinox 3y ago> what's special in this case There's an existing TLD that is a string prefix of the new TLD. Apart from lookalike attacks I'm also wondering if this will do weird things while you type in an address, e.g. if you try to type "foo.internal" and pause for a second after "foo.int"… your application may run off and do lookups or even prefetches.
- lifthrasiir 3y agoThat happens pretty regularly anyway, e.g. `example.com` vs. `example.co/m` or `example.net` vs. `example.ne/t` (and both `.co` and `.ne` allow SLD registrations).