Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: IANA Special-Purpose Address

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 252.189.242.97
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55099
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;252.189.242.97.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025021002 1800 900 604800 86400

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 08:00:36 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 97.242.189.252.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 97.242.189.252.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
1.180.226.242 attack
Fail2Ban - FTP Abuse Attempt
2019-11-10 16:25:19
80.82.77.139 attackbotsspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-11-10 16:14:50
178.127.24.20 attack
failed_logins
2019-11-10 16:09:10
188.143.91.142 attackspambots
Nov 10 07:23:40 work-partkepr sshd\[6235\]: Invalid user myassetreport from 188.143.91.142 port 59868
Nov 10 07:23:40 work-partkepr sshd\[6235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.143.91.142
...
2019-11-10 16:27:54
196.43.196.108 attackspam
5x Failed Password
2019-11-10 16:06:15
212.237.51.190 attack
Nov  9 21:53:16 web1 sshd\[20670\]: Invalid user i89op0 from 212.237.51.190
Nov  9 21:53:16 web1 sshd\[20670\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.51.190
Nov  9 21:53:17 web1 sshd\[20670\]: Failed password for invalid user i89op0 from 212.237.51.190 port 37046 ssh2
Nov  9 21:57:04 web1 sshd\[21050\]: Invalid user bosco from 212.237.51.190
Nov  9 21:57:04 web1 sshd\[21050\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.51.190
2019-11-10 16:03:22
101.124.6.112 attackspam
2019-11-10T08:31:13.282889  sshd[14626]: Invalid user transam from 101.124.6.112 port 53934
2019-11-10T08:31:13.297099  sshd[14626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.124.6.112
2019-11-10T08:31:13.282889  sshd[14626]: Invalid user transam from 101.124.6.112 port 53934
2019-11-10T08:31:14.733875  sshd[14626]: Failed password for invalid user transam from 101.124.6.112 port 53934 ssh2
2019-11-10T08:35:28.591797  sshd[14665]: Invalid user !!@#qweASD from 101.124.6.112 port 57486
...
2019-11-10 16:22:23
157.245.95.69 attackspambots
Nov 10 07:30:14 srv1 sshd[7472]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.95.69
Nov 10 07:30:15 srv1 sshd[7472]: Failed password for invalid user adrien from 157.245.95.69 port 42030 ssh2
...
2019-11-10 16:44:19
219.148.37.34 attack
$f2bV_matches
2019-11-10 16:19:49
164.132.104.58 attackspambots
Nov 10 10:07:19 server sshd\[3229\]: Invalid user glenn from 164.132.104.58
Nov 10 10:07:19 server sshd\[3229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.ip-164-132-104.eu 
Nov 10 10:07:21 server sshd\[3229\]: Failed password for invalid user glenn from 164.132.104.58 port 33488 ssh2
Nov 10 10:30:10 server sshd\[9602\]: Invalid user login from 164.132.104.58
Nov 10 10:30:10 server sshd\[9602\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.ip-164-132-104.eu 
...
2019-11-10 16:30:49
112.121.163.11 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-10 16:12:16
46.101.73.64 attackbots
Nov  9 21:51:38 sachi sshd\[17308\]: Invalid user hero from 46.101.73.64
Nov  9 21:51:38 sachi sshd\[17308\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.73.64
Nov  9 21:51:40 sachi sshd\[17308\]: Failed password for invalid user hero from 46.101.73.64 port 50952 ssh2
Nov  9 21:54:57 sachi sshd\[17604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.73.64  user=root
Nov  9 21:54:58 sachi sshd\[17604\]: Failed password for root from 46.101.73.64 port 59802 ssh2
2019-11-10 16:16:27
139.155.118.190 attackbots
Nov  9 22:15:20 auw2 sshd\[975\]: Invalid user cache@123 from 139.155.118.190
Nov  9 22:15:20 auw2 sshd\[975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.118.190
Nov  9 22:15:22 auw2 sshd\[975\]: Failed password for invalid user cache@123 from 139.155.118.190 port 37154 ssh2
Nov  9 22:19:50 auw2 sshd\[1382\]: Invalid user adya from 139.155.118.190
Nov  9 22:19:50 auw2 sshd\[1382\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.118.190
2019-11-10 16:21:05
5.188.206.14 attack
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-11-10 16:18:29
60.170.38.145 attackbotsspam
firewall-block, port(s): 23/tcp
2019-11-10 16:37:59

Recently Reported IPs

92.221.138.84 5.69.171.23 6.206.65.252 228.232.1.208
129.85.70.41 169.52.39.69 86.172.47.4 79.147.121.175
181.225.251.34 179.153.128.135 202.28.246.220 24.149.152.117
33.198.147.193 52.176.151.230 244.92.50.71 212.164.138.22
42.222.242.211 27.219.32.75 200.163.149.182 184.92.182.226