Name Collision

Currently building this page.

A Name Collision is a term used to describe the circumstance in which a term is used to try and reach a private Domain Name that results in resolving to a public Domain Name unintentionally. Private domain names are used in Intranets and in many corporations and organizations throughout the world. A domain name on a private network that matches a name in the public Internet can create security risks in which private information is obtained or private networks are hacked.

New gTLD Program

A renewed interest in the name collision issue came about as ICANN's New gTLD Program was preparing to delegate hundreds of New domain names to the Root.

Interisle Consulting Report

ICANN contracted Interisle Consulting to carry out an investigation into the effects the delegation of 100s of new gTLDs would have on the security of the existing Internet and intranets around the world. The resulting report, which was published on August 6th, 2013 by ICANN, found that there would be many name collisions for new gTLDs that could create potential security risks. ICANN's initial response to this report was to propose a delay based on the assessed security risk each New gTLD would carry.

• For .home and .corp, ICANN deemed the two strings "high-risk" because of the widespread use of the terms on internal networks. Currently, ICANN is indefinitely delaying the delegation of these string to the Root Zone.

• 20% of applications had been deemed an "uncalculated risk" by ICANN initially, saying these strings would be delayed 2-3 months in their application process while they conduct more research into whether the string is of "high" or "low" risk.

Research

• ANA and verisign
• Name Collisions
• Collisions summit
• .club solution
• responses
• Australian Bank
• announcement
• looking at it wrong way?
• Neustar analysis
• Resolution
• Domain Incite response to resolution from ICANN
• Domain Name wire response
• Blocked Trademarks still Eligible for Donuts Sunrises