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.
This IP address has been reported a total of
15
times from
11 distinct
sources.
104.22.43.30 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 4
reports;
United Kingdom of Great Britain and Northern Ireland
with 4
reports;
United States of America
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
13
times;
Bad Web Bot
8
times;
Port Scan
6
times;
Brute-Force
3
times;
Hacking
2
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
Bad Web Bot
Web App Attack
Port Scan
Anonymous
Blocked by firewall on hugin [8443/tcp] | Rule: UFW | SPT: 21668 | TTL: 56 | LEN: 60 | TOS: 0x00 • R ...
show moreBlocked by firewall on hugin [8443/tcp] | Rule: UFW | SPT: 21668 | TTL: 56 | LEN: 60 | TOS: 0x00 • Reported by: github.com/sefinek/UFW-AbuseIPDB-Reporter
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
Scan for .git Files at 2026-10-19T01:05:45+00:00
Web App Attack
Anonymous
104.22.43.30 - - [19/Oct/2026:00:46:25 +0000] "GET /.git/config HTTP/2.0" 302 370 "-" "Mozilla/5.0 ( ...
show more104.22.43.30 - - [19/Oct/2026:00:46:25 +0000] "GET /.git/config HTTP/2.0" 302 370 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
...
show less
[18/Oct/2026:06:00:33 +0300] -- 104.22.43.30 Ban reason: Scanner [CMS_GENERIC] | Request: GET /.git/ ...
show more[18/Oct/2026:06:00:33 +0300] -- 104.22.43.30 Ban reason: Scanner [CMS_GENERIC] | Request: GET /.git/config HTTP/1.1
show less
Web scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ba ...
show moreWeb scanner probing for sensitive files (.env, .git, backups) or path traversal. Reported by fail2ban.
show less
