HTTP 444 No Response
Updated Free mock REST & WebSocket APIs
HTTP 444 No Response — nginx closes the connection without sending any response.
- Class
- 4xx Client Error
- Defined in
- Unofficial (nginx)
- Official
- No — nginx-specific
- Cacheable by default
- No (unless Cache-Control/Expires say so)
- Safe to retry
- Not without changing the request
What does HTTP 444 mean?
An nginx-only pseudo-status: return 444; makes nginx drop the connection immediately, which is handy for blocking scanners, unknown Host headers or abusive clients without wasting bandwidth. The client never sees 444 — it sees an empty reply (curl: "Empty reply from server"); 444 only appears in nginx's access log.
How to fix 444
- Visitors: Reload the page, check the address for typos, and clear the site's cookies. If it persists, the site owner needs to fix it.
- Developers: Read the response body and server logs for details, fix the request (method, headers, body, credentials) and return a clear error message to clients.
Example 444 response
# Not sent to the client — appears in nginx's access log: 203.0.113.7 - - [18/Oct/2026:10:00:00 +0000] "GET /slow HTTP/1.1" 444 0 "-" "Mozilla/5.0 …"
4xx Client Error: The request contains an error or can't be fulfilled — fix the request before retrying. See the full list of HTTP status codes.
Related status codes
- 499 Client Closed Requestnginx logs 499 when the client closed the connection before the server finished responding.
- 403 ForbiddenThe server understood the request but refuses to authorize it.
- 400 Bad RequestThe server can't process the request because it's malformed or invalid.
Related tools
Frequently asked questions
What does HTTP 444 No Response mean?
nginx closes the connection without sending any response.
Is 444 a client or a server error?
444 is a 4xx code, so it signals a problem with the request (as seen by the server). Retrying the identical request usually gives the same result.
Is 444 an official HTTP status code?
No. It isn't in the IANA HTTP Status Code Registry; it's specific to nginx. Generic HTTP clients treat it as an unknown 4xx status.
How can I test how my app handles a 444?
Call https://mockfox.dev/api/status/444 — it responds with 444 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.