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 47.79.13.81:
This IP address has been reported a total of
26
times from
12 distinct
sources.
47.79.13.81 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 8
reports;
Denmark
with 5
reports;
Canada
with 3
reports.
The most common categories in these recent reports were:
Web App Attack
16
times;
Bad Web Bot
11
times;
Exploited Host
7
times;
Hacking
4
times;
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.
Detected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot ...
show moreDetected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot / scanner behavior). Hits from same IP in last 60 minutes: 1. Unique request paths counted internally: 1. Cloudflare action: managed_challenge. Cloudflare source: botFight.
show less
[06/Sep/2026:06:25:43 +0300] -- 47.79.13.81 Ban reason: Scanner [SENSITIVE_FILES] | Request: GET /si ...
show more[06/Sep/2026:06:25:43 +0300] -- 47.79.13.81 Ban reason: Scanner [SENSITIVE_FILES] | Request: GET /sitemap-news.xml.gz HTTP/1.1
show less
Detected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot ...
show moreDetected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot / scanner behavior). Hits from same IP in last 60 minutes: 1. Unique request paths counted internally: 1. Cloudflare action: managed_challenge. Cloudflare source: botFight.
show less
Mass vulnerability scanning (LFI / path traversal probes with query parameters such as lokasie=/proc ...
show moreMass vulnerability scanning (LFI / path traversal probes with query parameters such as lokasie=/proc/...) against a production server. Observed on 1 day(s) between 2026-08-28 and 2026-08-28 (UTC). 60 further address(es) from the same network showed abusive behaviour. Sample request: GET /index.php?loknya=/proc/5/net/stat HTTP/1.1
show less
[27/Aug/2026:10:32:25 +0300] -- 47.79.13.81 Ban reason: Scanner [SENSITIVE_FILES] | Request: GET /si ...
show more[27/Aug/2026:10:32:25 +0300] -- 47.79.13.81 Ban reason: Scanner [SENSITIVE_FILES] | Request: GET /sitemap-index.xml.gz HTTP/1.1
show less
Detected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot ...
show moreDetected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot / scanner behavior). Hits from same IP in last 60 minutes: 1. Unique request paths counted internally: 1. Cloudflare action: managed_challenge. Cloudflare source: botFight.
show less
Detected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot ...
show moreDetected by Cloudflare Security Events via WordPress automation. Detection: bad_bot_scanner (Bad bot / scanner behavior). Hits from same IP in last 60 minutes: 1. Unique request paths counted internally: 1. Cloudflare action: managed_challenge. Cloudflare source: botFight.
show less
