622 karma · joined May 5, 2010
There are certain circumstances where private network operators may wish to use their own domain naming scheme that is not intended to be used or accessible by the global domain name system (DNS), such as within closed corporate or home networks.
The "internal" top-level domain is reserved to provide this purpose in the DNS. Such domains will not resolve in the global DNS, but can be configured within closed networks as the network operator sees fit.
This reservation is intended for a similar purpose that private-use IP address ranges that are set aside (e.g. [RFC1918]).
It says it is licensed under Apache License 2.0, but also under "Prosperity Public License 3.0.0" which limits use for a commercial purpose to 30 days.
The history on why some external territories are coded is because an international standard is the basis for the two-letters used for these TLDs, and that standard is used for other purposes. Far flung localities are often coded due to things like physical mail delivery or customs boundaries which utilize the same standard.
Why does .eu exist? Essentially because "eu" was coded for the European Union to facilitate "EUR" as a currency code when the Euro was introduced. ISO 4217 currency codes derive from ISO 3166 country codes.
https://www.icann.org/en/announcements/details/ccnso-propose...
On my commute to work I see buses from half a dozen different agencies, the fact that every individual city in the metro area seems to run its own bus service is probably another piece of the problem.
In short, it seems too early to assume if you've ever stayed at a hotel you are a victim.
It is also not uncommon in places where petty theft is high for you to have to show your baggage receipt matches the baggage tag before you can take it from the baggage handling area.
Plus, should your luggage get waylaid, there are other things you can do to hasten its recovery: have a fairly unique bag that is unlikely to be mistaken by another traveller as theirs, clearly label your contact details inside and out in case the paper tag gets ripped off.
What is odd is my most recent Amazon return they did not offer that store as an return option, instead my nearest drop off point was an Amazon Books location about 15 miles further away. I'd assumed the Kohl's experiment was over.
Emoji is illegal according to the IETF IDN specification. Some naive clients allow it (i.e. don't follow the standard) but ICANN rules prohibit registries allowing registration of labels that are disallowed by the standard.
Also, ARIN only has allocations made in North America. Plus, ARIN only covers North American allocations.
https://github.com/phishai/phish-ai-api/blob/master/phish_ai...
In the case of .dev, it didn't even appear in the weeds of usage when the DNS root servers were measured for traffic to identify potential new TLDs usage conflicts in the real world (e.g. https://www.icann.org/en/system/files/files/name-collision-0... p22). Even if .dev were in significant usage, that traffic was not reaching the domain name system. The complaint seems to be fundamentally to be about the pre-loaded configuration of Chrome, not the DNS.
In the case of your regex, it would breaks millions of production domains in used today and fail in a wide variety of scenarios. It is only understandable in the context of someone who hasn't done any cursory research into the topic.