Error map

SPF length SPF record invalid: TXT string longer than 255 characters (must be split into quoted strings)

Email / SMTP · layer 2, Network

Open the full error page →

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.

SPF length — SPF record invalid: TXT string longer than 255 characters (must be split into quoted strings) (Email / SMTP)SPF lengthSPF PermError: too many DNS lookups — SPF: spf=permerror — Too many DNS lookups (limit is 10) (Email / SMTP)SPF PermError: too …SPF fail / softfail: sender IP not authorized — SPF: Received-SPF: softfail (google.com: domain of transitioning bounce@example.com does not designate 203.0.113.5 as permitted sender) (Email / SMTP)SPF fail / softfail…SPF: multiple SPF records — SPF: spf=permerror — Multiple SPF records found for example.com (Email / SMTP)SPF: multiple SPF r…DMARC syntax — DMARC record invalid: syntax error, wrong tag order or multiple records (v=DMARC1 must be first) (Email / SMTP)DMARC syntax550 5.1.8 — 550 5.1.8 Sender address rejected: Domain not found (sender domain has no DNS A/MX) (Email / SMTP)550 5.1.85.4.310 — Exchange Online: 550 5.4.310 DNS domain does not exist (DNS domain name could not be resolved) (Email / SMTP)5.4.310SPF temperror — SPF temperror: DNS timeout while evaluating an include: mechanism (Email / SMTP)SPF temperror550 5.7.26 — 550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC) (Email / SMTP)550 5.7.26421 4.7.0 Try again later (rate limited) — 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 (Email / SMTP)421 4.7.0 Try again…550 5.7.25 PTR record required — 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 (Email / SMTP)550 5.7.25 PTR reco…DKIM: no key for signature — DKIM: dkim=permerror (no key for signature) / key not found in DNS selector._domainkey (Email / SMTP)DKIM: no key for si…DMARC: no record found — DMARC: dmarc=none (no DMARC record found for example.com) — bulk sender requirements not met (Email / SMTP)DMARC: no record fo…DMARC fail: SPF and DKIM not aligned — DMARC: dmarc=fail (p=REJECT) — SPF and DKIM pass but domains are not aligned with the From header (Email / SMTP)DMARC fail: SPF and…dig: status: SERVFAIL (DNSSEC validation failed) — Networking: dig: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL — resolver failed to answer (DNSSEC validation or upstream failure) (Networking)dig: status: SERVFA…Domain still resolves to the old IP (DNS propagation/cache) — Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation") (Networking)Domain still resolv…dig: status: REFUSED (recursion not available) — Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you (Networking)dig: status: REFUSE…500 — 500 5.5.1 Command unrecognized / Syntax error, command unrecognized (Email / SMTP)500501 — 501 5.1.7 Bad sender address syntax (invalid MAIL FROM) (Email / SMTP)501501 — 501 5.5.4 Syntax error in parameters or arguments (invalid SMTP command argument) (Email / SMTP)501UnknownHostException — java.net.UnknownHostException: api.example.com (Java)UnknownHostExceptioncURL error 6 — cURL error 6: Could not resolve host: api.example.com (PHP)cURL error 6Pending validation — ACM certificate stuck in Pending validation (AWS)Pending validationsudo: unable to resolve host — sudo: unable to resolve host <hostname>: Name or service not known (Linux)sudo: unable to res…Temporary failure in name resolution — ping: google.com: Temporary failure in name resolution (Linux)Temporary failure i…0x80072EE7 — Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved) (Windows)0x80072EE7

Directly related (7)

SPF PermError: too many DNS lookupsEmail / SMTP

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 fail / softfail: sender IP not authorizedEmail / SMTP

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.

SPF: multiple SPF recordsEmail / SMTP

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.

DMARC syntaxEmail / SMTP

DMARC record invalid: syntax error, wrong tag order or multiple records (v=DMARC1 must be first)

Receivers ignore your DMARC record because it isn't valid, so no policy is enforced.

550 5.1.8Email / SMTP

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.

5.4.310Email / SMTP

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.

SPF temperrorEmail / SMTP

SPF temperror: DNS timeout while evaluating an include: mechanism

SPF evaluation failed temporarily because a DNS lookup for one of your includes timed out or returned SERVFAIL.

Two steps away (18)

550 5.7.26Email / SMTP

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).

421 4.7.0 Try again later (rate limited)Email / SMTP

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…

550 5.7.25 PTR record requiredEmail / SMTP

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…

DKIM: no key for signatureEmail / SMTP

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…

DMARC: no record foundEmail / SMTP

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 fail: SPF and DKIM not alignedEmail / SMTP

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…

dig: status: SERVFAIL (DNSSEC validation failed)Networking

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.

Domain still resolves to the old IP (DNS propagation/cache)Networking

Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")

You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.

dig: status: REFUSED (recursion not available)Networking

Networking: dig: status: REFUSED / recursion requested but not available — the DNS server won't resolve queries for you

The DNS server answered, but its policy refuses to look up names for your address.

500Email / SMTP

500 5.5.1 Command unrecognized / Syntax error, command unrecognized

The server didn't understand a command the client sent, often because it spoke the wrong protocol or the wrong mode.

501Email / SMTP

501 5.1.7 Bad sender address syntax (invalid MAIL FROM)

The sender address in MAIL FROM isn't a valid address.

501Email / SMTP

501 5.5.4 Syntax error in parameters or arguments (invalid SMTP command argument)

A command argument (HELO name, MAIL FROM, RCPT TO or AUTH data) didn't match the expected syntax.

UnknownHostExceptionJava

java.net.UnknownHostException: api.example.com

DNS resolution failed for the hostname.

cURL error 6PHP

cURL error 6: Could not resolve host: api.example.com

PHP cURL couldn’t resolve the hostname via DNS.

Pending validationAWS

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.

sudo: unable to resolve hostLinux

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.

Temporary failure in name resolutionLinux

ping: google.com: Temporary failure in name resolution

The Linux host can’t resolve domain names — no working DNS server is configured or reachable.

0x80072EE7Windows

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.