HTTP 429 / 454 / 455 Blocked
Explanation of HTTP 429, 454 and 455 errors from our firewall: why they occur, what they mean, and how to resolve the block.
Simply.com uses an advanced protection system (Web Application Firewall) to prevent and block attacks, misuse, and exploitation of vulnerabilities in our customers' websites.
HTTP 429
When you encounter this error code, the web server performs an automatic security check of your browser before letting you continue. The check is there to protect the website against bots and automated attacks that can overload the server or attempt to exploit vulnerabilities.
All normal browsers can complete this check without problems and will subsequently receive an HTTP 200 response code.
In most cases, the check takes place in the background, and a regular browser with JavaScript and cookies enabled gets through in a few seconds without you noticing it. Once the check has been passed, you can freely navigate the website for a while before it is possibly renewed.
You may see the message "Checking your browser" for various reasons, e.g.:
- The website is currently receiving an unusually high number of requests or is actively under attack.
- The visit comes from an IP address that has a poor “reputation” and is known for attacks. You can look up the IP address at www.simply.com/rbl/.
- A known crawler that has made too many requests within a short period of time.
- The error code can also originate from the website's own code and protection (outside our control).
If you get stuck in the check, you can try reloading the page, updating your browser, or visiting the page from another device or network connection.
The error code tells the visitor that they should/can try again later.
HTTP 454
This response code can occur if:
- You are using a very old browser that lacks the features a modern web is built on.
- You are pretending to be a very old browser that lacks the features a modern web is built on.
All normal browsers can complete this check without problems and will subsequently receive an HTTP 200 response code.
If you are the owner of the website and find that legitimate visitors, integrations, or devices are being affected, first contact the owner of this integration and ask them to investigate the problem. Check which user-agent is being sent.
HTTP 455
This response code can occur if:
- The individual request is blocked due to a firewall rule.
- An AI agent that does not use a custom user-agent, or uses a user-agent that is also used by botnets.
You can see the precise reason for the block by reviewing the logs for your product. This is done under "Webserver logs" in our Control Panel.
Based on the reason, you can most likely resolve the block.
Services whitelisted
Well-known third-party services such as Googlebot, OpenAI, Anthropic, Bing, LinkedIn, Jetpack, PayPal, Facebook, ManageWP, etc. are whitelisted in our security filter.
We do not whitelist security services, as our security filter is itself a security element – and removing it in order to scan the security therefore does not make much sense.
Bots pretending to be approved services
If you are investigating blocks, note that many bots pretend to be these well-known services in an attempt to get through the security filter. Therefore, always check whether it is in fact an approved service that has been blocked (based on IP address).
Requirements for adding to the whitelist
In general, our WAF behaves properly towards legitimate requests, i.e. requests that comply with common rules. If you wish to have a well-known third-party service whitelisted, we can offer this if a public and maintained URL exists with a list of the IP addresses used.
Please investigate whether a block is actually occurring before requesting whitelisting.
Article from the support category: PHP