451 Unavailable For Legal Reasons — HTTP Status Code

What 451 means

451 Unavailable For Legal Reasons means "I am not serving this because of a legal demand." It is defined in RFC 7725, Section 3, published in 2016. Unlike most 4xx codes, it says nothing about what the client did wrong. It exists so that legal blocking is visible and distinguishable from ordinary access denial or a missing page.

RFC 7725 asks servers to explain the legal demand in the response body: who made it, which law or regulation applies, and to whom and what it applies. Section 4 of the RFC adds that the entity doing the blocking should identify itself with a Link header whose rel parameter is blocked-by:

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

That header names the party implementing the block, not the authority that ordered it.

When you see it

• Geographic restrictions. A site blocks visitors from a country where serving the content would break local law, or where it has chosen not to comply with local rules.
• Court orders and takedowns. A platform disables a specific page, repository or file after a legal notice, while the rest of the service works normally.
• Network-level blocking. An ISP or national network operator intercepts requests to a blocked site and answers with its own 451 page.
• Sanctions and export rules that stop a service from serving users in particular regions.

The same URL can return 200 in one country and 451 in another, or 200 on one network and 451 on a different ISP in the same city.

Common causes

Unlike most errors, 451 is rarely a bug. The usual causes are deliberate: a legal notice the site operator acted on, a geoblocking rule set at the CDN or application level, or a block applied by an intermediary. Less often, a geolocation rule meant for one country catches the wrong users because an IP address is mapped to the wrong location, or because traffic arrives through a VPN or proxy in a blocked region.

How to fix it

If you run the site and did not intend the block:

1. Find who is sending it. Check the Link: rel="blocked-by" header and the body. If the response is not from your server or CDN, the block is upstream and outside your control.
2. Review geoblocking rules in your CDN, WAF and application. Confirm the country list and that the rule only applies where it should.
3. Check IP geolocation for affected users. Misattributed IP ranges can put visitors in the wrong country.

If you run the site and the block is intentional, return 451 rather than 403 or 404, include the explanation RFC 7725 asks for, and add the blocked-by header. Search engines and users can then tell a legal block from a broken page.

If you are a visitor, the response body should say why the content is unavailable. Whether you can or should access it another way depends on the law where you are.

How to check it

Look at the status, the Link header and the server identity in one request:

curl -s -D - -o /dev/null https://www.example.com/blocked-page \
  | grep -i -E "^(HTTP|link|server|cf-ray|via)"

The server, via and CDN headers help show whether the 451 came from your origin, your CDN or a network in between. Run the same command from servers in different regions to see whether the block is regional.

What it means for uptime monitoring

PingRobot's checker sends a GET with the user agent PingRobot/1.0 (+https://pingrobot.io/bot), follows redirects, and treats the final response as up only if its status is 200–399. A 451 counts as down, and the failure is re-checked from a second region before alerting.

Because 451 is often regional, results can differ between regions, and the second-region confirmation may not see the same answer as the first. A 451 that appears for one region and not another is a strong sign of geoblocking rather than an outage. If the block is your own and expected, it is not a failure to alert on; point the monitor at a URL that is meant to be reachable everywhere, such as your home page or a health endpoint. If the block is unexpected, treat it as an incident for the affected audience, since those users cannot reach your content.

Related codes

• 403 Forbidden – access refused for reasons other than law.
• 404 Not Found – nothing at this URL.
• 410 Gone – removed permanently, by choice.
• 401 Unauthorized – authentication required.
• 511 Network Authentication Required – another response that may come from the network, not the site.

Start monitoring free — 10 monitors, no credit card.