Error map
Server header Security scan: Server / X-Powered-By header discloses software version
HTTP · layer 2, Network
Centre: this error. First ring: errors it is linked with (9). 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 (9)
Nginx: nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead
Since Nginx 1.25.1 HTTP/2 is enabled with a separate `http2 on;` directive instead of `listen 443 ssl http2;`.
400 Bad Request: Request Header Or Cookie Too Large
The server rejected the request because its headers, usually accumulated cookies, are bigger than it allows.
400 Bad Request: invalid character in header
A header contains a character the HTTP parser doesn't accept, such as a newline, a null byte or raw non-ASCII text.
401 Unauthorized without WWW-Authenticate header
The server answered 401 but didn't say which authentication scheme to use.
HTTP request smuggling: Content-Length vs Transfer-Encoding mismatch
Two servers in a chain disagree about where a request ends, letting an attacker hide a second request inside the first.
CORS error hides the real failure: Access-Control-Allow-Origin is missing on 4xx/5xx responses
The browser reports a CORS error, but the real problem is a server error (500, 401, 404) whose response carries no CORS headers.
Security scan: HTTP TRACE / TRACK method enabled
The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.
Security scan: Strict-Transport-Security (HSTS) header missing
The site doesn't tell browsers to always use HTTPS, so a first visit over HTTP can be intercepted (SSL stripping).
tlsv1 alert insufficient security — server rejects the offered protocol/cipher/key strength
The server requires stronger parameters (TLS version, cipher, DH/key size) than the client offered.
Two steps away (27)
HTTP 410 Gone
The resource used to exist but was intentionally and permanently removed, with no forwarding address.
Nginx: nginx: [emerg] unknown directive "x" in /etc/nginx/sites-enabled/x:12 — configuration file test failed
Nginx found a directive it doesn’t know — a typo, a missing semicolon on the previous line, a directive from a module that isn’t…
Nginx: [emerg] SSL_CTX_set_tmp_dh("/etc/ssl/dhparam.pem") failed (SSL: error:1401E0A8:SSL routines:... dh key too small)
The Diffie-Hellman parameters file is too weak (e.g. 512 or 768 bit) for the current OpenSSL security level.
HTTP 400 Bad Request
The server could not understand the request because its syntax, headers or body are malformed or invalid.
Warning: Cannot modify header information - headers already sent
You called `header()`, `setcookie()` or `session_start()` after output had already been sent to the browser.
HTTP 411 Length Required
The server refuses a request with a body but no Content-Length header.
HTTP 422 Unprocessable Content
The request is well-formed, but the data fails validation (e.g. invalid email, missing required field).
HTTP 428 Precondition Required
The server requires a conditional request (If-Match / If-Unmodified-Since) to prevent lost updates, and you didn’t send one.
Refused to load the script because it violates the following Content Security Policy directive
The page’s Content-Security-Policy doesn’t allow that script, style, image or connection source.
HTTP 401 Unauthorized
The request has no valid authentication credentials — you need to log in or send a valid token.
HTTP 403 Forbidden
The server understood the request but refuses to authorize it — you (or the server process) are not allowed to access this resour…
JWT Expired / Invalid Token
The JSON Web Token sent with the request is expired, malformed or signed with a different key, so the API rejects it (usually wit…
Webhook signature verification failed (Stripe, Razorpay, GitHub…)
Your endpoint computed a different HMAC signature than the one the provider sent, so the webhook is rejected.
Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in
The site owner blocked your network provider (ASN) — common for VPNs, cloud/data-center IPs and some mobile carriers.
Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned
The site owner (or a Cloudflare security setting) blocked your IP address.
CORS Error: No 'Access-Control-Allow-Origin' header is present
The browser blocked a cross-origin request because the server’s response didn’t include the CORS headers allowing your site’s ori…
CORS: Response to preflight request doesn't pass access control check: no HTTP ok status
The browser's OPTIONS preflight got an error status (401, 403, 404, 405, 500) instead of 2xx.
CORS: Request header field is not allowed by Access-Control-Allow-Headers in preflight response
Your request adds a custom header (Authorization, X-Api-Key, Content-Type: application/json) the server didn't list as allowed.
HTTP 405 Method Not Allowed
The URL exists, but it doesn’t accept the HTTP method you used (e.g. POST to a GET-only route).
HTTP 501 Not Implemented
The server doesn’t support the functionality (usually the HTTP method) needed to fulfil the request.
Cloudflare Error 1009: Access denied — The owner of this website has banned the country or region your IP address is in
The site blocks visitors from your country/region.
Cloudflare Error 1010: The owner of this website has banned your access based on your browser's signature
Cloudflare’s bot detection blocked the request because its browser fingerprint looks automated.
Cloudflare Error 1011: Access denied (Hotlinking denied)
An image or file is being loaded from another site, and Cloudflare Hotlink Protection blocked it.
Cloudflare Error 1012: Access denied
The site owner blocked access with a rule that matched your request (often due to malicious activity detected from your IP).
Error creating: pods is forbidden: violates PodSecurity "restricted:latest": allowPrivilegeEscalation != false ...
The namespace enforces a Pod Security Standard (baseline/restricted) and the pod spec breaks one of its rules.
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).
Map another error
Popular: 500400403ORA-009331064Critical errorFileNotFoundException assemblyTypeError