What is a 444 status code?

A 444 is not part of the HTTP specification. It is an nginx invention, and it means the server closed the connection immediately without sending a response. Because nothing is sent, you will rarely see the number 444 anywhere except in the site's own access logs. What your client sees is a connection reset or an empty reply.

That is the whole point of it. A refusal that says nothing gives the other side no information to work with.

Why a site would use it

Returning a proper error costs the server work: generating a page, sending headers, keeping the connection open long enough to finish. Against high-volume unwanted traffic, that cost adds up, and it also tells the sender exactly what happened.

return 444 in an nginx config skips all of it. Operators use it for requests matching a blocklist, for known scanner user agents, for requests to paths that should not be public, and for traffic from address ranges they have decided not to serve.

How to recognise it from the client side

You will not get a status code, so look at the shape of the failure instead:

• The connection is accepted and then reset, rather than refused outright at the TCP level.
• It happens fast, with none of the delay a real timeout involves.
• It is consistent for a given request shape and disappears when you change the user agent, the path or the source address.
• A browser on the same connection loads the page normally.

That last point separates a 444 from a genuine network problem. A dropped connection that only affects your client is a decision.

What to do about it

Since the server tells you nothing, work backwards through the things it could have matched. Change one variable at a time: try a full browser header set, try a different path on the same host to see whether the rule is path-scoped, and try a different IP to see whether the rule is address-scoped. Whichever change restores a response identifies the rule.

Retrying unchanged is pointless here in a way it is not for a 408 or a 503. The server has already decided about this request shape, and sending it again produces the same silence.