Domain Errors Explained: DNS and SSL Errors
Last updated: November 2026
What each error message means, whether the fault is the domain or the visitor, and what to check first.
A domain error stops a browser before the website gets a chance to answer. A resolution error such as NXDOMAIN or SERVFAIL means the name could not be turned into an address. A certificate error such as ERR_CERT_DATE_INVALID means it resolved, but the connection could not be secured. To tell a domain fault from a local one, ask a public resolver from another network: if it fails the same way, the fault is the domain.
Which layer failed
A browser loads a name in a fixed order, and the error message tells you which step it stopped at.
-
Does the name resolve?
A resolver asks the domain's nameservers for its address. If the name is missing, the nameservers are broken or DNSSEC fails, the browser stops here with a resolution error.
-
Does a server answer securely?
The browser connects to that address on port 443 and negotiates TLS. A server with no HTTPS, or one with outdated settings, fails here with a protocol error.
-
Is the certificate valid for this name?
The certificate must be in date, issued for the exact name visited, and chain to a trusted authority. Any one of those failing produces a certificate error.
-
Only then does the website load
Errors past this point, such as 404 or 500, come from the website itself and are not domain errors.
Resolution errors
The name could not be turned into an address, so the browser never reached a server.
- 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.
- 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.
- REFUSED (query refused)
- A DNS response code meaning the server received the query and declined to answer it.
- Lame delegation
- A nameserver listed for a domain that does not answer authoritatively for it.
Certificate errors
The name resolved and a server answered, but the connection could not be secured.
- 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.
- ERR_CERT_COMMON_NAME_INVALID (name mismatch)
- A browser error meaning the certificate presented was not issued for the name in the address bar.
- 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.
- ERR_SSL_PROTOCOL_ERROR
- A browser error meaning the secure connection could not be negotiated at all, before any certificate was checked.
- HSTS error
- A browser error shown when a site that requires HTTPS through HSTS presents an invalid certificate, with no option to continue anyway.
Domain error messages explained
Put this into practice
Look up a domain's records
Read every record from the domain's authoritative nameservers to see what exists.
Compare resolvers
Ask several public resolvers at once to tell a domain fault from a local one.
Check DNSSEC
Confirm the DS record at the registry matches the keys the zone signs with.
Check a certificate
Read the certificate a name presents: its expiry date, the names it covers and its chain.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 3 domains are free.
No credit card required • Cancel anytime
Frequently asked questions
What is a domain error?
A domain error is a failure caused by the name itself rather than by the website behind it or the device asking for it. Either the name does not resolve, because its DNS is missing, broken or unreachable, or it resolves but the certificate presented for it is expired, issued for another name or not trusted. Both stop a browser before the website has a chance to answer.
How do I tell if an error is the domain or my own network?
Ask a different resolver. If public resolvers such as 1.1.1.1 and 8.8.8.8 return the same error from another network, the fault is the domain. If they answer normally and only your device fails, the problem is a local cache, a VPN, a firewall or your router. A DNS propagation check does this comparison in one step.
What is the difference between NXDOMAIN and SERVFAIL?
NXDOMAIN is an answer: the authoritative servers say the name does not exist. SERVFAIL is a failure to get an answer: the resolver could not reach a working nameserver, or the answer failed DNSSEC validation. NXDOMAIN usually means a missing record, a typo or a suspended domain; SERVFAIL usually means broken nameservers or a DNSSEC mismatch.
Can an expired domain cause a DNS error?
Yes. When a domain expires, the registrar usually replaces its nameservers with a parking page or the registry places it on hold, which removes it from the zone. Visitors then get NXDOMAIN or a parking page instead of the site, often within a day of the expiry date.
Why does my site show a certificate error when nothing changed?
Certificates expire on a fixed date, so something always changes: time. The most common cause is an automatic renewal that silently stopped working weeks earlier. The next most common is a DNS change that sent the name to a host whose certificate does not cover it.