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: China

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 <<>> 45.125.97.224
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55570
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.125.97.224.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 21:28:23 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 224.97.125.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 224.97.125.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
14.140.210.30 attackspam
1581545978 - 02/12/2020 23:19:38 Host: 14.140.210.30/14.140.210.30 Port: 445 TCP Blocked
2020-02-13 07:21:05
194.26.29.124 attackbotsspam
Portscan or hack attempt detected by psad/fwsnort
2020-02-13 06:58:12
185.176.27.178 attackspambots
Feb 13 00:12:27 debian-2gb-nbg1-2 kernel: \[3808376.338320\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.178 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=4918 PROTO=TCP SPT=46621 DPT=25964 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-13 07:17:28
106.13.78.180 attackbotsspam
Feb 12 23:20:00 srv206 sshd[23356]: Invalid user rolex from 106.13.78.180
Feb 12 23:20:00 srv206 sshd[23356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.78.180
Feb 12 23:20:00 srv206 sshd[23356]: Invalid user rolex from 106.13.78.180
Feb 12 23:20:02 srv206 sshd[23356]: Failed password for invalid user rolex from 106.13.78.180 port 45088 ssh2
...
2020-02-13 07:06:27
51.159.35.140 attack
51.159.35.140 was recorded 8 times by 8 hosts attempting to connect to the following ports: 389. Incident counter (4h, 24h, all-time): 8, 15, 31
2020-02-13 07:12:36
106.53.88.247 attackspambots
Invalid user blake from 106.53.88.247 port 59534
2020-02-13 07:04:51
201.251.237.2 attack
Rude login attack (2 tries in 1d)
2020-02-13 07:33:06
112.126.100.76 attack
Feb 12 13:00:34 web9 sshd\[2797\]: Invalid user fava from 112.126.100.76
Feb 12 13:00:34 web9 sshd\[2797\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.126.100.76
Feb 12 13:00:35 web9 sshd\[2797\]: Failed password for invalid user fava from 112.126.100.76 port 34660 ssh2
Feb 12 13:04:34 web9 sshd\[3372\]: Invalid user 1qazwsx from 112.126.100.76
Feb 12 13:04:34 web9 sshd\[3372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.126.100.76
2020-02-13 07:08:06
190.64.64.74 attackspambots
Feb 12 14:38:13 home sshd[18266]: Invalid user scheduler from 190.64.64.74 port 37365
Feb 12 14:38:13 home sshd[18266]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.64.64.74
Feb 12 14:38:13 home sshd[18266]: Invalid user scheduler from 190.64.64.74 port 37365
Feb 12 14:38:16 home sshd[18266]: Failed password for invalid user scheduler from 190.64.64.74 port 37365 ssh2
Feb 12 15:11:08 home sshd[18449]: Invalid user hadoop from 190.64.64.74 port 5388
Feb 12 15:11:08 home sshd[18449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.64.64.74
Feb 12 15:11:08 home sshd[18449]: Invalid user hadoop from 190.64.64.74 port 5388
Feb 12 15:11:10 home sshd[18449]: Failed password for invalid user hadoop from 190.64.64.74 port 5388 ssh2
Feb 12 15:13:59 home sshd[18469]: Invalid user mother from 190.64.64.74 port 23312
Feb 12 15:13:59 home sshd[18469]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r
2020-02-13 07:13:53
112.85.42.188 attackspambots
02/12/2020-18:31:18.750639 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan
2020-02-13 07:32:50
37.139.1.197 attackbots
Invalid user ceq from 37.139.1.197 port 53116
2020-02-13 06:59:56
218.57.140.130 attack
Feb 12 23:52:01 cp sshd[21459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.57.140.130
Feb 12 23:52:01 cp sshd[21459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.57.140.130
2020-02-13 07:28:39
222.186.30.76 attackbots
Feb 12 23:53:19 amit sshd\[5203\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
Feb 12 23:53:21 amit sshd\[5203\]: Failed password for root from 222.186.30.76 port 61264 ssh2
Feb 12 23:56:36 amit sshd\[5246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76  user=root
...
2020-02-13 07:01:52
46.125.250.72 attack
Bitte überprüfen
2020-02-13 07:27:57
195.162.96.133 attack
Telnet/23 MH Probe, BF, Hack -
2020-02-13 07:30:19

Recently Reported IPs

234.46.236.110 148.94.69.98 231.216.203.132 73.194.62.154
187.145.65.236 19.122.232.255 2.218.53.34 53.129.8.226
63.246.187.74 29.198.151.235 247.150.29.183 131.21.85.65
38.41.190.116 24.113.98.50 235.176.13.174 184.82.210.37
214.17.149.76 192.138.162.176 163.59.86.163 56.84.70.101