451 Unavailable For Legal Reasons

The content exists but cannot be served for legal reasons — censorship orders, GDPR geo-blocks, DMCA takedowns. The code number is a deliberate Fahrenheit 451 reference, and responses should ideally include a Link header identifying the blocking authority.

What usually causes it

  • Geo-restrictions implementing regional law (news sites blocking EU pre-GDPR-compliance was the famous wave)
  • Court-ordered content removal
  • Sanctions-based access blocks

How to debug and fix it

  1. As a client there is rarely a technical fix — the block is policy, keyed usually on IP geolocation.
  2. As an operator, prefer 451 over a misleading 404: it is honest, and the Link header documents the blocking demand.

Easily confused with

Debugging an API? Build and inspect requests, check response headers, or read the full status-code debugging guide.