Error map
FCrDNS Reverse DNS (PTR) mismatch: forward-confirmed reverse DNS fails for the sending IP
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (7). 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 (7)
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…
Sending IP listed on a DNS blocklist (Spamcop, Barracuda, SORBS, UCEPROTECT) — mail rejected or sent to spam
Your server's IP appears on one or more DNSBLs, so many receivers refuse or junk your mail.
504 5.5.2 Helo command rejected: need fully-qualified hostname (invalid EHLO name)
The receiving server rejected the HELO/EHLO name, because it isn't a valid fully-qualified domain name.
Email provider suspended or throttled your account: bounce rate too high (hard bounces from invalid addresses)
Your sending service paused your account because too many messages bounced.
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.
Exchange Online: 550 5.4.310 DNS domain does not exist (DNS domain name could not be resolved)
Exchange Online couldn't resolve the recipient's domain, often a typo or a domain that isn't registered.
Two steps away (21)
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: 550 5.7.1 Service unavailable; Client host [203.0.113.5] blocked using zen.spamhaus.org
The receiving server checked your IP in a DNS blocklist (Spamhaus, Barracuda, SORBS…) and refused your mail because it is listed.
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.
Yahoo/AOL: 421 4.7.0 [TSS04] Messages from your IP temporarily deferred due to unexpected volume or user complaints
Yahoo deferred your mail because your IP's volume or complaint rate looks suspicious.
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.
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.
Gmail/Yahoo bulk sender requirement: one-click unsubscribe (List-Unsubscribe-Post) missing
Marketing/bulk mail without RFC 8058 one-click unsubscribe headers gets throttled or sent to spam.
Amazon SES account under review or paused: bounce rate above 5% / complaint rate above 0.1%
SES placed your account on probation or paused sending because bounce or complaint rates passed its thresholds.
SendGrid: emails accepted (202) but never delivered — recipient is on the bounce/spam/unsubscribe suppression list
SendGrid returns success, but messages to some addresses are dropped because they're suppressed.
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.
SMTP: 550 5.1.2 Domain not found / 554 5.4.4 Unable to resolve MX / Host or domain name not found
Mail cannot be routed because the recipient domain has no MX (or A) record, or DNS for it fails.
Postfix: status=deferred (Host or domain name not found. Name service error for name=example.com type=A: Host not found, try again)
Postfix could not resolve the destination domain through DNS — the resolver is down or unreachable, or the domain does not exist.
Certbot: Detail: DNS problem: NXDOMAIN looking up A for www.example.com - check that a DNS record exists for this domain
Let's Encrypt could not resolve the domain you asked a certificate for; no A/AAAA record exists.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError