425 Too Early

What it means

Related to TLS 1.3 early data (0-RTT), which could be replayed by an attacker.

Common causes

• A request sent in TLS early data to a sensitive endpoint.

How to fix it

1. Retry the request after the TLS handshake completes; most clients do this automatically.

Example response

HTTP/1.1 425 Too Early
Content-Type: text/plain; charset=utf-8

Worked example

A client sends a request the server cannot fulfill as submitted. Check the response body and request details, correct the input or permissions, and retry only after the relevant issue is resolved.

How to read this response

1. Find the status line in your browser's Network panel, API client, or server access log.
2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 425

425 Too Early: The server will not process a request that might be replayed.

Common causes: 425

A request sent in TLS early data to a sensitive endpoint.

How to fix it: HTTP 425

Retry the request after the TLS handshake completes; most clients do this automatically.

Tools