Error map
domain verify Mailgun domain not verified / 'Domain not found': DNS records (SPF, DKIM, MX, tracking CNAME) missing
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (10). 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 (10)
The trust relationship between this workstation and the primary domain failed
The computer’s machine account password no longer matches Active Directory, so domain logins fail.
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…
Mailgun: 403 Forbidden — Sandbox subdomains are for test purposes only. Please add your own domain or add the address to authorized recipients
You are sending from Mailgun's free sandbox domain, which only delivers to addresses you have manually authorized.
DKIM: dkim=permerror (no key for signature) / key not found in DNS selector._domainkey
The message is signed with a selector, but the receiver found no DKIM public key in DNS at that selector, so verification cannot…
SPF: spf=permerror — Multiple SPF records found for example.com
The domain publishes more than one TXT record starting with `v=spf1`; receivers must treat that as a permanent error.
Mailgun 401 Forbidden: wrong API key or region (EU domains need api.eu.mailgun.net)
Mailgun rejects the request because the key is wrong, or the EU/US base URL doesn't match the domain's region.
Azure App Service: custom domain SSL binding failed (certificate not found, thumbprint or hostname validation)
Binding a TLS/SSL certificate to a custom domain in App Service fails or the domain isn't validated.
553 5.1.8 Domain of sender address <x> does not exist (sendmail/Exim sender verification)
The receiving server tried to resolve the sender's domain and failed.
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.
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 (30)
Windows Error 0x80070005 (E_ACCESSDENIED): Access is denied
Windows refused an operation because the account or process lacks permission — seen in Windows Update, installers, Task Scheduler…
Windows Error 0x80070002: The system cannot find the file specified
A file or registry entry Windows expected is missing — common in Windows Update, backups and app installs.
Windows Error 0x80004005 (E_FAIL): Unspecified error
A generic failure code — the operation failed for a reason the component didn’t report precisely. Context decides the fix.
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: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing
The server hit an internal problem (disk, database, content filter, DNS) while handling your message and asked you to retry later.
550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC)
Gmail/Outlook rejected the message because SPF and DKIM didn’t pass for the sender’s domain (DMARC failure).
SPF: spf=permerror — Too many DNS lookups (limit is 10)
Your SPF record needs more than 10 DNS lookups to evaluate, so receivers treat SPF as a permanent error and the check fails.
SPF: Received-SPF: softfail (google.com: domain of transitioning bounce@example.com does not designate 203.0.113.5 as permitted sender)
The server that sent the mail is not listed in the sender domain's SPF record, so the receiver marks it fail or softfail.
DMARC: dmarc=none (no DMARC record found for example.com) — bulk sender requirements not met
The sender's domain publishes no `_dmarc` TXT record, so receivers cannot apply any policy; Gmail and Yahoo now require one for b…
DMARC: dmarc=fail (p=REJECT) — SPF and DKIM pass but domains are not aligned with the From header
Authentication passed for another domain (your ESP's), but neither the SPF Return-Path domain nor the DKIM `d=` domain matches th…
Networking: dig: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL — resolver failed to answer (DNSSEC validation or upstream failure)
The DNS resolver couldn't get a valid answer, often because DNSSEC signatures are broken or the authoritative servers fail.
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.
Gmail: 421 4.7.28 Our system has detected an unusual rate of unsolicited mail originating from your IP address
Gmail rate-limited your sending IP because it saw a spike or spam-like patterns.
SendGrid: 401 Unauthorized / 403 Forbidden — API key invalid or lacking Mail Send permission
The SendGrid API or SMTP login rejects the key.
Azure SQL: Cannot open server 'x' requested by the login. Client with IP address 'y' is not allowed to access the server (Error 40615)
The Azure SQL server firewall doesn’t allow your client’s IP address.
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.
Windows/IIS: A specified logon session does not exist / The certificate does not have a private key associated with it
IIS cannot bind an HTTPS site because the imported certificate has no private key attached.
SMTP: 553 5.7.1 <noreply@example.com>: Sender address rejected: not owned by user user@example.com
The SMTP server only lets an authenticated user send as addresses they own, and the From/envelope sender does not match the login.
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.
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.
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.
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.
Let's Encrypt/CA: CAA record for example.com prevents issuance
The domain's DNS CAA records do not list the certificate authority you asked, so the CA must refuse.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError