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

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

;; QUESTION SECTION:
;125.42.216.146.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 11 23:59:34 CST 2022
;; MSG SIZE  rcvd: 107
Host info
146.216.42.125.in-addr.arpa domain name pointer hn.kd.ny.adsl.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
146.216.42.125.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
162.105.92.98 attack
May 23 04:44:49 server sshd\[118914\]: Invalid user tomcat from 162.105.92.98
May 23 04:44:49 server sshd\[118914\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.105.92.98
May 23 04:44:51 server sshd\[118914\]: Failed password for invalid user tomcat from 162.105.92.98 port 56494 ssh2
...
2019-07-11 22:23:06
81.22.45.63 attackspambots
TCP 3389 (RDP)
2019-07-11 22:52:10
160.218.185.67 attackbotsspam
May 26 02:08:07 server sshd\[233643\]: Invalid user mou from 160.218.185.67
May 26 02:08:07 server sshd\[233643\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=160.218.185.67
May 26 02:08:09 server sshd\[233643\]: Failed password for invalid user mou from 160.218.185.67 port 49036 ssh2
...
2019-07-11 22:26:52
159.89.199.236 attackspambots
Apr  9 17:55:35 server sshd\[40658\]: Invalid user applmgr from 159.89.199.236
Apr  9 17:55:35 server sshd\[40658\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.199.236
Apr  9 17:55:36 server sshd\[40658\]: Failed password for invalid user applmgr from 159.89.199.236 port 58902 ssh2
...
2019-07-11 22:37:51
103.218.3.124 attack
Jul 11 14:17:39 MK-Soft-VM4 sshd\[18164\]: Invalid user test from 103.218.3.124 port 52072
Jul 11 14:17:39 MK-Soft-VM4 sshd\[18164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.218.3.124
Jul 11 14:17:41 MK-Soft-VM4 sshd\[18164\]: Failed password for invalid user test from 103.218.3.124 port 52072 ssh2
...
2019-07-11 22:37:04
91.225.20.20 attackspambots
[portscan] Port scan
2019-07-11 22:54:37
36.92.44.202 attackspam
ssh failed login
2019-07-11 22:14:59
139.59.44.60 attack
Triggered by Fail2Ban at Vostok web server
2019-07-11 22:13:18
159.89.204.28 attack
Jul  8 06:44:47 server sshd\[80330\]: Invalid user ftpuser from 159.89.204.28
Jul  8 06:44:47 server sshd\[80330\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.204.28
Jul  8 06:44:49 server sshd\[80330\]: Failed password for invalid user ftpuser from 159.89.204.28 port 58620 ssh2
...
2019-07-11 22:37:32
1.255.242.238 attackbots
$f2bV_matches
2019-07-11 22:27:39
74.73.145.47 attackspambots
Jul 11 12:43:48 OPSO sshd\[911\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.73.145.47  user=root
Jul 11 12:43:50 OPSO sshd\[911\]: Failed password for root from 74.73.145.47 port 46389 ssh2
Jul 11 12:47:38 OPSO sshd\[1234\]: Invalid user minera from 74.73.145.47 port 52612
Jul 11 12:47:38 OPSO sshd\[1234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=74.73.145.47
Jul 11 12:47:40 OPSO sshd\[1234\]: Failed password for invalid user minera from 74.73.145.47 port 52612 ssh2
2019-07-11 22:10:13
172.110.30.30 attackspam
445/tcp 445/tcp 445/tcp...
[2019-05-13/07-11]16pkt,1pt.(tcp)
2019-07-11 22:02:57
117.102.88.119 attackspambots
2019-07-11T14:55:19.626623lon01.zurich-datacenter.net sshd\[13306\]: Invalid user sentry from 117.102.88.119 port 42106
2019-07-11T14:55:19.632263lon01.zurich-datacenter.net sshd\[13306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.102.88.119
2019-07-11T14:55:21.745860lon01.zurich-datacenter.net sshd\[13306\]: Failed password for invalid user sentry from 117.102.88.119 port 42106 ssh2
2019-07-11T14:59:14.297905lon01.zurich-datacenter.net sshd\[13358\]: Invalid user tommy from 117.102.88.119 port 47566
2019-07-11T14:59:14.302270lon01.zurich-datacenter.net sshd\[13358\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.102.88.119
...
2019-07-11 22:12:39
159.89.28.170 attack
Apr 23 20:10:23 server sshd\[90670\]: Invalid user gitlab from 159.89.28.170
Apr 23 20:10:23 server sshd\[90670\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.28.170
Apr 23 20:10:25 server sshd\[90670\]: Failed password for invalid user gitlab from 159.89.28.170 port 44018 ssh2
...
2019-07-11 22:31:11
184.105.247.194 attackbots
SMB Server BruteForce Attack
2019-07-11 21:55:42

Recently Reported IPs

125.41.9.48 125.43.64.175 125.43.139.67 125.44.13.202
125.42.15.196 125.44.199.79 125.43.81.114 125.43.73.254
125.44.235.236 125.44.195.238 125.44.46.65 125.44.21.131
125.44.48.116 125.45.122.62 125.45.18.202 125.44.31.64
125.46.182.36 125.45.49.18 125.47.84.89 125.47.83.6