Skip to the content

421 Misdirected Request

The request arrived at a server that isn't set up to answer for this host name. The client can try again on a new connection.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 9110

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

With HTTP/2 a browser may use one connection for several host names when they share an IP address and a certificate that covers them all. If the server at the other end doesn't in fact serve one of those names, it answers 421.

What to do about it

Clients are allowed to send the request again on a fresh connection, and browsers do that without showing anything. If visitors do get to see it, the configuration of the server is off: typically a certificate that covers more names than the site behind it serves, or a proxy that sends the connection to the wrong backend.

Not to be confused with

400 Bad RequestThe request itself is malformed.
404 Not FoundThe host is right, the path isn't.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12