MockFoxAdvertise

HTTP 451 Unavailable For Legal Reasons

Updated Free mock REST & WebSocket APIs

HTTP 451 Unavailable For Legal Reasons — The resource is blocked for legal reasons, such as a court order or government censorship.

Class
4xx Client Error
Defined in
RFC 7725
Official
Yes (IANA registry)
Cacheable by default
No (unless Cache-Control/Expires say so)
Safe to retry
Not without changing the request

Try it: get a real 451 response

Our test endpoint answers every request with 451 Unavailable For Legal Reasons.

curl -i https://mockfox.dev/api/status/451

Use it in tests, health-check monitors or to see how your client handles a 451. Add ?delay=2000 to slow it down.

What does HTTP 451 mean?

Named after Fahrenheit 451. Used when content is removed or geo-blocked because of legal demands — DMCA takedowns, court orders, sanctions or local censorship laws. The response should explain the demand and may include a Link header with rel="blocked-by" identifying who is enforcing the block. GitHub uses it for repositories taken down by DMCA.

How to fix 451

  1. Visitors: Reload the page, check the address for typos, and clear the site's cookies. If it persists, the site owner needs to fix it.
  2. Developers: Read the response body and server logs for details, fix the request (method, headers, body, credentials) and return a clear error message to clients.

Example 451 response

HTTP/1.1 451 Unavailable For Legal Reasons
Link: <https://legal.example.com>; rel="blocked-by"
Content-Type: application/json

{"status":451,"error":"Unavailable For Legal Reasons"}

4xx Client Error: The request contains an error or can't be fulfilled — fix the request before retrying. See the full list of HTTP status codes.

Related status codes

Related tools

Frequently asked questions

What does HTTP 451 Unavailable For Legal Reasons mean?

The resource is blocked for legal reasons, such as a court order or government censorship.

Is 451 a client or a server error?

451 is a 4xx code, so it signals a problem with the request (as seen by the server). Retrying the identical request usually gives the same result.

Where is 451 defined?

In RFC 7725. It's listed in the IANA HTTP Status Code Registry.

How can I test how my app handles a 451?

Call https://mockfox.dev/api/status/451 — it responds with 451 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.