Error map
500 500 5.5.1 Command unrecognized / Syntax error, command unrecognized
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)
PHP Parse error: syntax error, unexpected …
PHP can’t parse the file because of a syntax mistake — the real error is often on the line before the one reported.
IndentationError: unexpected indent / expected an indented block
Python’s block structure is broken — inconsistent indentation or mixed tabs and spaces.
SyntaxError: invalid syntax
Python couldn’t parse the code. The caret (^) points at or just after the mistake.
Firefox: Secure Connection Failed — SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
Firefox sent a TLS handshake but received plain HTTP back — you used `https://` on a port that serves HTTP.
OpenSSL: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
The peer did not answer with a TLS record — you spoke TLS to a plain HTTP/SMTP port (or the reverse), or a proxy intervened.
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.
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…
OpenSSL: error:14094410 / SSL alert number 70 — tlsv1 alert protocol version
The server rejected the TLS version your client offered, because it requires a newer (or older) protocol.
503 5.5.1 Bad sequence of commands / Error: send HELO/EHLO first (or need MAIL command)
The client sent SMTP commands in an order the server doesn't accept.
501 5.1.7 Bad sender address syntax (invalid MAIL FROM)
The sender address in MAIL FROM isn't a valid address.
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.
SSL routines: unsupported protocol (TLS 1.0/1.1 disabled by the server or OpenSSL security level)
Client and server have no common TLS version, usually because a legacy version is disabled on one side.
Two steps away (35)
MySQL ERROR 1064 (42000): You have an error in your SQL syntax
MySQL couldn’t parse the query. The text after “near” shows where parsing failed.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
Fatal error: Cannot redeclare function foo() (previously declared in …)
The same function (or class) was defined twice — usually a file included more than once.
NameError: name 'x' is not defined
Python doesn’t know the name — it was never assigned/imported in this scope, or it’s misspelled.
docker compose: services.x Additional property y is not allowed / yaml: line N: mapping values are not allowed
The compose file is invalid YAML or uses a key Compose doesn’t recognise at that level (usually an indentation mistake).
SyntaxError: await is only valid in async functions and the top level bodies of modules
await was used inside a function that isn’t async (or in a classic, non-module script).
SyntaxError: missing ) after argument list
A function call’s parentheses are unbalanced — often an unescaped quote or a missing comma/plus.
SyntaxError: Identifier 'x' has already been declared
The same let/const/class name was declared twice in the same scope.
SyntaxError: Invalid or unexpected token
The code contains a character the parser can’t handle — smart quotes, stray characters or an unterminated string.
ERR_SSL_PROTOCOL_ERROR (This site can't provide a secure connection)
The browser couldn’t negotiate TLS — the server sent an invalid response, often plain HTTP on the HTTPS port.
Firefox: Peer's Certificate has expired. Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Firefox found an expired certificate in the chain presented by the server.
Firefox: Websites prove their identity via certificates — the certificate is only valid for other names. Error code: SSL_ERROR_BAD_CERT_DOMAIN
The certificate does not include the hostname you typed.
cURL error 35: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to host:443
The TLS handshake failed — protocol/cipher mismatch, a proxy interfering, or the server closed the connection.
SMTP: [SSL: WRONG_VERSION_NUMBER] wrong version number — SMTP over SSL on a STARTTLS port
Your client tried to start TLS immediately on a port where the server speaks plain SMTP first (or the reverse), so the handshake…
OpenSSL: error:num=20:unable to get local issuer certificate / SSL: CERTIFICATE_VERIFY_FAILED
The client could not build a chain from the server's certificate to a CA it trusts — the issuer is missing locally or the server…
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: 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.
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…
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).
Chrome: This site can’t provide a secure connection — uses an unsupported protocol. ERR_SSL_VERSION_OR_CIPHER_MISMATCH
The browser and the server could not agree on a TLS version or cipher — the server is too old or misconfigured, or the browser is.
Chrome: Connection not secure — ERR_SSL_OBSOLETE_VERSION (old TLS 1.0/1.1)
The server only supports an outdated TLS version that current browsers no longer allow.
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.
421 Service not available, closing transmission channel (SMTP server refused or dropped the connection)
The receiving server accepted the connection but immediately said it can't serve you now and closed it.
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.
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.
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.
553 5.1.3 The recipient address is not a valid RFC-5321 address (mailbox name not allowed)
The recipient address you entered isn't syntactically valid.
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.
SMTPUTF8: internationalised email address (UTF-8 local part) rejected or mangled
Addresses with non-ASCII characters (`müller@example.com`, `用户@例子.cn`) fail because the server or client doesn't support SMTPUTF8.
HTTP 505 HTTP Version Not Supported
The server doesn’t support the HTTP protocol version used in the request.
HTTP 100 Continue
An interim response telling the client to go ahead and send the request body — normal when the client sent Expect: 100-continue.
HTTP 103 Early Hints
An interim response that sends Link headers early so the browser can preload CSS, fonts or scripts while the server is still buil…
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError