This IP address has been reported a total of
16
times from
16 distinct
sources.
54.81.195.152 was first reported on
, and the most recent report was
.
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.
Reporter
IoA Timestamp (UTC)
Comment
Categories
Anonymous
postfix sasl authentication failure blocked by fail2ban
...
Sep 13 00:34:24 ksol postfix/submission-587/smtpd[92389]: NOQUEUE: reject: CONNECT from ec2-54-81-19 ...
show moreSep 13 00:34:24 ksol postfix/submission-587/smtpd[92389]: NOQUEUE: reject: CONNECT from ec2-54-81-195-152.compute-1.amazonaws.com[54.81.195.152]:52802: 554 5.7.1 Service unavailable; Client host [54.81.195.152] blocked using sbl-xbl.spamhaus.org; Listed by XBL, see https://check.spamhaus.org/query/ip/54.81.195.152 / Listed by CSS, see https://check.spamhaus.org/query/ip/54.81.195.152; proto=SMTP
Sep 13 00:34:24 ksol postfix/submission-587/smtpd[92389]: NOQUEUE: lost connection after CONNECT from ec2-54-81-195-152.compute-1.amazonaws.com[54.81.195.152]:52802
...
show less
2026-09-12 22:32:43 TLS error on connection from ec2-54-81-195-152.compute-1.amazonaws.com (EC2AMAZ- ...
show more2026-09-12 22:32:43 TLS error on connection from ec2-54-81-195-152.compute-1.amazonaws.com (EC2AMAZ-PRU9TCD.ec2.internal) [54.81.195.152] (recv): The TLS connection was non-properly terminated.
2026-09-12 22:32:44 TLS error on connection from ec2-54-81-195-152.compute-1.amazonaws.com [54.81.195.152] (gnutls_handshake): The TLS connection was non-properly terminated.
...
show less
Cloudmax IPS Block - Suspicious activity. Possible port scanning, service reconnaissance, or vulnera ...
show moreCloudmax IPS Block - Suspicious activity. Possible port scanning, service reconnaissance, or vulnerability probing
show less