HTTP 425 Too Early

What does HTTP 425 mean?

The server is unwilling to process a request that might be replayed. Related to TLS 1.3 0-RTT “early data”, which can be replayed by an attacker. Servers answer 425 to non-idempotent early requests so the client retries after the full handshake.

4xx Client error: The request has a problem the client can fix: wrong URL, missing credentials, bad data or too many requests.

How to fix 425 Too Early

• Clients retry automatically; no action needed.

425 and SEO

No SEO impact.

Example response

HTTP/1.1 425 Too Early

How to return a 425 response

Node.js (Express)

res.status(425).json({ error: 'Too Early' });

PHP

http_response_code(425);

Python (Flask)

return {'error': 'Too Early'}, 425

Go (net/http)

w.WriteHeader(425)

nginx

return 425;

Related status codes

• 400 Bad Request — The server cannot process the request because it is malformed.
• 429 Too Many Requests — The client sent too many requests in a given amount of time.

Check which status code a URL returns with the HTTP header checker.