Recent Activity
This IP has received recent abuse reports, which causes the score to increase.
IPv6 SLAAC Note
Public IPv6 addresses may implement the SLAAC
privacy extension. With SLAAC, the interface identifier is randomly generated. SLAAC also implements a
configurable time out, so that the original IPv6 interface addresses will be discarded in favor of a new
interface identifier.
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 2a01:4020:31:0:101::8
This IP address has been reported a total of
5
times from
5 distinct
sources.
2a01:4020:31:0:101::8 was first reported on
, and the most recent report was
.
In the last 60 days, the top reporter locations were:
United States of America
with 2
reports;
Canada
with 1
report;
Hong Kong
with 1
report.
The most common categories in these recent reports were:
Port Scan
4
times;
Brute-Force
1
time;
Hacking
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.
2026-09-23T15:06:55.370503+00:00 Canada1 postfix/smtps/smtpd[780632]: NOQUEUE: lost connection after ...
show more2026-09-23T15:06:55.370503+00:00 Canada1 postfix/smtps/smtpd[780632]: NOQUEUE: lost connection after CONNECT from unknown[2a01:4020:31:0:101::8]
2026-09-23T15:08:06.710939+00:00 Canada1 postfix/smtpd[811559]: NOQUEUE: lost connection after CONNECT from unknown[2a01:4020:31:0:101::8]
...
show less
Blocked by UFW on hk [9080/tcp]
Source port: 47978
TTL: null
Packet length: 60
TOS: null
This repor ...
show moreBlocked by UFW on hk [9080/tcp]
Source port: 47978
TTL: null
Packet length: 60
TOS: null
This report was generated by:
https://github.com/sefinek/UFW-AbuseIPDB-Reporter
show less