Error map
HELO 504 5.5.2 Helo command rejected: need fully-qualified hostname (invalid EHLO name)
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (12)
Apache: [ssl:warn] AH01909: example.com:443:0 server certificate does NOT include an ID which matches the server name
Apache's SSL virtual host name does not match any name inside the certificate it loads.
SMTP: 550-5.7.25 The IP address sending this message does not have a PTR record setup, or the corresponding forward DNS entry does not point to the sending IP
Gmail (and others) require your sending IP to have a reverse DNS (PTR) record that resolves back to the same IP; yours has none o…
SMTP: 504 5.5.2 <localhost>: Helo command rejected: need fully-qualified hostname
The receiving server refused your EHLO/HELO greeting because the name you sent is not a valid fully-qualified domain name.
Firefox: Websites prove their identity via certificates — the certificate is only valid for other names. Error code: SSL_ERROR_BAD_CERT_DOMAIN
The certificate does not include the hostname you typed.
Java: javax.net.ssl.SSLHandshakeException: No subject alternative names matching IP address 10.0.0.5 found
Java checks the hostname against the certificate's SANs and found no matching entry (for DNS names or IPs).
curl: (51) SSL: no alternative certificate subject name matches target host name 'example.com'
The certificate's names (SANs) don't include the host curl connected to.
MTA-STS policy fetch failed / no valid TLS (mta-sts.txt not reachable or certificate invalid)
Senders can't retrieve or trust your MTA-STS policy, so TLS enforcement isn't applied (or mail is deferred in enforce mode).
SMTP TLS certificate verification failed: hostname mismatch / unable to get local issuer (mail client or library)
The client verified the mail server's certificate and it didn't match the host name or wasn't trusted.
openssl verify error:num=62:Hostname mismatch / Verify return code: 62
The certificate is valid but not for the hostname you connected to or asked OpenSSL to check.
Java: SSLPeerUnverifiedException — Certificate for <host> doesn't match any of the subject alternative names
The TLS handshake worked, but Java's hostname verification found the certificate isn't valid for the requested host.
550 5.1.8 Sender address rejected: Domain not found (sender domain has no DNS A/MX)
The receiving server looked up the sender's domain and found no valid DNS record, so it rejected the message.
554 5.4.4 Unable to route: no MX or A record for the recipient domain / Host not found (HostNotFound)
The sending server can't find a mail route for the recipient's domain.
Two steps away (36)
ERR_TOO_MANY_REDIRECTS with Cloudflare (Flexible SSL redirect loop)
The page redirects to itself forever — classic cause: Cloudflare SSL mode “Flexible” while the origin redirects HTTP to HTTPS.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a Cloudflare site (certificate not issued / multi-level subdomain)
Cloudflare has no edge certificate for the hostname — the Universal SSL cert is still pending, or the hostname is a second-level…
NET::ERR_CERT_AUTHORITY_INVALID with a Cloudflare Origin Certificate (record not proxied)
Cloudflare Origin CA certificates are only trusted by Cloudflare — visitors reaching the origin directly (grey-cloud record, dire…
cURL error 6: Could not resolve host: api.example.com
PHP cURL couldn’t resolve the hostname via DNS.
sudo: unable to resolve host <hostname>: Name or service not known
The machine’s hostname isn’t in /etc/hosts (or DNS), so sudo prints this warning — usually after changing the hostname.
ping: google.com: Temporary failure in name resolution
The Linux host can’t resolve domain names — no working DNS server is configured or reachable.
SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
The receiving server (often Gmail or Outlook) is temporarily throttling your mail because the volume or reputation of your sendin…
SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
The recipient server deliberately rejected the first delivery attempt from an unknown sender (greylisting) and expects a legitima…
SMTP: 554 5.7.1 Service unavailable; Client host [203.0.113.5] blocked / 554 5.7.1 <mail.example.com>: Client host rejected: Access denied
The server refused the connection from your IP because it is blocked by policy, not in the allowed list, or listed on a blacklist.
NET::ERR_CERT_COMMON_NAME_INVALID: Your connection is not private (certificate is for a different domain)
The certificate presented doesn’t include the hostname you visited — e.g. visiting www.example.com with a certificate only for ex…
Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Firefox found an expired certificate in the chain presented by the server.
OpenSSL: SSL alert number 112 — tlsv1 unrecognized name
The server did not recognise the hostname sent in SNI and rejected the handshake (or an alert/warning is logged).
javax.net.ssl.SSLHandshakeException: PKIX path building failed: unable to find valid certification path to requested target
Java doesn’t trust the server’s certificate chain (self-signed, corporate proxy CA, or missing intermediate).
Java: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
The server rejected the Java client's TLS offer — no shared protocol/cipher, SNI issue or a required client certificate.
Let's Encrypt: Fetching http://example.com/.well-known/acme-challenge/token: Timeout during connect (likely firewall problem)
The ACME validation server could not reach your server on port 80 within the timeout.
curl: (60) SSL certificate problem: unable to get local issuer certificate
curl could not verify the server's certificate — missing CA, incomplete chain, self-signed or expired certificate.
curl: (77) error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: none
curl cannot read the CA bundle file it is configured to use — missing file, wrong path or permissions.
Browser: *.example.com certificate does not match a.b.example.com (ERR_CERT_COMMON_NAME_INVALID)
A wildcard certificate covers exactly one label: `*.example.com` matches `www.example.com` but not `a.b.example.com` or the bare…
SMTP: 530 5.7.0 Must issue a STARTTLS command first / 530 5.7.1 Authentication required
The server will not accept mail until you encrypt the connection (STARTTLS) and/or authenticate, and your client did neither.
SMTP: [SSL: WRONG_VERSION_NUMBER] wrong version number — SMTP over SSL on a STARTTLS port
Your client tried to start TLS immediately on a port where the server speaks plain SMTP first (or the reverse), so the handshake…
Nodemailer: Error: Greeting never received (code: 'ETIMEDOUT', command: 'CONN')
The TCP connection was made but the server never sent its SMTP `220` banner — usually a TLS mode mismatch or a firewall/proxy swa…
Nodemailer: Error: self signed certificate in certificate chain (code: 'ESOCKET') / unable to verify the first certificate
Nodemailer refused the SMTP server's TLS certificate because it is self-signed, expired, hostname-mismatched or missing its inter…
SSL Labs: Chain issues: Incomplete — Extra download (intermediate certificate missing)
The server sends only its own certificate and not the intermediate CA(s), so some clients cannot build a trusted chain.
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM — certificate signed with SHA-1 or MD5
The browser rejects a certificate (or a chain certificate) signed with a weak hash like SHA-1.
OpenSSL: error:num=20:unable to get local issuer certificate / SSL: CERTIFICATE_VERIFY_FAILED
The client could not build a chain from the server's certificate to a CA it trusts — the issuer is missing locally or the server…
Self-signed/CSR certificate rejected: no Subject Alternative Name (openssl req needs -addext)
A certificate made with a plain `openssl req` has only a CN, and modern clients ignore the CN.
Go: x509: certificate relies on legacy Common Name field, use SANs instead
Go (1.15+) no longer accepts certificates that only have a CN and no Subject Alternative Name.
Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
keytool or the JVM could not open the keystore — wrong password, wrong file type, or damaged file.
Java: SSLHandshakeException — TLSv1/TLSv1.1 or algorithm disabled by jdk.tls.disabledAlgorithms
A newer JDK refuses a TLS version, cipher or certificate algorithm listed in `java.security`.
Java: SSLException — Unrecognized SSL message, plaintext connection? (HTTPS client talking to an HTTP port)
The client expects TLS, but the server answered with plain text, so the handshake can't start.
java.net.UnknownHostException: api.example.com
DNS resolution failed for the hostname.
ACM certificate stuck in Pending validation
ACM is waiting to see the DNS (or email) validation record — it wasn’t created, was created in the wrong DNS zone, or has a typo.
Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved)
Windows can’t resolve Microsoft’s server names — DNS, hosts file, proxy or firewall problems.
Whitelabel Error Page — This application has no explicit mapping for /error
Spring Boot’s default error page — the request hit no controller mapping (404) or a controller threw (500).
TypeError: Missing parameter name at 1 (path-to-regexp)
An Express 5 (path-to-regexp v8) route uses old wildcard syntax like '*' or '/:id?'.
connect: Network is unreachable (ENETUNREACH)
The host has no route to the destination network — no default gateway, interface down, or trying IPv6 without IPv6 connectivity.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError