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 141.101.98.136
This IP address has been reported a total of
208
times from
41 distinct
sources.
141.101.98.136 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Belgium
with 3
reports;
United States of America
with 3
reports;
Germany
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
11
times;
Bad Web Bot
5
times;
Brute-Force
3
times;
Exploited Host
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.
[26/Sep/2026:16:48:20 +0300] -- 141.101.98.136 Ban reason: Scanner [CMS_GENERIC] | Request: GET /wp- ...
show more[26/Sep/2026:16:48:20 +0300] -- 141.101.98.136 Ban reason: Scanner [CMS_GENERIC] | Request: GET /wp-config.php HTTP/1.1
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
