451 Unavailable For Legal Reasons
The server is denying access to the resource as a result of a legal demand, such as a government-ordered content block.
Defined in RFC 7725 §3
What 451 means
RFC 7725, whose title is a deliberate nod to Ray Bradbury's novel Fahrenheit 451, defines this status for responses where access is denied specifically because of a legal demand: government censorship, a court order, a copyright takedown, or a comparable compulsion. Where possible, the response should explain the legal basis for the block and, ideally, name the authority that demanded it, via a Link header carrying rel="blocked-by" that points to a page with further details.
Services including GitHub, Google, and various news and media outlets use 451 to indicate content is blocked in specific jurisdictions because of local law, such as a GDPR-driven restriction, a DMCA takedown, or a government censorship order, rather than being genuinely removed or nonexistent. That transparency is exactly what distinguishes a legally compelled block from an ordinary 403 or 404, letting affected users and researchers understand why the content is missing.
The Link header, formatted as Link: <https://example.com/legal-notice>; rel="blocked-by", lets clients, crawlers, and archival tools programmatically discover the reason for a block and surface the relevant legal notice or transparency report, a pattern especially valued by projects like the Lumen Database that track takedown requests over time.
In practice, 451 usage is inconsistent: some operators deliberately use a plain 403 or 404 instead, to avoid drawing attention to the existence of a legal order at all, since some gag orders or national security demands may even prohibit disclosing that a block occurred. So while 451 is the spec-correct choice, its absence does not necessarily mean no legal block is in effect.
Common causes
- A government-mandated censorship order requires blocking access to specific content within a jurisdiction.
- A DMCA or other copyright takedown notice compels removal or geo-blocking of the resource.
- A court injunction or comparable legal demand requires the operator to restrict access for certain users or regions.
- GDPR or another regional privacy or data-protection law compels the operator to withhold content from specific regions.
- An ISP-level or CDN-level legal block intercepts the request before it ever reaches the origin server.
How to fix a 451
If you are the client (browser user or API caller)
- Check the response body and the Link header (rel="blocked-by") for details on which legal authority issued the block.
- Determine whether the block is region-specific and, where legally appropriate, access the content from an unaffected jurisdiction.
- Consult the cited legal notice or transparency report to understand available appeal or removal-dispute options.
If you run the server
- Include a Link header with rel="blocked-by" pointing to a page that explains the legal basis for the block.
- Explain, to the extent legally permitted, which authority issued the demand and what content is affected.
- Scope the block as narrowly as possible, to the specific region or resource actually covered, rather than blocking globally when only one jurisdiction requires it.
- Log and periodically review legal blocks so they can be lifted promptly once the underlying legal basis expires.
Example
GET /articles/8842 HTTP/1.1
Host: news.example.com
HTTP/1.1 451 Unavailable For Legal Reasons
Link: <https://news.example.com/legal-notices/8842>; rel="blocked-by"
Content-Type: text/plain
This content has been withheld in your region under a legal order.
See the Link header for details on the requesting authority.Try it live
Our free status responder returns a real HTTP 451 you can point tests, monitors or a browser at.
GET https://mcp.httpstatus.com/status/451