451 Unavailable For Legal Reasons

What’s actually happening

The request is well-formed and the resource exists, but the server (or an intermediary on the path) returns 451 to say access is blocked by law. It's the deliberate, honest cousin of a 403: a court order, government censorship, a DMCA takedown, or geo-restricted licensing. The number is a nod to Fahrenheit 451. RFC 7725 recommends a Link header with rel="blocked-by" naming the entity that demanded the block, though many servers omit it.

Common causes

• Government or regulatory censorship requiring an ISP, CDN, or origin to block the resource in a jurisdiction.
• A court order or legal injunction compelling removal or geo-blocking of specific content.
• DMCA / copyright takedown applied at the host, CDN, or registrar level.
• Geo-restriction for licensing — streaming or regional rights that legally bar serving certain countries (commonly keyed off client IP).
• An upstream provider (CDN/WAF) enforcing a legal block before the request reaches your origin.

How to fix it

1. Find out who is blocking and whyInspect response headers for a Link: <...>; rel="blocked-by" entry and any explanatory body. Confirm whether the 451 comes from your origin, your CDN/WAF, or an upstream — curl -I against the origin directly versus through the CDN tells you where the block lives.
2. If you didn't intend it, check your edge providerA 451 you didn't configure usually originates at a CDN, WAF, or hosting provider responding to a takedown or compliance rule. Check that provider's dashboard, abuse notices, and legal/compliance inbox.
3. Make a lawful block accurate and clearIf you must block for a real legal reason, return 451 (not a generic 403/404), serve a human-readable explanation, and add the RFC 7725 Link rel="blocked-by" header so clients and crawlers understand it's a legal restriction.
4. Scope geo-restrictions preciselyFor licensing-driven geo-blocks, key the rule to the specific countries the legal terms require and verify your IP-geolocation source. Over-broad rules block legitimate users in regions you were allowed to serve.
5. Resolve the underlying demand through legal channelsThe status is a symptom of an off-the-wire requirement. Lifting it means addressing the order or takedown itself — counter-notice, licensing the rights for the region, or complying with the directive.