Error map
M365 DKIM Microsoft 365 DKIM: selector1/selector2 CNAME records not published (can't enable DKIM signing)
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)
SMTP: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled / SmtpClientAuthentication is disabled for the Tenant
Microsoft 365 turned off password-based SMTP AUTH for your mailbox or tenant; your client must use OAuth or the setting must be r…
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: 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…
CloudFront: CNAMEAlreadyExists / alternate domain name not covered by the certificate (InvalidViewerCertificate)
Adding a custom domain to CloudFront fails because the name is in use elsewhere or the certificate doesn't cover it.
Postfix: warning: connect to Milter service inet:localhost:8891: Connection refused (OpenDKIM/OpenDMARC not running)
Postfix is configured to use a milter (DKIM signing, spam filter) that isn't listening, so mail is deferred or sent unsigned.
Microsoft 365: 535 5.7.3 Authentication unsuccessful (SMTP AUTH / client submission blocked)
Microsoft 365 rejected the SMTP login, even with correct credentials, because SMTP AUTH or the sign-in method is blocked.
Microsoft 365: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
Exchange Online couldn't find a recipient with that address in the tenant's directory.
DKIM key too short: use 2048-bit RSA keys (1024-bit rejected or warned)
Some receivers and checkers flag or reject DKIM keys shorter than 2048 bits.
DKIM: body hash did not verify — message modified after signing (footers, mailing list, line wrapping)
The signature's body hash doesn't match the received body, because something changed the content after DKIM signing.
DKIM: signature expired (x= tag in the past) — signed message too old when verified
The DKIM signature has an expiry time and it passed before the message was verified.
Two steps away (27)
ReplyError: NOAUTH Authentication required.
The Redis server requires a password (or ACL user) but the client didn’t authenticate.
Received disconnect: Too many authentication failures
Your SSH agent offered too many keys before the right one, and the server cut the connection (MaxAuthTries, default 6).
passwd: Authentication token manipulation error
passwd couldn’t update the password — the root filesystem is read-only, /etc/shadow has wrong permissions/attributes, or a PAM ru…
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.
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).
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: 534-5.7.9 Application-specific password required. Learn more at https://support.google.com/accounts/answer/185833
The Google account has 2-Step Verification on, so SMTP clients cannot use the normal password; they need an app password (or OAut…
CloudFront: 403 ERROR — The request could not be satisfied
CloudFront refused or couldn’t serve the request — wrong alternate domain/certificate, blocked by origin access settings, a WAF/g…
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…
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.
DKIM: dkim=fail (body hash did not verify) / signature verification failed
The receiver recomputed the message hash and it does not match the DKIM signature, so the message was altered after signing.
Postfix queue keeps growing: many deferred messages (postqueue -p, flush, find the reason)
Mail piles up in the deferred queue because deliveries keep failing temporarily.
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.
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…
denied: Your authorization token has expired. Reauthenticate and try again. (Amazon ECR)
Docker’s login to Amazon ECR has expired — ECR tokens last 12 hours, so pushes and pulls fail until you log in again.
550 5.1.1 The email account that you tried to reach does not exist (User unknown)
The recipient mailbox doesn’t exist on the receiving server — a typo in the address, a deleted account, or a wrong domain.
SMTP: 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DB5EUR03FT015.eop-EUR03.prod.protection.outlook.com]
Microsoft 365 / Exchange Online rejected the message because the recipient address does not exist in that tenant (Directory Based…
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.
WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! (ssh host key changed)
The server’s SSH host key differs from the one saved in ~/.ssh/known_hosts — usually because the server was rebuilt or the IP was…
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
apt can’t verify a repository’s signature because the repo’s signing key isn’t installed (or has expired/rotated).
SELinux is preventing ... / avc: denied { read } for pid=... (permission denied despite correct permissions)
SELinux blocked the access — file permissions look fine, but the file’s security context or a boolean doesn’t allow the service t…
Forwarded or mailing-list mail fails DMARC: ARC chain missing or failed (arc=fail)
A message forwarded through a list or forwarding service loses SPF/DKIM alignment, and the ARC seal can't rescue it.
Postfix: status=deferred (connect to gmail-smtp-in.l.google.com[142.250.27.26]:25: Connection timed out)
Postfix could not reach the remote mail server on port 25, so the message stays in the queue and is retried.
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: verify error:num=10:certificate has expired — notAfter=Jan 1 00:00:00 2025 GMT
OpenSSL's verification found a certificate in the chain whose validity period has ended.
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError