Error map
SES reputation Amazon SES account under review or paused: bounce rate above 5% / complaint rate above 0.1%
Email / SMTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (12). 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 (12)
Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
You are sending faster than your Amazon SES account's per-second limit, so SES throttles the requests.
SES MessageRejected: Email address is not verified. The following identities failed the check in region
SES refused to send because the From address/domain isn’t verified — or the account is still in the SES sandbox, where recipients…
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…
CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
The certificate you want to attach to CloudFront isn't listed, because it was created in another region.
Gmail Postmaster Tools: spam rate above 0.3% — mail delivered to spam or throttled
Too many recipients mark your mail as spam, so Gmail's reputation for your domain drops.
Amazon SES SMTP: 535 Authentication Credentials Invalid (IAM user vs SMTP credentials, region)
The SMTP login to SES fails because you used the wrong kind of credentials or the wrong regional endpoint.
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.
Postmark: 406 Inactive recipient (error code 406) — address suppressed after a hard bounce or spam complaint
Postmark refuses to send to an address that previously hard bounced or complained, to protect your reputation.
AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy)
The AWS CLI or SDK can't verify the endpoint's certificate, usually behind a TLS-inspecting proxy or with an outdated bundle.
ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete
An Application Load Balancer HTTPS listener can't be created or serves the wrong certificate.
Microsoft: 550 5.7.606 Access denied, banned sending IP (S3150/S3140 — IP reputation block)
Outlook.com/Microsoft 365 blocked your sending IP because of its reputation.
Old clients can't connect to the AWS load balancer: security policy disables TLS 1.0/1.1 (or requires it)
The ELB/ALB/NLB SSL negotiation policy doesn't allow the protocol/ciphers the client uses.
Two steps away (36)
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: 452 4.5.3 Your message has too many recipients / 452 Too many recipients received this hour
The server limits how many recipients a single message or sender may have; yours exceeded it.
SMTP: 550 5.4.5 Daily user sending quota exceeded (Gmail)
The Gmail or Google Workspace account reached its 24-hour sending limit, so it stops accepting outgoing mail until the limit rese…
PHP mail() returns false / emails not delivered
PHP’s mail() function failed or emails never arrive (spam or rejected).
AccessDeniedException: User: arn:aws:iam::... is not authorized to perform: service:Action on resource: ...
The IAM user or role making the call has no permission for that action on that resource — the message names both.
API Gateway {"message": "Internal server error"} 502 — Malformed Lambda proxy response
The Lambda behind an API Gateway proxy integration returned something that isn’t the required {statusCode, headers, body} shape,…
WordPress / PHPMailer: SMTP Error: Could not authenticate / SMTP connect() failed
The SMTP server rejected the login or couldn’t be reached — wrong credentials, app passwords required, wrong port/encryption, or…
550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
The receiving (or your outgoing) mail server refused the message — relaying isn’t allowed, the sender isn’t authenticated, or it…
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).
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.
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…
ERR_TOO_MANY_REDIRECTS with Cloudflare (Flexible SSL redirect loop)
The page redirects to itself forever — classic cause: Cloudflare SSL mode “Flexible” while the origin redirects HTTP to HTTPS.
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…
SMTP: 535-5.7.8 Username and Password not accepted. Learn more at https://support.google.com/mail/?p=BadCredentials
The server received your login but rejected it — wrong username or password, an unusable password type, or a blocked sign-in.
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: 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: 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…
Python: smtplib.SMTPAuthenticationError: (535, b'5.7.8 Username and Password not accepted')
`smtp.login()` was rejected by the server — wrong credentials, wrong password type, or authentication not allowed for that accoun…
SendGrid: 403 Forbidden — The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved
SendGrid only sends from addresses or domains you have verified (single sender or domain authentication).
554 4.4.7 Message expired: unable to deliver in 840 minutes (delivery timeout)
The sending server kept retrying but the recipient server never accepted the message before the retry limit.
SendGrid: 401 Unauthorized / 403 Forbidden — API key invalid or lacking Mail Send permission
The SendGrid API or SMTP login rejects the key.
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.
Bounce storm / backscatter: your server sends bounces to forged senders or bounces loop between servers
Mail systems send non-delivery reports to innocent people (forged senders) or bounce messages ping-pong endlessly.
Exim: message is frozen — recipient or sender can't be bounced (frozen bounce messages pile up)
Exim freezes bounce messages it can't deliver (invalid sender), and they sit in the queue until removed.
API Gateway: {"message": "Endpoint request timed out"} (504 after 29 seconds)
The backend (usually Lambda) didn’t respond within API Gateway’s integration timeout (29 seconds by default for REST APIs).
docker: invalid reference format (repository name must be lowercase)
Docker couldn’t parse the image name — uppercase letters, spaces, an empty variable, or a misplaced option.
Error response from daemon: No such container
The container name or ID you used doesn’t exist on this Docker host — it was removed, has another name, or you’re talking to a di…
ERR_SSL_VERSION_OR_CIPHER_MISMATCH on a Cloudflare site (certificate not issued / multi-level subdomain)
Cloudflare has no edge certificate for the hostname — the Universal SSL cert is still pending, or the hostname is a second-level…
NET::ERR_CERT_AUTHORITY_INVALID with a Cloudflare Origin Certificate (record not proxied)
Cloudflare Origin CA certificates are only trusted by Cloudflare — visitors reaching the origin directly (grey-cloud record, dire…
Node/OpenSSL: Error: self signed certificate (code: DEPTH_ZERO_SELF_SIGNED_CERT)
The server presented a self-signed certificate (issuer equals subject), which no CA vouches for.
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.
Microsoft 365: 451 4.7.500 Server busy, please try again later (throttling / reputation)
Exchange Online is delaying your mail because its capacity limits or your sending reputation triggered throttling.
Chrome: You cannot visit example.com right now because the website uses HSTS (NET::ERR_CERT_… no bypass)
The site told browsers to use only valid HTTPS (HSTS), so Chrome hides the "Proceed anyway" link when its certificate has any pro…
Console: Refused to display 'https://…' in a frame because it set 'X-Frame-Options' to 'deny' / 'sameorigin'
The page you tried to embed in an `` forbids framing through the `X-Frame-Options` header or CSP `frame-ancestors`.
Console: [Violation] Permissions policy violation: camera is not allowed in this document (Feature-Policy)
A browser feature (camera, microphone, geolocation, fullscreen, payment…) was blocked by a `Permissions-Policy` header or an ifra…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError