Three tabs in your protection area show what's been happening on your site: Overview, Traffic and Blocks. Each one covers the last 24 hours. Times are shown in UTC, not your local time.
Overview
Overview gives you a quick summary of the last 24 hours:
- Allowed requests: requests that reached your website.
- Blocked requests: requests that were stopped.
- Browser checks passed and Browser checks failed: shown when Captcha Protection applies to your site (see "The browser check your visitors may see").
- Would have blocked: shown while your site is in log mode. These requests matched an attack check but were let through.
- Recorded but let through: shown when your site is set to blocking and something was still recorded but let through.
Below the tiles, Overview also shows:
- Requests by hour: a chart of allowed and blocked requests over the last 24 hours.
- Protection now: a summary of what's working on your site.
- Top block reasons: the most common reasons requests were blocked.
- Most blocked IP addresses: the addresses blocked most often.
- Top countries: the countries most of your visitors came from.
If your host has paused any of your settings, you'll also see Settings your host has paused.
For more detail, use the links to the Traffic, Blocks and Protection tabs.
Traffic
Traffic, last 24 hours charts your allowed and blocked requests by hour. If there were none, it reads:
No requests were recorded in the last 24 hours.
Below the chart, a map shows requests to your site by the visitor's country. No IP addresses are stored or shown on the map.
Blocks
Blocks shows:
- Why requests were blocked: each reason in plain words, with how many requests it stopped.
- Most blocked IP addresses: the addresses blocked most often, with their location (city and country).
If nothing was blocked, it reads:
Nothing was blocked in the last 24 hours.
It also shows requests that were recorded but not blocked:
- Would have blocked, last 24 hours: while your site is in log mode.
- Recorded but let through, last 24 hours: when your site is set to blocking.
See "Log mode and blocking" for what these mean.
Block reasons
Here are the reasons you're most likely to see, in alphabetical order.
- Admin login lock: address not allowed: someone opened your WordPress login page or admin area from an address that isn't on your admin login lock list. See "Locking your WordPress login".
- AI crawler (bot blocking): blocked because AI crawlers are ticked in Bot blocking.
- blocked by default: (service name): a service your host blocks on your site by default. You can allow it on Settings, under Blocked by default by your host.
- blocked by owner: (service name): a service blocked under Block AI crawlers and other services.
- Browser check: naughty list: the visitor's address is on the stillorigin naughty list, so they were asked to complete a browser check. This isn't a block: they get through if they pass the check.
- Country rule: (country name): a country rule on your site or your host's network that is being enforced.
- Country rule in log mode: (country name): a country rule that is only being recorded, not blocked or checked.
- Error response from your site (404): your website sent this error itself, for example because the page doesn't exist. It's counted with blocked requests, but your protection didn't block it. The number shows the type of error.
- Fake crawler: something claimed to be a well-known service, such as a search engine, but didn't come from that service's official addresses. Your host manages this setting.
- Folder escape attempt: a request tried to reach files outside your website's folders. This is a common sign of an attack.
- Internal WordPress file request: a direct request for one of WordPress's internal PHP files. This is a built-in WordPress protection.
- Request for a private file: a request for a file that should never be public, such as a configuration file or a backup.
- Script or HTTP library (bot blocking): blocked because scripts and HTTP libraries are ticked in Bot blocking.
- Script run from uploads folder: an attempt to run a script from the WordPress uploads folder. This is a built-in WordPress protection.
- SEO crawler (bot blocking): blocked because SEO crawlers are ticked in Bot blocking.
- Too many requests: one IP address sent more requests than the rate limit allows. This block is temporary.
- WordPress setup file request: a request for wp-config.php or the WordPress install or upgrade scripts. This is a built-in WordPress protection.
- WordPress user listing attempt: an attempt to list your site's WordPress user accounts. This is a built-in WordPress protection.
- WordPress XML-RPC request: a request to xmlrpc.php, which is often used to guess passwords. This is a built-in WordPress protection that always applies.
Attack checks show the kind of attack and the rule number, for example, Database attack (rule 942100). Your host manages these checks.
What to do about a block
Most blocks are attacks or unwanted bots, and you don't need to do anything. If a real visitor, or a tool you use, is being blocked:
- Find the reason on Blocks.
- If it comes from a setting you can change, such as Bot blocking, the Admin login lock or a country on Countries, change it.
- If you can't change it, use Get help from your host and tell them the reason, the visitor's IP address and roughly when it happened.
For more help, see "Why was a visitor blocked, and how do they get unblocked?".
If you don't see a setting, your host manages it for you. Contact your host if you'd like it changed.
A failed browser check isn't a block. The visitor can try again with JavaScript turned on in their browser.
Not everything shows here
Some blocks happen on your host's network before a request reaches Website protection. These include addresses your host blocks for all its sites, and addresses on the stillorigin naughty list. These usually don't appear on your Blocks tab.