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
59
times from
24 distinct
sources.
51.81.163.30 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
Germany
with 21
reports;
Canada
with 12
reports;
United States of America
with 8
reports.
The most common categories in these recent reports were:
Bad Web Bot
41
times;
Brute-Force
9
times;
Web App Attack
9
times;
Exploited Host
7
times;
DDoS Attack
6
times;
Other
11
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.
Report for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET /robots.txt [DOMAI ...
show moreReport for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET /robots.txt [DOMAIN_REMOVED] 200 5738 - Mozilla/5.0 (compatible; AhrefsBot/7.0; +[DOMAIN_REMOVED]
show less
Web vulnerability scanning / probing from 51.81.163.30: automated requests for CMS admin paths, logi ...
show moreWeb vulnerability scanning / probing from 51.81.163.30: automated requests for CMS admin paths, login endpoints, xmlrpc, and common scanner fingerprints over HTTPS. 1 hits; paths: /books/index.html.
show less
Blocked abusive HTTP application-layer DoS / botnet traffic from 51.81.163.30: traffic from this add ...
show moreBlocked abusive HTTP application-layer DoS / botnet traffic from 51.81.163.30: traffic from this address continues high-cost dynamic page and feed requests at abusive rates via TCP/HTTPS despite edge block responses. Likely compromised end-user host.
show less
(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/Uni ...
show more(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/United States/proxy-us-west000-cip15.ahrefs.net)
show less
(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/Uni ...
show more(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/United States/proxy-us-west000-cip15.ahrefs.net)
show less
Fail2ban automatic report for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET ...
show moreFail2ban automatic report for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET /robots.txt [DOMAIN_REMOVED] 200 5738 - Mozilla/5.0 (compatible; AhrefsBot/7.0; +[DOMAIN_REMOVED]
show less
Fail2ban automatic report for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET ...
show moreFail2ban automatic report for plesk-apache-badbot: 51.81.163.30 - - [13/Oct/2026:20:46:15 +0200] GET /robots.txt [DOMAIN_REMOVED] 200 5738 - Mozilla/5.0 (compatible; AhrefsBot/7.0; +[DOMAIN_REMOVED]
show less
(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/Uni ...
show more(apache-useragents) Failed apache-useragents trigger with match [redacted] from 51.81.163.30 (US/United States/proxy-us-west000-cip15.ahrefs.net)
show less
