444 No Response
Nginx administrators use return 444; to silently drop unwanted requests. The client never receives a status line - the 444 only shows up in nginx's access log.
An nginx-specific code that makes nginx close the connection without sending any response.
444 is an unofficial status code used by nginx. It is not part of the HTTP standard or the IANA registry.
What HTTP 444 No Response Means
An nginx-specific code that makes nginx close the connection without sending any response.
Nginx administrators use return 444; to silently drop unwanted requests. The client never receives a status line - the 444 only shows up in nginx's access log.
Common Causes
- A catch-all default_server block drops requests whose Host header matches no configured site
- Requests from blocked bots, scanners, or user agents
- Rules that drop requests for exploit paths such as /wp-login.php or /.env
- Requests to the server's bare IP address
How to Fix It (For Visitors)
- Check that you are using the correct domain name, not an IP address
- Disable VPNs or proxies that could be on a block list
- Contact the site owner if a legitimate page keeps returning an empty reply
How to Fix It (For Developers/Admins)
- Search your config for return 444: grep -rn 'return 444' /etc/nginx/
- Make sure your domain is listed in the right server_name so it does not fall through to the default server
- Check the access log to see which requests are dropped and why
- Narrow overly broad user-agent or path rules
Example: Dropping Unknown Hosts
# Catch-all server: close connections for unknown Host headers
server {
listen 80 default_server;
server_name _;
return 444;
}Clients see the connection close with no data. With curl it looks like this:
$ curl -i http://203.0.113.10/
curl: (52) Empty reply from serverBrowsers show a generic error such as ERR_EMPTY_RESPONSE. Because nothing is sent, the 444 status only exists in nginx's access log.
Frequently Asked Questions
What does HTTP 444 No Response mean?
Nginx administrators use return 444; to silently drop unwanted requests. The client never receives a status line - the 444 only shows up in nginx's access log. In short: An nginx-specific code that makes nginx close the connection without sending any response.
Is 444 an official HTTP status code?
No. 444 is not registered in the IANA HTTP Status Code Registry; it is specific to nginx. A client that receives an unrecognized status code treats it like the generic 400 code of its class.
How do I fix a 444 No Response error?
Search your config for return 444: grep -rn 'return 444' /etc/nginx/. Make sure your domain is listed in the right server_name so it does not fall through to the default server. Check the access log to see which requests are dropped and why.
Specification Status
444 No Response is not an official HTTP status code. It is not registered in the IANA HTTP Status Code Registry and is specific to nginx. Other servers and clients may not recognize it.