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 42.49.82.45
This IP address has been reported a total of
16
times from
12 distinct
sources.
42.49.82.45 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 6
reports;
France
with 2
reports;
United Kingdom of Great Britain and Northern Ireland
with 2
reports.
The most common categories in these recent reports were:
Web App Attack
13
times;
Hacking
5
times;
Brute-Force
5
times;
Bad Web Bot
3
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.
This address requests our sites over plain http, is answered with a redirect to https, and never fol ...
show moreThis address requests our sites over plain http, is answered with a redirect to https, and never follows it — over and over. A browser follows redirects; a scanner enumerating hosts does not. It reads nothing it asks for and only loads the server; blocked. Please check what runs on this address. | method: GET | path: /wp-content/plugins/social-icons-widget-by-wpzoom/readme.txt (+2 more) | 2026-09-26 10:26 UTC
show less
This address keeps sending requests that the sites' own web application firewall refuses — attack pa ...
show moreThis address keeps sending requests that the sites' own web application firewall refuses — attack payloads, forbidden paths — again and again. One refusal is a mistake; a series is an attack tool at work. Blocked; please check the machine behind it. | method: GET | path: /wp-content/plugins/login-designer/readme.txt (+5 more) | 2026-09-25 10:22 UTC
show less
This address keeps sending requests that the sites' own web application firewall refuses — attack pa ...
show moreThis address keeps sending requests that the sites' own web application firewall refuses — attack payloads, forbidden paths — again and again. One refusal is a mistake; a series is an attack tool at work. Blocked; please check the machine behind it. | method: GET | path: /wp-content/plugins/event-organiser/readme.txt (+4 more) | 2026-09-22 20:00 UTC
show less
