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: United States of America (the)

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

;; QUESTION SECTION:
;29.162.245.125.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 08 23:42:36 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 125.245.162.29.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 125.245.162.29.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
142.93.210.218 attack
Feb 27 15:10:03 iago sshd[3914]: Invalid user narciso from 142.93.210.218
Feb 27 15:10:03 iago sshd[3914]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.210.218 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=142.93.210.218
2020-02-28 04:08:44
89.248.160.150 attackbots
89.248.160.150 was recorded 24 times by 14 hosts attempting to connect to the following ports: 40854,40850. Incident counter (4h, 24h, all-time): 24, 153, 5685
2020-02-28 03:57:00
5.253.26.142 attackspambots
Feb 27 11:21:19 ws24vmsma01 sshd[133346]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.253.26.142
Feb 27 11:21:21 ws24vmsma01 sshd[133346]: Failed password for invalid user dspace from 5.253.26.142 port 51514 ssh2
...
2020-02-28 04:08:19
74.63.237.218 attack
Port 2169 scan denied
2020-02-28 04:23:45
96.47.10.53 attack
Feb 27 20:41:28 vps691689 sshd[1913]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=96.47.10.53
Feb 27 20:41:31 vps691689 sshd[1913]: Failed password for invalid user liuzhenfeng from 96.47.10.53 port 56019 ssh2
...
2020-02-28 04:02:11
221.156.126.1 attackspam
2020-02-27T15:26:28.641797randservbullet-proofcloud-66.localdomain sshd[11265]: Invalid user debian-spamd from 221.156.126.1 port 51836
2020-02-27T15:26:28.648188randservbullet-proofcloud-66.localdomain sshd[11265]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.156.126.1
2020-02-27T15:26:28.641797randservbullet-proofcloud-66.localdomain sshd[11265]: Invalid user debian-spamd from 221.156.126.1 port 51836
2020-02-27T15:26:30.487732randservbullet-proofcloud-66.localdomain sshd[11265]: Failed password for invalid user debian-spamd from 221.156.126.1 port 51836 ssh2
...
2020-02-28 03:52:07
113.172.227.165 attack
20/2/27@09:21:33: FAIL: Alarm-Network address from=113.172.227.165
...
2020-02-28 03:58:20
174.60.121.175 attack
Feb 27 09:59:03 web1 sshd\[26663\]: Invalid user sito from 174.60.121.175
Feb 27 09:59:03 web1 sshd\[26663\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.60.121.175
Feb 27 09:59:05 web1 sshd\[26663\]: Failed password for invalid user sito from 174.60.121.175 port 47634 ssh2
Feb 27 10:07:56 web1 sshd\[27434\]: Invalid user noc from 174.60.121.175
Feb 27 10:07:56 web1 sshd\[27434\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.60.121.175
2020-02-28 04:21:57
119.254.12.66 attackspambots
$f2bV_matches
2020-02-28 04:00:29
94.203.254.248 attackspam
$f2bV_matches
2020-02-28 04:17:12
170.84.105.71 attackbots
Automatic report - Port Scan Attack
2020-02-28 04:10:42
92.118.37.99 attackbots
Automatic report - Port Scan
2020-02-28 04:11:57
111.241.120.32 attackbotsspam
suspicious action Thu, 27 Feb 2020 11:21:26 -0300
2020-02-28 04:05:35
95.61.92.185 attackspambots
Feb 27 15:21:21 pmg postfix/postscreen\[32524\]: NOQUEUE: reject: RCPT from \[95.61.92.185\]:37424: 550 5.7.1 Service unavailable\; client \[95.61.92.185\] blocked using zen.spamhaus.org\; from=\, to=\, proto=ESMTP, helo=\
2020-02-28 04:09:41
84.38.180.44 attackbotsspam
Lines containing failures of 84.38.180.44
Feb 27 10:09:54 UTC__SANYALnet-Labs__cac1 sshd[4606]: Connection from 84.38.180.44 port 51318 on 104.167.106.93 port 22
Feb 27 10:09:55 UTC__SANYALnet-Labs__cac1 sshd[4606]: Address 84.38.180.44 maps to rm01.ru, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Feb 27 10:09:55 UTC__SANYALnet-Labs__cac1 sshd[4606]: Invalid user at from 84.38.180.44 port 51318
Feb 27 10:09:55 UTC__SANYALnet-Labs__cac1 sshd[4606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.38.180.44
Feb 27 10:09:57 UTC__SANYALnet-Labs__cac1 sshd[4606]: Failed password for invalid user at from 84.38.180.44 port 51318 ssh2
Feb 27 10:09:57 UTC__SANYALnet-Labs__cac1 sshd[4606]: Received disconnect from 84.38.180.44 port 51318:11: Bye Bye [preauth]
Feb 27 10:09:57 UTC__SANYALnet-Labs__cac1 sshd[4606]: Disconnected from 84.38.180.44 port 51318 [preauth]
Feb 27 10:36:11 UTC__SANYALnet-Labs__cac1 sshd[5320........
------------------------------
2020-02-28 04:15:08

Recently Reported IPs

122.82.178.79 252.0.185.226 232.51.100.236 154.82.153.109
244.205.217.135 148.168.251.41 198.155.35.163 130.192.230.138
219.42.2.93 23.140.153.130 106.22.93.235 99.127.45.128
241.207.36.200 7.15.235.98 204.184.218.15 159.89.217.133
88.140.48.39 9.8.253.217 52.40.36.38 29.8.128.40