← All status codes4xx – Client Error

HTTP 444 – No Response

(NGINX) The server closes the connection without sending any response, commonly used to silently drop malformed or malicious requests.

Common use case

Configured as a deliberate defence: instead of responding to obviously malicious or malformed traffic, NGINX just drops the connection to avoid giving attackers any information.

History

An NGINX-specific extension, not part of any official HTTP specification, introduced early in NGINX's history as a security-hardening feature.

Did you know?

Because no bytes are actually sent back, it never appears in a real client's response - it only shows up in NGINX's own access logs.

Other 4xx codes

400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot422Unprocessable Content425Too Early426Upgrade Required428Precondition Required429Too Many Requests430Shopify Security Rejection431Request Header Fields Too Large451Unavailable For Legal Reasons460Client Closed Connection463Malformed X-Forwarded-For Header464Incompatible Protocol Versions494Request Header Too Large495SSL Certificate Error496SSL Certificate Required497HTTP Request Sent To HTTPS Port499Client Closed Request