Check an IP Address, Domain Name, or Subnet

e.g. 44.200.168.16, microsoft.com, or 5.188.10.0/24


User Needysausage joined AbuseIPDB in January 2023 and has reported 11,160 IP addresses.

Standing (weight) is good.

ACTIVE USER
IP Date Comment Categories
138.59.35.23
Blocked by UFW - Port 22
Port Scan Brute-Force SSH
174.107.241.127
Port 22 bad connection
Brute-Force
172.70.97.42
Not authorized
SSH
14.252.13.128
Abuse Center SSH
Scanned Port 3389
Port Scan
42.119.1.89
Illegal Port Scanning
Port Scan SSH
189.93.9.122
Abuse SRC=189.93.9.122 DST=22
Brute-Force SSH
115.48.26.236
Is not allowed to connect @ tcp 80
Port Scan Brute-Force SSH
120.85.185.75
Attempted from 120.85.185.75
Failed Attempt to get in to server
SSH
101.206.176.69
TCP port scan.
SSH
88.153.67.74
Malicous connection port 80
Possible brute force
Port Scan Brute-Force
89.133.25.68
Network UFW ban
Brute-Force SSH
112.113.235.56
Network UFW ban
Brute-Force
44.192.23.228
Hacking/Portscan
Port Scan Brute-Force
1.64.4.38
Automatic ban Fail2ban
Brute-Force
175.175.61.234
Port 3389 bad connection
Port Scan Brute-Force
180.94.150.9
Unauthorized Connection To 21
Port Scan Brute-Force SSH
39.102.204.106
Malicous connection port 80
Possible brute force
Brute-Force SSH
162.158.21.87
Fail2Ban automatic report
Port Scan
60.169.251.180
Port Sweep SRC=60.169.251.180
Brute-Force SSH
87.236.176.139
Spam 87.236.176.139
Brute-Force
117.241.125.138
Invalid connection from 117.241.125.138
Not allowed when not authorized
Port Scan Brute-Force
60.54.136.115
Abuse Report
Port Scan Brute-Force SSH
173.8.38.21
TCP port scan.
Brute-Force
34.85.244.200
Port Sweep SRC=34.85.244.200
Brute-Force SSH
123.175.102.104
Is not allowed to connect @ tcp 23
Port Scan SSH
** This Document Provided By AbuseIPDB **
Source: https://www.abuseipdb.com