HTTP 444: No Response
HTTP 444 No Response is a non-standard status code used by Nginx to instruct the server to close the connection without sending a response. This is used to block malicious or unwanted requests — the client receives a connection reset instead of an HTTP response.
Status
444 No ResponseExample
GET /xmlrpc.php HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0
Accept: text/html(connection closed — no HTTP response sent)
Nginx access log:
192.0.2.55 - - [28/Feb/2026:14:22:01 +0000] "GET /xmlrpc.php HTTP/1.1" 444 0How to Troubleshoot
Check Nginx configuration
Look for 'return 444' directives in the Nginx configuration to see which requests are being blocked.
nginx -T | grep 'return 444'
Check access logs
Review Nginx access logs to see which requests are getting 444 responses.
Verify you are not being blocked
If you are a legitimate user, check if your IP, User-Agent, or request pattern matches a blocking rule.
Common Causes
Nginx request blocking rule
highAn Nginx configuration rule is deliberately returning 444 to drop the connection for matching requests (e.g., bots, scanners, specific IPs).
Firewall or WAF rule
mediumA Web Application Firewall or security rule is configured to silently drop suspicious requests.
Related Status Codes
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.