Neutral Activity
There is no recent abuse activity, or the IP address is whitelisted.
Whitelisted Subnet
Whitelisted netblocks are typically owned by trusted entities, such as Google or Microsoft who
may use them for search engine spiders. However, these same entities sometimes also provide cloud
servers and mail services which are easily abused. Pay special attention when trusting or
distrusting these IPs.
Log in to view charts and search reports for this IP.
Log In
Reports Activity
Example preview
Report Categories (Last 60 Days)
Example preview
Top Reporter Countries (Last 60 Days)
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 104.22.104.240
This IP address has been reported a total of
64
times from
21 distinct
sources.
104.22.104.240 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 30
reports;
Germany
with 6
reports;
United Kingdom of Great Britain and Northern Ireland
with 5
reports.
The most common categories in these recent reports were:
Web App Attack
45
times;
Bad Web Bot
29
times;
Brute-Force
27
times;
Port Scan
7
times;
SSH
2
times;
Other
4
times.
Recent Reports
We have received reports of abusive activity from this IP address within the last week. It is
potentially still actively engaged in abusive activities.
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Fail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad ...
show moreFail2Ban nginx: repeated suspicious HTTP requests consistent with automated probing, scanning or bad bot behaviour. Technical log details and local server identifiers intentionally omitted for privacy.
show less
Bad Web Bot
Web App Attack
Port Scan
Anonymous
(caddyscan) Scanner path probe from 104.22.104.240 (US/United States/-): 5 in the last 3600 secs; Po ...
show more(caddyscan) Scanner path probe from 104.22.104.240 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs: [REDACTED] 200 2627 104.22.104.240 - - [20/Aug/2026:11:21:47 +0000] "GET /web1/wp-admin/network/index.php HTTP/1.1"
[REDACTED] 200 2627 104.22.104.240 - - [20/Aug/2026:11:21:50 +0000] "GET /wp-admin/js/widgets/91567/index.php HTTP/1.1"
[REDACTED] 200 2627 104.22.104.240 - - [20/Aug/2026:11:21:50 +0000] "GET /wp-admin/includes/589124/index.php HTTP/1.1"
[REDACTED] 200 2627 104.22.104.240 - - [20/Aug/2026:11:21:50 +0000] "GET /wp-admin/images/453484/index.php HTTP/1.1"
[REDACTED] 200 2627 104.22.104.240 - - [20/Aug/2026:11:21:51 +0000] "GET /wp-admin/includes/496118/index.php HTTP/1.1"
show less
