Name Collision
Name Collision | Guide to Name Collision Identification and Mitigation for IT Professionals | FAQs: Name Collision Identification and Mitigation for IT Professionals | Name Collision Occurrence Mitigation for New ccTLDs | FAQs: Name Collision Occurrence Management Framework for Registries | Report a Name Collision
What is a Name Collision?
Name Collision refers to the situation in which a resource name that is intended to be resolved in one naming system is inadvertently resolved in a different naming system, potentially leading to unexpected behavior such as communication being disrupted or redirected from its intended recipient.
Name collisions are not new. The introduction of any new domain name into the Domain Name System (DNS), whether a generic TLD, country code TLD, or second-level domain name, creates the potential for name collisions. However, queries for un-delegated TLDs at the root level of the global DNS have received renewed attention because applied-for new gTLD strings could be identical to name labels used in private networks or other naming systems. ICANN works to ensure a secure, stable, and resilient Internet. Therefore, ICANN has a commitment to the Internet community to launch a substantial effort to mitigate and manage name collision occurrence.
How will the risk of Name Collisions be mitigated in the New Generic Top-Level Domains (gTLD) Program: 2026 Round?
It is unlikely that name collisions will affect significant numbers of corporate network operators or Internet users. However, ICANN considers it essential that it does everything possible to minimize potential impact and to offer clear advice on dealing with the issue.
As part of ICANN's New Generic Top-Level Domains (gTLD) Program: 2026 Round, the Name Collision project's purpose is to implement the necessary functionality and procedures to assess and mitigate risks caused by name collisions between the global DNS and other naming systems using the Name Collision Risk Management Framework, following recommendations from the Name Collision Analysis Project Study Two Report, as directed by the ICANN Board on 7 September 2024 (2024.09.07,10).
Key Updates and Upcoming Milestones:
| Date | Description |
|---|---|
| 09 April 2026 |
ICANN published the Name Collision Procedure Public Comments Report. The finalized procedure documents are below:
The publication of this report fully closed out the Public Comment proceeding. A public review period ran from 29 January 2026 to 16 March 2026. During this time feedback on the procedure documents was received. To review the public comments, please visit https://itp.cdn.icann.org/en/files/name-collision/summary-report-name-collision-procedure-documentation-09-04-2026-en.pdf |
| 31 March 2026 |
ICANN published a video related to the Name Collision Observatory. The video answers frequently asked questions and provides information about the tool and how it works for users. To watch the video, please visit https://www.youtube.com/watch?v=ubAwLfPKk6s |
| 16 March 2026 |
ICANN Published the IPv6 Public Comments Report and the ICANN Controlled Interruption IPv6 Research Study Summary Report. The publication of these documents fully closed out the Public Comment proceeding. A public review period ran from 20 October 2025 to 22 December 2025. During this time, feedback on the reports was received which ultimately led to ICANN's final decision for how Controlled Interruption will be managed during the 2026 Round. To see the public comments, or read more about the outcome, please visit https://itp.cdn.icann.org/en/files/new-generic-top-level-domain-gtld/summary-report-name-collision-ipv6-research-study-16-03-2026-en.pdf. |
| 04 February 2026 |
The Name Collision Observatory (NCO) tool was developed to allow potential gTLD applicants, or other community members to display historical DNS magnitude data – a DNS popularity score – for top-level domain strings. The magnitude data presented is provided by a number of root server operators, as well as by some recursive resolver providers. The data may help applicants to assess the likelihood of their string causing high-risk name collisions. It should be noted that the magnitude data for an applied-for string is only one of several factors that will be considered in the Name Collision Initial Assessment. Both quantitative data and qualitative aspects will be considered when assessing the risk associated with that string in the 2026 Round TLD application process. Applicants should not assume that if this tool indicates a low volume of queries for a string, the string will be assessed during the application process as safe to be delegated. For more information see the "Name Collision" section of the latest version of the Applicant Guidebook. The NCO is available at https://newgtldprogram-nco.icann.org/ |
How are Name Collisions Identified? 127.0.53.53
127.0.53.53 is a special IPv4 address that will appear in system logs alerting system administrators that there is a potential name collision issue, enabling a quick diagnosis and remediation. The "53" is used as a mnemonic to indicate a DNS-related problem owing to the use of network port 53 for the DNS service.
System administrators that encounter a system error due to name collision are encouraged to take the following steps:
- Report the problem to ICANN »
Instances where there is a reasonable belief of demonstrable, severe harm as a consequence of a name collision should be reported. - Read the Guide to Name Collision Identification and Mitigation for IT Professionals (version 1.1) [PDF, 476 KB] and implement the measures outlined therein.
- Spread the word about the potential for name collision occurrence and mitigation in your professional circle.