必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): unknown

省份(region): unknown

国家(country): United States of America (the)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.104.160.0
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7102
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.104.160.0.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 19 22:05:04 CST 2025
;; MSG SIZE  rcvd: 106
HOST信息:
Host 0.160.104.139.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 0.160.104.139.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
111.72.197.24 attack
Aug 15 06:20:44 srv01 postfix/smtpd\[31636\]: warning: unknown\[111.72.197.24\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 06:20:56 srv01 postfix/smtpd\[31636\]: warning: unknown\[111.72.197.24\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 06:21:13 srv01 postfix/smtpd\[31636\]: warning: unknown\[111.72.197.24\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 06:21:31 srv01 postfix/smtpd\[31636\]: warning: unknown\[111.72.197.24\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Aug 15 06:21:43 srv01 postfix/smtpd\[31636\]: warning: unknown\[111.72.197.24\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-08-15 18:23:00
222.186.180.147 attackspambots
Aug 15 05:42:05 plusreed sshd[13573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.147  user=root
Aug 15 05:42:07 plusreed sshd[13573]: Failed password for root from 222.186.180.147 port 15088 ssh2
...
2020-08-15 17:49:27
221.144.178.231 attack
Aug 15 05:45:01 serwer sshd\[13617\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.144.178.231  user=root
Aug 15 05:45:03 serwer sshd\[13617\]: Failed password for root from 221.144.178.231 port 34286 ssh2
Aug 15 05:47:00 serwer sshd\[15171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.144.178.231  user=root
...
2020-08-15 18:00:49
128.199.92.187 attack
TCP port : 13478
2020-08-15 18:26:26
23.82.28.25 attackbotsspam
(From eric@talkwithwebvisitor.com) Cool website!

My name’s Eric, and I just found your site - spineworksdecompression.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool.
 
But if you don’t mind me asking – after someone like me stumbles across spineworksdecompression.com, what usually happens?

Is your site generating leads for your business? 
 
I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace.

Not good.

Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.”

You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literall
2020-08-15 17:48:15
192.241.239.189 attack
[Thu Aug 06 03:49:30 2020] - DDoS Attack From IP: 192.241.239.189 Port: 54114
2020-08-15 17:59:33
106.12.34.97 attackspam
frenzy
2020-08-15 18:26:41
23.245.154.104 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found decubellisfamilychiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new
2020-08-15 17:54:17
222.186.61.191 attackbotsspam
Aug 15 10:30:43 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
Aug 15 10:30:45 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
Aug 15 10:30:46 inter-technics postfix/smtpd[22491]: warning: unknown[222.186.61.191]: SASL LOGIN authentication failed: authentication failure
...
2020-08-15 18:21:42
62.112.11.8 attackbotsspam
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-08-15T08:06:14Z and 2020-08-15T09:37:13Z
2020-08-15 17:48:42
46.52.130.82 attackspam
Aug 15 11:18:00 mout sshd[15295]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.52.130.82  user=pi
Aug 15 11:18:02 mout sshd[15295]: Failed password for pi from 46.52.130.82 port 48426 ssh2
Aug 15 11:18:03 mout sshd[15295]: Connection closed by authenticating user pi 46.52.130.82 port 48426 [preauth]
2020-08-15 18:23:26
5.188.84.228 attackspambots
2,50-01/03 [bc01/m10] PostRequest-Spammer scoring: rome
2020-08-15 18:16:35
180.126.185.94 attack
Lines containing failures of 180.126.185.94
Aug 15 11:52:31 shared03 sshd[9035]: Bad protocol version identification '' from 180.126.185.94 port 59119
Aug 15 11:52:33 shared03 sshd[9037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.126.185.94  user=r.r
Aug 15 11:52:35 shared03 sshd[9037]: Failed password for r.r from 180.126.185.94 port 59758 ssh2
Aug 15 11:52:37 shared03 sshd[9037]: Connection closed by authenticating user r.r 180.126.185.94 port 59758 [preauth]
Aug 15 11:52:43 shared03 sshd[9052]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.126.185.94  user=r.r
Aug 15 11:52:45 shared03 sshd[9052]: Failed password for r.r from 180.126.185.94 port 33427 ssh2
Aug 15 11:52:46 shared03 sshd[9052]: Connection closed by authenticating user r.r 180.126.185.94 port 33427 [preauth]
Aug 15 11:52:50 shared03 sshd[9074]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 ........
------------------------------
2020-08-15 18:28:27
109.87.143.67 attackspambots
Dovecot Invalid User Login Attempt.
2020-08-15 18:18:59
175.24.81.207 attackspambots
Aug 15 04:19:37 serwer sshd\[19362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.81.207  user=root
Aug 15 04:19:38 serwer sshd\[19362\]: Failed password for root from 175.24.81.207 port 40370 ssh2
Aug 15 04:23:07 serwer sshd\[21403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.24.81.207  user=root
...
2020-08-15 17:59:52

最近上报的IP列表

6.174.68.54 33.83.250.63 175.198.154.231 92.89.144.18
42.255.99.137 185.54.229.189 137.181.234.3 200.226.160.19
238.22.75.26 143.157.201.163 95.39.86.114 211.240.234.255
12.139.231.85 14.107.176.100 252.30.151.28 223.61.187.32
208.177.152.4 180.213.64.12 31.230.241.93 206.17.40.142