Error map

rua external DMARC reports not arriving: external destination domain didn't authorise reports (_report._dmarc record)

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.

rua external — DMARC reports not arriving: external destination domain didn't authorise reports (_report._dmarc record) (Email / SMTP)rua external550 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…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…third-party — DMARC p=reject blocking your own legitimate mail from third-party senders (CRM, newsletter, helpdesk) (Email / SMTP)third-partyDMARC 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.310DMARC reject — 550 5.7.1 Unauthenticated email is not accepted due to the domain's DMARC policy (p=reject) (Email / SMTP)DMARC rejectcURL error 6 — cURL error 6: Could not resolve host: api.example.com (PHP)cURL error 6sudo: 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…550 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.26SPF PermError: too many DNS lookups — SPF: spf=permerror — Too many DNS lookups (limit is 10) (Email / SMTP)SPF PermError: too …SPF: multiple SPF records — SPF: spf=permerror — Multiple SPF records found for example.com (Email / SMTP)SPF: multiple SPF r…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…5.7.32 — Gmail: 550 5.7.32 Your email has been blocked because the From: header domain isn't aligned with SPF or DKIM (Email / SMTP)5.7.32BIMI — BIMI logo not displayed in Gmail/Yahoo: DMARC enforcement, SVG Tiny PS or VMC certificate problem (Email / SMTP)BIMI500 — 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)UnknownHostExceptionPending validation — ACM certificate stuck in Pending validation (AWS)Pending validation0x80072EE7 — Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved) (Windows)0x80072EE7No MX record / Domain not found — SMTP: 550 5.1.2 Domain not found / 554 5.4.4 Unable to resolve MX / Host or domain name not found (Email / SMTP)No MX record / Doma…Postfix: Host or domain name not found — Postfix: status=deferred (Host or domain name not found. Name service error for name=example.com type=A: Host not found, try again) (Email / SMTP)Postfix: Host or do…Helo command rejected: need fully-qualified hostname — SMTP: 504 5.5.2 <localhost>: Helo command rejected: need fully-qualified hostname (Email / SMTP)Helo command reject…AADSTS700016 — Azure AD (Entra ID): AADSTS700016 Application not found in the directory (Azure)AADSTS700016AADSTS50076 — Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required (Azure)AADSTS50076NOAUTH — ReplyError: NOAUTH Authentication required. (Node.js)NOAUTH

Directly related (7)

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…

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…

third-partyEmail / SMTP

DMARC p=reject blocking your own legitimate mail from third-party senders (CRM, newsletter, helpdesk)

After moving to `p=reject`, mail from tools sending on your behalf bounces or lands in spam because they aren't aligned.

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.

DMARC rejectEmail / SMTP

550 5.7.1 Unauthenticated email is not accepted due to the domain's DMARC policy (p=reject)

The recipient rejected your message because the From domain publishes `p=reject` and your mail failed SPF/DKIM alignment.

Two steps away (21)

cURL error 6PHP

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

PHP cURL couldn’t resolve the hostname via DNS.

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.

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

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: 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 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…

5.7.32Email / SMTP

Gmail: 550 5.7.32 Your email has been blocked because the From: header domain isn't aligned with SPF or DKIM

Gmail's bulk sender rules require the visible From domain to align with an authenticated SPF or DKIM domain.

BIMIEmail / SMTP

BIMI logo not displayed in Gmail/Yahoo: DMARC enforcement, SVG Tiny PS or VMC certificate problem

Your brand logo doesn't appear next to emails even though you published a BIMI record.

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.

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.

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.

No MX record / Domain not foundEmail / SMTP

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: Host or domain name not foundEmail / SMTP

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.

Helo command rejected: need fully-qualified hostnameEmail / SMTP

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.

AADSTS700016Azure

Azure AD (Entra ID): AADSTS700016 Application not found in the directory

The client ID in your sign-in request doesn’t exist in the tenant you’re authenticating against.

AADSTS50076Azure

Azure AD (Entra ID): AADSTS50076 / AADSTS50079 — multi-factor authentication required

A Conditional Access policy requires MFA, but the sign-in flow (often a script, legacy client or ROPC password grant) can’t compl…

NOAUTHNode.js

ReplyError: NOAUTH Authentication required.

The Redis server requires a password (or ACL user) but the client didn’t authenticate.