Domain error messages, explained
When a name will not load, the error message says which layer failed: the DNS that should resolve it, or the certificate that should secure it. Here is what each message means, whether the fault is the domain or the visitor, and what to check first.
A domain error is a failure caused by the name itself, before the website behind it gets a chance to answer. Resolution errors mean the name could not be turned into an address: NXDOMAIN says the name does not exist, SERVFAIL says no valid answer could be obtained, and REFUSED says a nameserver declined to answer. Certificate errors mean the name resolved but the connection could not be secured: the certificate has expired, was issued for another name, or comes from an issuer the browser does not trust.
NXDOMAIN (domain does not exist)
A DNS response code meaning the name being looked up does not exist. Browsers show it as DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED.
Error messages
NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN
ERR_NAME_NOT_RESOLVED
Non-existent domain
NXDOMAIN is a definite answer, not a timeout: a nameserver in the chain said there is no such name. If it comes from the domain's own nameservers, the record you asked for is missing from the zone, often a subdomain that was never created or was deleted. If the whole domain returns NXDOMAIN, the registry has no delegation for it, which happens when the domain has expired, been placed on hold, or was never registered. Check the spelling first, then whether the domain is registered and delegated, then whether the record exists in the zone. If only your own device gets NXDOMAIN while public resolvers answer, the fault is a local cache or network filter, not the domain.
Related terms NS record A record Expired clientHold
Monitor it DNS change detection
Tool Look up a domain's DNS records Read the full definition
SERVFAIL (server failure)
A DNS response code meaning the resolver could not get a valid answer for the name. It is a failure to answer, not a statement that the name is missing.
Error messages
SERVFAIL
Server failed
ERR_NAME_NOT_RESOLVED
A resolver returns SERVFAIL when every route to an answer failed. The two common causes on a registered domain are broken nameservers (they are down, unreachable, or do not hold the zone) and a DNSSEC mismatch, where the DS record at the registry no longer matches the keys the zone signs with, so validating resolvers reject the answer as bogus. The DNSSEC case is easy to miss: resolvers that do not validate still answer, so the site works on some networks and fails on others. A DNS host change without first removing or updating the DS record is the classic trigger.
Related terms DNSSEC DS record Lame delegation NS record
Monitor it DNS change detection
Tool Compare the answer across resolvers Read the full definition
REFUSED (query refused)
A DNS response code meaning the server received the query and declined to answer it.
Error messages
REFUSED
Query refused
A nameserver refuses a query for a zone it does not serve, or when its policy does not allow the asker. For a domain, REFUSED from one of its own listed nameservers usually means that server is not configured for the zone: the domain was deleted from a DNS host account, or the nameservers at the registrar point to a provider that never had the zone set up. Resolvers treat it like a dead server and try the others, so one refusing nameserver slows lookups, and all of them refusing produces SERVFAIL for visitors.
Related terms SERVFAIL (server failure) Lame delegation NS record
Lame delegation
A nameserver listed for a domain that does not answer authoritatively for it.
Error messages
lame delegation
lame server
The registry tells resolvers which nameservers hold a domain, and a lame delegation is one of those servers failing to hold it: it times out, refuses, or answers without authority. It is common after a DNS provider change, when the old provider is left in the NS set or the zone is removed from it too early. With some servers lame, lookups are slow and intermittently fail; with all of them lame, the domain stops resolving. The fix is to make the NS records at the registrar and in the zone list only servers that actually serve it.
Related terms NS record SERVFAIL (server failure) Registrar SOA record
Monitor it DNS change detection
ERR_CERT_DATE_INVALID (expired certificate)
A browser error meaning the site's certificate is outside its validity dates, almost always because it has expired.
Error messages
NET::ERR_CERT_DATE_INVALID
SEC_ERROR_EXPIRED_CERTIFICATE
Your connection is not private
Every TLS certificate has a fixed end date, and once it passes, browsers block the site behind a full-page warning such as "Your connection is not private". The usual cause is an automatic renewal that stopped working: a changed DNS record broke validation, a server was rebuilt without the renewal job, or a certificate was installed by hand and forgotten. Less often the certificate is valid and the visitor's clock is wrong, which you can rule out when other devices see the same error. Renewing and installing a new certificate fixes it immediately; nothing needs to propagate.
Related terms ERR_CERT_COMMON_NAME_INVALID (name mismatch) ERR_CERT_AUTHORITY_INVALID (untrusted issuer) HSTS error
Tool Check a site's SSL certificate Read the full definition
ERR_CERT_COMMON_NAME_INVALID (name mismatch)
A browser error meaning the certificate presented was not issued for the name in the address bar.
Error messages
NET::ERR_CERT_COMMON_NAME_INVALID
SSL_ERROR_BAD_CERT_DOMAIN
A certificate lists the names it covers, and the browser rejects it when the name you visited is not among them. The certificate itself can be perfectly valid; it simply belongs to someone or something else. The common causes are a missing variant (the certificate covers example.com but not www.example.com), a new subdomain added without reissuing, or DNS pointing the name at a shared host or CDN that does not hold a certificate for it, so the server falls back to its default one. Reissue the certificate with every name you serve, or fix the record that sends the name to the wrong server.
Related terms CNAME record A record ERR_CERT_DATE_INVALID (expired certificate) CAA record
Tool Check which names a certificate covers Read the full definition
ERR_CERT_AUTHORITY_INVALID (untrusted issuer)
A browser error meaning the certificate was not issued by an authority the browser trusts, or its chain to one is incomplete.
Error messages
NET::ERR_CERT_AUTHORITY_INVALID
SEC_ERROR_UNKNOWN_ISSUER
MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
Browsers trust a certificate only if it chains back to a root authority they ship with. A self-signed certificate, a certificate from a private or internal CA, or a server that sends its own certificate without the intermediate certificate in between all fail that check. The missing intermediate is the most common case on a public site and the most confusing, because some browsers fill the gap from a cache and load the site while others reject it. Install the full chain the authority provides, or replace a self-signed certificate with one from a public CA.
Related terms CAA record ERR_CERT_DATE_INVALID (expired certificate) ERR_CERT_COMMON_NAME_INVALID (name mismatch)
ERR_SSL_PROTOCOL_ERROR
A browser error meaning the secure connection could not be negotiated at all, before any certificate was checked.
Error messages
ERR_SSL_PROTOCOL_ERROR
ERR_SSL_VERSION_OR_CIPHER_MISMATCH
SSL_ERROR_RX_RECORD_TOO_LONG
The browser and server could not agree on how to talk securely. On a domain this usually means the name points at a server that does not serve HTTPS on port 443, such as an old host, a parking server or a mail server, or that the server only offers outdated protocol versions or ciphers. Related messages are ERR_SSL_VERSION_OR_CIPHER_MISMATCH and, in Firefox, SSL_ERROR_RX_RECORD_TOO_LONG, which means plain HTTP came back on the HTTPS port. Check that the A record points at the right server and that the server has TLS enabled for the name.
Related terms A record ERR_CERT_AUTHORITY_INVALID (untrusted issuer) ERR_CERT_COMMON_NAME_INVALID (name mismatch)
HSTS error
A browser error shown when a site that requires HTTPS through HSTS presents an invalid certificate, with no option to continue anyway.
Error messages
You cannot visit example.com right now because the website uses HSTS
HSTS (HTTP Strict Transport Security) is a header a site sends to say it must only ever be loaded over valid HTTPS. Once a browser has seen it, or the domain is on the browser's preload list, any certificate problem becomes a hard stop: the usual "proceed anyway" link disappears. The HSTS message is therefore never the root cause; it sits on top of an expired, mismatched or untrusted certificate. Fix the underlying certificate error and the HSTS error goes with it.
Related terms ERR_CERT_DATE_INVALID (expired certificate) ERR_CERT_COMMON_NAME_INVALID (name mismatch) ERR_CERT_AUTHORITY_INVALID (untrusted issuer)