HTTP 451 Unavailable For Legal Reasons: what the error means and what to do

You open a page and you get "451 Unavailable For Legal Reasons". This is not a broken server and it is not a typo in the address. A server, or a network between you and the server, has decided on purpose not to show you this page, because of a legal demand.

This guide explains what the status code 451 means, who sends it, how it differs from 403 and 404, and what to do if you are a visitor, a site owner or someone who monitors websites.

What does HTTP 451 Unavailable For Legal Reasons mean?

HTTP 451 is a status code from the 4xx family. It is defined in RFC 7725, "An HTTP Status Code to Report Legal Obstacles", written by Tim Bray and published in February 2016. The RFC says the code is for the case where a server operator has received a legal demand to deny access to a resource, or to a set of resources that includes the requested one.

The number is a reference to Ray Bradbury's novel Fahrenheit 451, in which books are outlawed. The RFC itself only thanks Ray Bradbury in its acknowledgements and does not explain the choice of number.

Two details matter. First, a 451 says nothing about the page itself: the RFC states that the code implies neither that the resource exists nor that it does not. Second, if the legal demand ends, a request may still fail. The block is a statement about the law, not about the server's health.

Who sends a 451, and what does it look like?

Often the site operator sends it. But the RFC says the blocking server might not be the origin server. It names ISPs, cache providers and DNS servers as entities in the path that could deny access, and says that legal demands typically most directly affect ISPs and search engines.

The RFC asks the sender to explain the block in the response body: who made the demand, which law applies and which people and resources it covers. It also asks the blocking entity to identify itself in a Link header with the relation blocked-by. This is the example from the RFC:

HTTP/1.1 451 Unavailable For Legal Reasons
Link: <https://spqr.example.org/legislatione>; rel="blocked-by"
Content-Type: text/html

The blocked-by link names the party that actually implements the block, not the party that demanded it. Both the explanation and the link are only recommendations ("SHOULD") in the RFC, so many 451 responses carry neither. To see the headers of a page yourself, run curl -i on the address.

451 compared with 403, 404 and 410

All four codes mean "you do not get the page", but they tell you different things.

The caching column matters. A 451 response is cacheable by default, unless the request method or explicit cache controls say otherwise. A 403 is not on the list of codes that are cacheable by default. So a cache can keep serving a 451 after the block is gone.

Why the same site returns 451 in one country and 200 in another

The block depends on where the request comes from. The best-known case followed the start of GDPR. Some websites outside the European Economic Area chose to answer visitors from the EEA with 451 instead of complying with the new privacy law. Many regional news sites in the United States did this. The GDELT Project crawls the web and reported that these errors appeared only from its crawlers located in EU countries, not from crawlers elsewhere. One affected site showed a notice that it was not intended for people in the EEA.

Sources disagree on how many sites do this, so treat it as one common cause, not the only one. A court order, a copyright takedown or a sanctions rule can also apply to one country and not to others.

You may never see a 451

RFC 7725 says plainly that clients cannot rely on the use of the 451 code. Some authorities want to avoid transparency and do not want the demand disclosed at all. So a legal block can also appear as a 403, a 404, an empty answer, a DNS failure or a timeout. When a page fails only in one country and you see no reason, a legal block is one of the possible causes.

What to do about error HTTP 451

Check a 451 from other locations

Because a block depends on location, one check is not enough. Use the free website down checker to request the page from 22 locations on six continents. The checker treats any answer below 500 as a reply from a working server and shows the status code for each city. A page that is blocked in one region shows 451 there and 200 in the others. That pattern tells you the block is regional, not a server failure.

For the full method, read how to check if a website is down from multiple locations.

When this is not the right tool

• You need the reason. The checker shows the status code and the response time. It does not show the legal reason. For that, read the response body and the Link header with curl -i.
• You need legal advice. A status code tells you what a server did. It does not tell you what the law requires of you. Ask a lawyer.
• You want to bypass a block. This guide does not help with that, and a monitoring tool will not either.
• The block is from a private network. A company or school can filter traffic inside its own network. The checker tests from public data centers and will not see it.

FAQ