Check an IP Address, Domain Name, or Subnet

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


User Grudgingchough joined AbuseIPDB in January 2023 and has reported 11,128 IP addresses.

Standing (weight) is good.

ACTIVE USER
IP Date Comment Categories
196.191.133.234
tcp/80
Port Scan
198.199.94.6
Port 1080 bad connection
Brute-Force SSH
172.68.49.223
Not authorized
Brute-Force
1.22.168.224
Abuse Center SSH
Scanned Port 8080
Port Scan SSH
165.73.252.69
Fail2Ban automatic report
Brute-Force
36.237.117.39
Unauthorized Connection To 3389
Port Scan SSH
111.255.28.154
Attempted from 111.255.28.154
Failed Attempt to get in to server
Port Scan Brute-Force SSH
216.201.9.164
Automatic ban Fail2ban
Port Scan Brute-Force
64.62.197.29
Reported By Github AbuseIPDB Reporter, failed attempt connection
Port Scan Brute-Force SSH
1.170.117.77
Failed password to root
Port Scan Brute-Force SSH
13.52.80.8
Hacking/Portscan
Port Scan
122.116.24.161
Reported By Github AbuseIPDB Reporter, failed attempt connection
Brute-Force
45.134.140.181
Scanning detected 45.134.140.181
Brute-Force SSH
119.65.52.209
119.65.52.209 Recorded Scanning
Brute-Force
223.13.25.188
223.13.25.188 Recorded Scanning
Port Scan Brute-Force SSH
59.126.232.143
Automatic ban Fail2ban
Port Scan
189.219.64.66
Global network scanner(zmap) TCP port22
Abuser 189.219.64.66
Port Scan Brute-Force SSH
98.166.148.187
Reported By Github AbuseIPDB Reporter, failed attempt connection
Port Scan Brute-Force SSH
213.16.178.66
Blocked by UFW - Port 443
Brute-Force
223.8.189.150
Reported By Github AbuseIPDB Reporter, failed attempt connection
Brute-Force SSH
61.74.89.3
Malicous connection port 23
Possible brute force
Port Scan Brute-Force
125.228.79.245
Illegal Port Scanning
Port Scan
122.254.16.250
Abuse Center SSH
Scanned Port 23
Brute-Force SSH
118.166.71.131
Malicous connection port 443
Possible brute force
Port Scan SSH
118.171.13.136
TCP-Scanner. Port: 80
Port Scan Brute-Force SSH
** This Document Provided By AbuseIPDB **
Source: https://www.abuseipdb.com