425
Too Early
Client errors (4xx)·RFC 8470
What 425 means
The server is unwilling to risk processing a request that might be replayed.
Related to TLS 1.3 early data (0-RTT), which is vulnerable to replay attacks.
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot421Misdirected Request422Unprocessable Content423Locked424Failed Dependency426Upgrade Required428Precondition Required429Too Many Requests431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 425
What does HTTP 425 mean?
425 Too Early: The server is unwilling to risk processing a request that might be replayed. Related to TLS 1.3 early data (0-RTT), which is vulnerable to replay attacks.
Which class does status code 425 belong to?
425 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 425 code defined?
Status code 425 is defined in RFC 8470 and is part of the IANA HTTP Status Code Registry.