Log in to view charts and search reports for this IP.
Log In
No reports in the last 60 days
20.213.108.138 has been reported 73
times. The most recent report is from
.
The full history is preserved below and remains searchable. A
0% score reflects the absence of recent activity, but
this is not a guarantee that earlier reports were invalid. Abuse confidence score decays,
naturally, over time, when the abusive activity stops.
IP Abuse Reports for 20.213.108.138:
This IP address has been reported a total of
73
times from
46 distinct
sources.
20.213.108.138 was first reported on
, and the most recent report was
.
72 requests, including :
GET /404.php HTTP/1.1
GET /x.php HTTP/1.1
GET /o.php HTTP/1.1
GET /100.php ...
show more72 requests, including :
GET /404.php HTTP/1.1
GET /x.php HTTP/1.1
GET /o.php HTTP/1.1
GET /100.php HTTP/1.1
GET /templates/beez5/index.php HTTP/1.1
GET /i.php HTTP/1.1
GET /2index.php HTTP/1.1
GET /wp-admin/includes/class-wp-media-list-data.php HTTP/1.1
GET /wp-uploads.php HTTP/1.1
GET /0z.php HTTP/1.1
GET /mini.php HTTP/1.1
GET /k.php HTTP/1.1
GET /wp-content/themes/seotheme/mar.php HTTP/1.1
GET /WSO.php HTTP/1.1
GET /wikindex.php HTTP/1.1
GET /13.php HTTP/1.1
GET /sh.php HTTP/1.1
GET /mari.php HTTP/1.1
GET /y.php HTTP/1.1
show less
(apache-scanners) Failed apache-scanners trigger with match [redacted] from 20.213.108.138 (AU/Austr ...
show more(apache-scanners) Failed apache-scanners trigger with match [redacted] from 20.213.108.138 (AU/Australia/-)
show less
(apache-scanners) Failed apache-scanners trigger with match [redacted] from 20.213.108.138 (AU/Austr ...
show more(apache-scanners) Failed apache-scanners trigger with match [redacted] from 20.213.108.138 (AU/Australia/-)
show less