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

城市(city): unknown

省份(region): unknown

国家(country): None

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;104.16.103.80.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 11:41:37 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 80.103.16.104.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 80.103.16.104.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
139.59.190.69 attack
2020-05-03T18:00:01.286733abusebot-5.cloudsearch.cf sshd[29857]: Invalid user gwb from 139.59.190.69 port 32855
2020-05-03T18:00:01.294526abusebot-5.cloudsearch.cf sshd[29857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.190.69
2020-05-03T18:00:01.286733abusebot-5.cloudsearch.cf sshd[29857]: Invalid user gwb from 139.59.190.69 port 32855
2020-05-03T18:00:03.119892abusebot-5.cloudsearch.cf sshd[29857]: Failed password for invalid user gwb from 139.59.190.69 port 32855 ssh2
2020-05-03T18:06:38.030695abusebot-5.cloudsearch.cf sshd[30077]: Invalid user ec2-user from 139.59.190.69 port 56490
2020-05-03T18:06:38.047517abusebot-5.cloudsearch.cf sshd[30077]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.190.69
2020-05-03T18:06:38.030695abusebot-5.cloudsearch.cf sshd[30077]: Invalid user ec2-user from 139.59.190.69 port 56490
2020-05-03T18:06:39.709143abusebot-5.cloudsearch.cf sshd[30077]: Failed
...
2020-05-04 02:27:25
106.13.56.204 attack
May  2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782
May  2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.56.204
May  2 05:12:28 cumulus sshd[3894]: Failed password for invalid user zym from 106.13.56.204 port 39782 ssh2
May  2 05:12:28 cumulus sshd[3894]: Received disconnect from 106.13.56.204 port 39782:11: Bye Bye [preauth]
May  2 05:12:28 cumulus sshd[3894]: Disconnected from 106.13.56.204 port 39782 [preauth]
May  2 05:30:17 cumulus sshd[5008]: Invalid user bcs from 106.13.56.204 port 50808
May  2 05:30:17 cumulus sshd[5008]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.56.204
May  2 05:30:18 cumulus sshd[5008]: Failed password for invalid user bcs from 106.13.56.204 port 50808 ssh2
May  2 05:30:18 cumulus sshd[5008]: Received disconnect from 106.13.56.204 port 50808:11: Bye Bye [preauth]
May  2 05:30:18 cumul........
-------------------------------
2020-05-04 02:46:23
113.87.128.190 attackspambots
2020-05-02 15:41:40 server sshd[62131]: Failed password for invalid user zy from 113.87.128.190 port 13692 ssh2
2020-05-04 02:33:03
64.94.210.138 attackspambots
(From eric@talkwithwebvisitor.com) Hello, my name’s Eric and I just ran across your website at mihlonchiropractic.com...

I found it after a quick search, so your SEO’s working out…

Content looks pretty good…

One thing’s missing though…

A QUICK, EASY way to connect with you NOW.

Because studies show that a web lead like me will only hang out a few seconds – 7 out of 10 disappear almost instantly, Surf Surf Surf… then gone forever.

I have the solution:

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.  You’ll know immediately they’re interested and you can call them directly to TALK with them - literally while they’re still on the web looking at your site.

CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works and even give it a try… it could be huge for your business.

Plus, now that you’ve got that phone number, with our new
2020-05-04 03:03:06
106.12.147.216 attackbotsspam
May  3 15:17:36 vps58358 sshd\[18378\]: Invalid user sx from 106.12.147.216May  3 15:17:38 vps58358 sshd\[18378\]: Failed password for invalid user sx from 106.12.147.216 port 58430 ssh2May  3 15:20:37 vps58358 sshd\[18391\]: Invalid user meneses from 106.12.147.216May  3 15:20:39 vps58358 sshd\[18391\]: Failed password for invalid user meneses from 106.12.147.216 port 33626 ssh2May  3 15:23:41 vps58358 sshd\[18409\]: Failed password for root from 106.12.147.216 port 37064 ssh2May  3 15:27:03 vps58358 sshd\[18431\]: Failed password for root from 106.12.147.216 port 40496 ssh2
...
2020-05-04 02:59:57
157.245.55.174 attack
May  3 14:42:32 mail sshd\[30116\]: Invalid user deploy from 157.245.55.174
May  3 14:42:32 mail sshd\[30116\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.55.174
...
2020-05-04 03:05:04
35.194.64.202 attack
May  3 22:07:08 web1 sshd[20162]: Invalid user mimi from 35.194.64.202 port 42320
May  3 22:07:08 web1 sshd[20162]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.194.64.202
May  3 22:07:08 web1 sshd[20162]: Invalid user mimi from 35.194.64.202 port 42320
May  3 22:07:10 web1 sshd[20162]: Failed password for invalid user mimi from 35.194.64.202 port 42320 ssh2
May  3 22:15:48 web1 sshd[23560]: Invalid user zhen from 35.194.64.202 port 37492
May  3 22:15:48 web1 sshd[23560]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.194.64.202
May  3 22:15:48 web1 sshd[23560]: Invalid user zhen from 35.194.64.202 port 37492
May  3 22:15:50 web1 sshd[23560]: Failed password for invalid user zhen from 35.194.64.202 port 37492 ssh2
May  3 22:19:25 web1 sshd[25276]: Invalid user chad from 35.194.64.202 port 49712
...
2020-05-04 03:01:36
125.99.159.87 attackspambots
2020-05-03 07:15:38 server sshd[96182]: Failed password for invalid user steven from 125.99.159.87 port 53950 ssh2
2020-05-04 02:42:05
50.62.208.191 attackbotsspam
Detected by ModSecurity. Request URI: /bg/xmlrpc.php
2020-05-04 02:31:14
46.38.144.32 attackbotsspam
May  3 20:24:37 ncomp postfix/smtpd[23559]: warning: unknown[46.38.144.32]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  3 20:26:02 ncomp postfix/smtpd[23559]: warning: unknown[46.38.144.32]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May  3 20:27:26 ncomp postfix/smtpd[23559]: warning: unknown[46.38.144.32]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-05-04 02:28:29
14.171.139.114 attack
Unauthorised access (May  3) SRC=14.171.139.114 LEN=52 TTL=109 ID=29811 DF TCP DPT=445 WINDOW=8192 SYN
2020-05-04 02:37:57
103.147.10.222 attackspam
Automatic report - Banned IP Access
2020-05-04 02:54:10
2.24.2.95 attack
Port scan on 1 port(s): 23
2020-05-04 02:36:05
190.85.171.126 attackspambots
2020-05-03T15:38:24.928956homeassistant sshd[4058]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.85.171.126  user=root
2020-05-03T15:38:26.266499homeassistant sshd[4058]: Failed password for root from 190.85.171.126 port 38216 ssh2
...
2020-05-04 02:34:51
188.166.9.162 attack
188.166.9.162
2020-05-04 02:52:43

最近上报的IP列表

1.20.193.174 1.20.193.151 1.20.193.195 1.20.193.141
1.20.193.112 1.20.193.190 1.20.193.160 1.20.193.12
1.20.193.159 1.20.193.218 1.20.193.188 104.16.104.27
1.20.193.215 1.20.193.201 1.20.193.223 1.20.193.220
1.20.193.224 1.20.193.250 1.20.193.247 1.20.193.53