ERR_ICANN_NAME_COLLISION — ICANN-level warning. Your internal network uses a domain (.corp, .home, .lan) that became a public TLD after ICANN gTLD expansion (2013+). Now external DNS resolves your internal hostname → confusion. Chrome warns. Fix: rename internal zones to .internal or .arpa (reserved), or explicitly blacklist.
Below: causes, fixes, FAQ.
.internal, .home.arpa (RFC 8375)SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.
Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).
Full chain verification: from leaf certificate through intermediates to root CA.
Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.
Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.
SSL certificate monitoring
TLS config audit
HTTPS as ranking factor
customer trust
www and subdomains.Strict-Transport-Security header forces browsers to always use HTTPS.SSL certificate monitoring, check history and alerts 30 days before expiry.
Sign up free.corp, .home, .mail, .office — NOT in public use but reserved by ICANN. Safer: .internal (proposed reserved), .home.arpa, .localhost.
Yes: attacker can register a .corp domain, resolve internal names to malicious IPs, MITM.
Chrome warns, does not block. But may treat as suspicious for certain workflows.
.internal (IETF draft), .test, .localhost, .invalid, .example — safe. Anything else — ideally check the public registry.