Welcome to the new IP check page! We're rolling it out gradually and would love your input. Spot a bug, or have a suggestion?
Share feedback
104.22.104.22
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
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example preview
Reports Activity
Example preview
Account required for the enhanced features
Log inSign up
IP Abuse Reports for 104.22.104.22:
This IP address has been reported a total of
12
times from
8 distinct
sources.
104.22.104.22 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Bulgaria
with 2
reports;
Belgium
with 1
report;
Japan
with 1
report.
The most common categories in these recent reports were:
Web App Attack
5
times;
Hacking
3
times;
Port Scan
1
time;
Bad Web Bot
1
time;
Brute-Force
1
time;
Other
1
time.
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.
Bad user agents ignoring web crawling rules. Draing bandwidth - detected by Fail2Ban in plesk-apache ...
show moreBad user agents ignoring web crawling rules. Draing bandwidth - detected by Fail2Ban in plesk-apache-badbot jail
show less
Bad Web Bot
Anonymous
(caddyscan) Scanner path probe from 104.22.104.22 (US/United States/-): 5 in the last 3600 secs; Por ...
show more(caddyscan) Scanner path probe from 104.22.104.22 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs: [REDACTED] 200 2627 104.22.104.22 - - [14/May/2026:00:26:30 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [14/May/2026:00:58:16 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [14/May/2026:00:58:37 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [14/May/2026:01:00:27 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [14/May/2026:01:02:05 +0000] "GET /.git/config HTTP/1.1"
show less
Port Scan
Anonymous
(caddyscan) Scanner path probe from 104.22.104.22 (US/United States/-): 5 in the last 3600 secs; Por ...
show more(caddyscan) Scanner path probe from 104.22.104.22 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_CUSTOMTRIGGER; Logs: [REDACTED] 200 2627 104.22.104.22 - - [13/May/2026:23:32:46 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [13/May/2026:23:35:35 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [13/May/2026:23:35:39 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [13/May/2026:23:37:03 +0000] "GET /.git/config HTTP/1.1"
[REDACTED] 200 2627 104.22.104.22 - - [13/May/2026:23:38:27 +0000] "GET /.git/config HTTP/1.1"
show less
Port Scan
Showing 1 to
12
of 12 reports
Think this IP has been falsely reported? You may request to have the associated
reports reviewed and removed.
Request Takedown 🚩
