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

城市(city): unknown

省份(region): unknown

国家(country): United States

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;104.21.91.196.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:14:50 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 196.91.21.104.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 196.91.21.104.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
185.39.10.31 attack
SSH Scan
2020-06-07 15:35:40
107.175.92.118 attack
(From eric@talkwithwebvisitor.com) Good day, 

My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

What for?  

Part of my job is to check out websites and the work you’ve done with svchiropractic.com definitely stands out. 

It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

There is, however, a catch… more accurately, a question…

So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? 

More importantly, how do you make a connection with that person?

Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

Here’s a way to create INSTANT engagement that you may not have known about… 

Talk With Web Visitor is a software widget that’s works on your site, ready to capture any
2020-06-07 15:41:12
122.51.114.51 attackbots
Jun  7 07:59:10 vps687878 sshd\[3419\]: Failed password for root from 122.51.114.51 port 44046 ssh2
Jun  7 08:00:58 vps687878 sshd\[3748\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.114.51  user=root
Jun  7 08:00:59 vps687878 sshd\[3748\]: Failed password for root from 122.51.114.51 port 35288 ssh2
Jun  7 08:02:47 vps687878 sshd\[3973\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.114.51  user=root
Jun  7 08:02:49 vps687878 sshd\[3973\]: Failed password for root from 122.51.114.51 port 54766 ssh2
...
2020-06-07 15:25:04
121.7.127.92 attack
Jun  7 07:54:22 MainVPS sshd[27866]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.7.127.92  user=root
Jun  7 07:54:24 MainVPS sshd[27866]: Failed password for root from 121.7.127.92 port 54909 ssh2
Jun  7 07:57:36 MainVPS sshd[30810]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.7.127.92  user=root
Jun  7 07:57:39 MainVPS sshd[30810]: Failed password for root from 121.7.127.92 port 46293 ssh2
Jun  7 08:00:39 MainVPS sshd[894]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.7.127.92  user=root
Jun  7 08:00:41 MainVPS sshd[894]: Failed password for root from 121.7.127.92 port 37686 ssh2
...
2020-06-07 15:22:37
139.162.39.204 attackspambots
RDP Brute-Force (honeypot 5)
2020-06-07 15:18:37
139.59.169.37 attackspambots
Jun  7 07:56:41 lukav-desktop sshd\[17836\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.169.37  user=root
Jun  7 07:56:43 lukav-desktop sshd\[17836\]: Failed password for root from 139.59.169.37 port 39278 ssh2
Jun  7 08:00:23 lukav-desktop sshd\[17895\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.169.37  user=root
Jun  7 08:00:26 lukav-desktop sshd\[17895\]: Failed password for root from 139.59.169.37 port 41832 ssh2
Jun  7 08:04:03 lukav-desktop sshd\[17934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.169.37  user=root
2020-06-07 15:16:03
183.224.38.56 attack
SSH login attempts.
2020-06-07 15:59:32
195.54.166.138 attackbots
Jun  7 10:08:00 debian kernel: [416239.620616] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=195.54.166.138 DST=89.252.131.35 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=42190 PROTO=TCP SPT=59541 DPT=6710 WINDOW=1024 RES=0x00 SYN URGP=0
2020-06-07 15:19:35
167.114.113.141 attackbots
$f2bV_matches
2020-06-07 15:58:25
161.35.11.165 attackbotsspam
$f2bV_matches
2020-06-07 15:30:11
116.255.196.135 attackbotsspam
Jun  7 07:28:10 mail sshd[29474]: Failed password for root from 116.255.196.135 port 50872 ssh2
Jun  7 07:45:57 mail sshd[31630]: Failed password for root from 116.255.196.135 port 35832 ssh2
Jun  7 07:49:08 mail sshd[32001]: Failed password for root from 116.255.196.135 port 44864 ssh2
...
2020-06-07 15:47:55
167.250.216.53 attackbots
2020-06-07 15:45:03
106.13.233.4 attackbots
2020-06-07T09:08:10.642571+02:00  sshd[27080]: Failed password for root from 106.13.233.4 port 57056 ssh2
2020-06-07 15:25:55
176.193.253.56 attackbots
Automatic report - Port Scan Attack
2020-06-07 15:47:25
112.85.42.89 attackspambots
Jun  7 09:11:20 ns381471 sshd[14102]: Failed password for root from 112.85.42.89 port 43478 ssh2
2020-06-07 15:27:52

最近上报的IP列表

104.21.91.200 104.21.91.203 104.21.91.204 104.21.91.206
104.21.91.205 104.21.91.207 104.21.91.208 104.21.91.21
104.21.91.217 104.21.91.212 104.21.91.210 104.21.91.216
104.21.91.215 104.21.91.219 104.21.91.218 104.21.91.220
104.21.91.222 104.21.91.223 104.21.91.230 104.21.91.228