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

;; QUESTION SECTION:
;139.8.72.97.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 14:23:18 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 97.72.8.139.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.72.8.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
89.248.174.193 attack
10/28/2019-12:53:41.843506 89.248.174.193 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-10-28 20:41:23
176.170.43.17 attack
SSH Scan
2019-10-28 20:27:06
132.148.129.180 attackspambots
Oct 28 03:20:37 Ubuntu-1404-trusty-64-minimal sshd\[24557\]: Invalid user zimbra from 132.148.129.180
Oct 28 03:20:37 Ubuntu-1404-trusty-64-minimal sshd\[24557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.148.129.180
Oct 28 03:20:39 Ubuntu-1404-trusty-64-minimal sshd\[24557\]: Failed password for invalid user zimbra from 132.148.129.180 port 46446 ssh2
Oct 28 12:59:44 Ubuntu-1404-trusty-64-minimal sshd\[32072\]: Invalid user usuario from 132.148.129.180
Oct 28 12:59:44 Ubuntu-1404-trusty-64-minimal sshd\[32072\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.148.129.180
2019-10-28 20:31:25
144.34.224.6 attackspam
2019-10-28T11:54:05.515588abusebot-8.cloudsearch.cf sshd\[13565\]: Invalid user 1q2a3z from 144.34.224.6 port 35694
2019-10-28 20:20:03
51.75.147.100 attack
Oct 28 11:45:56 ip-172-31-62-245 sshd\[9780\]: Invalid user idc2 from 51.75.147.100\
Oct 28 11:45:58 ip-172-31-62-245 sshd\[9780\]: Failed password for invalid user idc2 from 51.75.147.100 port 54244 ssh2\
Oct 28 11:49:46 ip-172-31-62-245 sshd\[9795\]: Invalid user cn from 51.75.147.100\
Oct 28 11:49:48 ip-172-31-62-245 sshd\[9795\]: Failed password for invalid user cn from 51.75.147.100 port 37962 ssh2\
Oct 28 11:53:34 ip-172-31-62-245 sshd\[9818\]: Invalid user tighten from 51.75.147.100\
2019-10-28 20:48:58
182.73.65.26 attackbots
Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2019-10-28 20:18:51
5.141.166.146 attackbots
Chat Spam
2019-10-28 20:44:15
142.93.212.168 attackbots
Oct 28 11:44:54 ip-172-31-62-245 sshd\[9771\]: Invalid user wletc04 from 142.93.212.168\
Oct 28 11:44:56 ip-172-31-62-245 sshd\[9771\]: Failed password for invalid user wletc04 from 142.93.212.168 port 33222 ssh2\
Oct 28 11:49:20 ip-172-31-62-245 sshd\[9793\]: Invalid user 1234@Qwer from 142.93.212.168\
Oct 28 11:49:22 ip-172-31-62-245 sshd\[9793\]: Failed password for invalid user 1234@Qwer from 142.93.212.168 port 43354 ssh2\
Oct 28 11:53:49 ip-172-31-62-245 sshd\[9828\]: Invalid user Puckett from 142.93.212.168\
2019-10-28 20:33:04
222.72.135.177 attackspambots
2019-10-28T12:25:28.181773abusebot-5.cloudsearch.cf sshd\[17015\]: Invalid user waggoner from 222.72.135.177 port 42802
2019-10-28 20:32:47
170.82.40.69 attack
Oct 28 12:07:38 venus sshd\[3438\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.82.40.69  user=root
Oct 28 12:07:40 venus sshd\[3438\]: Failed password for root from 170.82.40.69 port 34330 ssh2
Oct 28 12:12:06 venus sshd\[3555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.82.40.69  user=root
...
2019-10-28 20:30:23
117.85.48.122 attackbots
Oct 28 07:54:02 esmtp postfix/smtpd[19671]: lost connection after AUTH from unknown[117.85.48.122]
Oct 28 07:54:03 esmtp postfix/smtpd[19671]: lost connection after AUTH from unknown[117.85.48.122]
Oct 28 07:54:05 esmtp postfix/smtpd[19671]: lost connection after AUTH from unknown[117.85.48.122]
Oct 28 07:54:06 esmtp postfix/smtpd[19671]: lost connection after AUTH from unknown[117.85.48.122]
Oct 28 07:54:08 esmtp postfix/smtpd[19671]: lost connection after AUTH from unknown[117.85.48.122]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=117.85.48.122
2019-10-28 20:16:37
182.34.210.173 attackspambots
Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2019-10-28 20:30:55
82.196.14.222 attackspam
2019-10-28T11:46:30.035461shield sshd\[8054\]: Invalid user wiki from 82.196.14.222 port 52088
2019-10-28T11:46:30.039636shield sshd\[8054\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.14.222
2019-10-28T11:46:32.103548shield sshd\[8054\]: Failed password for invalid user wiki from 82.196.14.222 port 52088 ssh2
2019-10-28T11:56:17.722192shield sshd\[9934\]: Invalid user eugen from 82.196.14.222 port 46099
2019-10-28T11:56:17.726713shield sshd\[9934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.196.14.222
2019-10-28 20:17:04
136.228.161.66 attackbots
Oct 28 08:27:53 plusreed sshd[29158]: Invalid user cloud from 136.228.161.66
...
2019-10-28 20:28:30
31.163.164.115 attackbots
Telnetd brute force attack detected by fail2ban
2019-10-28 20:11:46

Recently Reported IPs

47.205.14.161 78.96.24.90 114.35.223.157 207.199.44.88
159.30.1.53 229.136.110.186 94.96.149.249 28.86.185.108
119.107.160.200 216.217.130.212 213.251.193.149 188.236.74.5
188.157.240.179 21.53.149.245 172.185.18.222 59.210.221.12
51.41.171.5 229.45.108.213 220.105.80.0 241.224.103.212