Error 400: Bad Request
Is it your browser or the website? Check right here whether the site responds normally for everyone else.
Checks the status code, every redirect, the variants with and without www and over http and https, the SSL certificate and the response time.
Free, no sign-up - no data about you is stored.
Result
Technical finding without guarantee. The check runs once from a server in Germany. If your website is only unreachable from certain networks or countries, the result may differ.
What does Error 400 mean?
A 400 Bad Request means the server considers the request malformed and won't process it at all. Unlike a 500, nothing has crashed, the server is simply rejecting what it received.
Often the cause is on the visitor side, or more precisely in their browser: too many or too large cookies, a broken URL or a faulty upload. Then only some people see the error while the site works for everyone else. nginx often shows "400 Bad Request - Request Header Or Cookie Too Large" in this case.
If the site also returns 400 in the checker here, the problem is the server or the application itself, for example a rule that rejects certain requests across the board.
Common causes.
Oversized cookies
Shops, tracking and consent tools set lots of cookies. Once together they exceed the server limit, every request from that browser is rejected.
Malformed URL
Invalid characters, badly encoded special characters or a link cut off in an email can make a request invalid.
Stale browser cache
Stored data no longer matches the current version of the site, for example after a rebuild or domain change.
Upload too large
Some servers answer oversized files with 400 instead of the more fitting 413 Payload Too Large.
Invalid API request
If required fields are missing or the format is wrong, an API responds with 400. This mostly affects forms and integrations.
With WordPress and hosting.
On WordPress sites with WooCommerce, several tracking tools and a cookie banner, cookies grow quickly. A typical sign is that only admins or regular customers see the error, because they've collected the most. The size limit for request headers is set in the nginx or Apache config, and on shared hosting only the host can change it.
If the 400 only appears when submitting a form or saving in the editor, look at security plugins and the hosting firewall, which may flag certain content as an attack. Proxies that modify headers on the way can also cause a 400.
How to fix it.
Compare with the checker
If the checker above returns 200, the site works in principle and the problem is your browser. If it returns 400, the server is the issue.
Delete the site's cookies
In your browser settings, delete cookies and site data for this one domain only. That fixes the most common case on the spot.
Check the URL
Type the address again instead of copying a long link. Watch out for special characters, spaces and parts that got cut off.
Try a private window or another browser
If it works there, cookies, cache or a browser extension are to blame.
Reduce cookies on the site
If many visitors are affected, check which plugins and tracking services set large or numerous cookies, and clean up.
Have the server limit raised
If that's not enough, your host can increase the request header limit. That's a web server setting, not something in WordPress.
Impact on Google.
Googlebot doesn't send cookies, so the most common 400 case doesn't affect it. If a page returns 400 to Google as well, though, Google treats it like a page that doesn't exist: it won't be indexed or drops out of the index. Check the Pages report in Search Console for URLs with 4xx errors.
Help from a developer
I can take care of it.
The check shows where things go wrong. I am happy to fix it, once or on an ongoing basis.
Good to know
Questions about Error 400?
The most common questions, answered briefly.
Questions about Error 400
Is a 400 my fault or the website?
Usually your browser, if others can see the site normally. If the checker here shows a 400 too, the website or server is the problem.
Will I lose data if I delete the cookies?
If you only delete cookies for this one site, you'll be logged out there and a shopping cart may be empty. Other websites aren't affected.
What does "Request Header Or Cookie Too Large" mean?
That's nginx's 400 message when a request's cookies or headers are bigger than allowed. Deleting the site's cookies helps for now, the lasting fix is setting fewer cookies or raising the server limit.
All status codes at a glance.
2xx: Success
- 200OKAll good: the server understood the request and delivers the page.
- 201CreatedThe request succeeded and created something new, for example a record via an API.
- 204No ContentSuccessful, but the response has no body. Typical for APIs and background requests, not for regular pages.
3xx: Redirects
- 301Moved PermanentlyPermanent redirect: the page now lives at a new address. Search engines switch to the new URL.Causes and fixes →
- 302FoundTemporary redirect: the page is currently available at another address, the original URL stays valid.Causes and fixes →
- 303See OtherRedirect to another page that is fetched with GET, typically after submitting a form.
- 304Not ModifiedThe page has not changed since the last visit, so the browser uses its cached copy. Not an error.
- 307Temporary RedirectTemporary redirect like 302, but the request method (such as POST) is guaranteed to stay the same.
- 308Permanent RedirectPermanent redirect like 301, but the request method (such as POST) is guaranteed to stay the same.
4xx: Client errors
- 400Bad RequestThe server can't process the request because it is malformed, for example due to oversized cookies or a broken URL.
- 401UnauthorizedThis page requires you to log in, for example via server-side password protection. No valid credentials, no access.Causes and fixes →
- 403ForbiddenThe server understood the request but refuses access, for example because of file permissions, a firewall or a block.Causes and fixes →
- 404Not FoundThere is no page at this address. It was deleted, moved, or the URL is misspelled.Causes and fixes →
- 405Method Not AllowedThe address exists but doesn't accept this kind of request, such as a POST where only GET is allowed.
- 408Request TimeoutThe server waited too long for the complete request and closed the connection, often on a slow connection.
- 410GoneThe page was removed deliberately and permanently and won't come back. A clearer signal than 404.Causes and fixes →
- 429Too Many RequestsToo many requests in a short time: a rate limit or bot protection is temporarily slowing down access.Causes and fixes →
- 451Unavailable For Legal ReasonsThe page is blocked for legal reasons, for example by an official order or a country block.
5xx: Server errors
- 500Internal Server ErrorGeneric server error: something went wrong while building the page. With WordPress it is usually a plugin, theme or PHP issue.Causes and fixes →
- 501Not ImplementedThe server doesn't know or support the request method. Rare on regular websites.
- 502Bad GatewayA server in front (proxy, nginx, CDN) didn't get a usable response from the actual server, often because PHP crashed.Causes and fixes →
- 503Service UnavailableThe server is temporarily unavailable due to maintenance or overload. Try again later.Causes and fixes →
- 504Gateway TimeoutA server in front waited too long for the actual server to respond and gave up.Causes and fixes →
- 520Web Server Returned an Unknown ErrorCloudflare error: the server behind Cloudflare sent an empty, invalid or unexpected response.
- 521Web Server Is DownCloudflare error: the server behind Cloudflare refuses the connection, so it is down or blocking Cloudflare.
- 522Connection Timed OutCloudflare error: Cloudflare couldn't establish a connection to the server behind it in time.
- 523Origin Is UnreachableCloudflare error: the server behind it can't be reached, often because of a wrong IP address in the DNS records at Cloudflare.
- 524A Timeout OccurredCloudflare error: the connection to the server works, but it didn't respond in time (100 seconds by default).
- 525SSL Handshake FailedCloudflare error: the encrypted connection between Cloudflare and the server behind it could not be established.
- 526Invalid SSL CertificateCloudflare error: the SSL certificate on the server behind Cloudflare is invalid or expired (with SSL mode "Full (strict)").
No status code: connection errors
- ×Server not found (DNS)There is no server for this domain: it has expired, is misconfigured, or the record with the IP address is missing.Causes and fixes →
- ×Connection refusedThe server is known but doesn't accept connections. The web server isn't running or a firewall is blocking.
- ×TimeoutThe server didn't answer in time. It is overloaded, stuck, or not reachable at all.
- ×Certificate error (SSL)The SSL certificate has expired, doesn't cover this domain, or the certificate chain is incomplete. Browsers show a warning.Causes and fixes →

