Fix website domain problems
Domain names, like google.com or whitehouse.gov, identify websites, but sometimes devices and sites on your intranet or local network use a domain name that's already assigned to an internet site. You might run into the following error if one domain name you’re using is the same as another name: "The site you are trying to reach may be conflicting with a new domain name."
Fix the name collision
If you see this error, you might be trying to visit a domain that uses a new Internet extension, like
.happy. This happens when an existing, private Internet address matches a new, public domain name. It could put you at a security risk, because you might end up at a site you didn't mean to where you could accidentally give out your personal information.
To fix the problem, talk to your system administrator.
Why name collisions happen
This error is frequently the result of a conflict between an internal domain name and a new public domain name. For example, many companies with offices in New York City use addresses like
printer.nyc to refer to computers and other resources in that office. However, the Internet Corporation for Assigned Names and Numbers (ICANN) has recently given the
.nyc domain to the City of New York. This means that visiting
printer.nyc could start redirecting to a public website, rather than an internal resource.
Info for system administrators
If you own the web page that's having the problem, learn more about why this is happening and how to fix it below.How Chrome detects name collisions
When a new domain name launches, it temporarily returns a special IP address (127.0.53.53). Chrome sees this address and warns you of the new, conflicting top level domain name. The warning might not happen all the time.
For example, if you use a laptop at work, the page might load, but if you try to access it from a local coffee shop, you might see this warning. Even though you only see the warning page some of the time, the problem still exists, and you need to update your configuration to avoid the new domain name.
Because of the potential for security problems, like sending print jobs across the Internet to an unrelated site, ICANN requires that all newly approved top-level domains return the spcial IP address 127.0.53.53 for all domains for the first 90 days of operation. This is so that users and administrators can detect and fix the problem, before more serious ones develop.
The best way to fix the problem is to stop using the old domain name. Although there isn’t a specific top-level domain reserved for use in private networks, we recommend you use
.internal if your configuration requires a specific top-level domain for internal use.
Visit the ICANN webpage for more information to help you fix any problems.
Megan is a Google Chrome expert and the author of this help page. Help her improve this article by leaving feedback below.