必须是合法有效的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.40.64
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24231
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.16.40.64.			IN	A

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

;; Query time: 31 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 01:37:16 CST 2022
;; MSG SIZE  rcvd: 105
HOST信息:
Host 64.40.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 64.40.16.104.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
170.0.128.10 attackspam
Oct  4 06:50:16 lcl-usvr-01 sshd[877]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.0.128.10  user=root
Oct  4 06:55:01 lcl-usvr-01 sshd[2159]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.0.128.10  user=root
Oct  4 06:59:53 lcl-usvr-01 sshd[3585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.0.128.10  user=root
2019-10-04 08:58:25
103.89.253.249 attackspam
Unauthorized access detected from banned ip
2019-10-04 08:49:03
51.255.95.119 attackspam
fail2ban honeypot
2019-10-04 09:02:50
54.37.129.235 attackspambots
Oct  4 02:27:24 nextcloud sshd\[30212\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.129.235  user=root
Oct  4 02:27:26 nextcloud sshd\[30212\]: Failed password for root from 54.37.129.235 port 50278 ssh2
Oct  4 02:31:00 nextcloud sshd\[3248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.129.235  user=root
...
2019-10-04 08:38:54
209.97.155.122 attack
Wordpress Admin Login attack
2019-10-04 09:03:41
109.236.91.85 attackbots
Oct  3 22:48:07 herz-der-gamer sshd[8933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.236.91.85  user=ts3
Oct  3 22:48:09 herz-der-gamer sshd[8933]: Failed password for ts3 from 109.236.91.85 port 36055 ssh2
...
2019-10-04 09:04:30
51.77.230.125 attack
Oct  4 02:25:06 mail sshd\[10365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.230.125  user=root
Oct  4 02:25:08 mail sshd\[10365\]: Failed password for root from 51.77.230.125 port 32858 ssh2
Oct  4 02:28:56 mail sshd\[10715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.230.125  user=root
Oct  4 02:28:58 mail sshd\[10715\]: Failed password for root from 51.77.230.125 port 45186 ssh2
Oct  4 02:32:43 mail sshd\[11094\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.230.125  user=root
2019-10-04 08:54:15
114.67.74.139 attackbotsspam
Oct  3 18:29:47 TORMINT sshd\[6121\]: Invalid user applmgr from 114.67.74.139
Oct  3 18:29:47 TORMINT sshd\[6121\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.74.139
Oct  3 18:29:49 TORMINT sshd\[6121\]: Failed password for invalid user applmgr from 114.67.74.139 port 33848 ssh2
...
2019-10-04 08:42:22
181.174.164.66 attackspam
Oct  3 16:12:55 localhost kernel: [3871394.718849] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=181.174.164.66 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=66 ID=28091 DF PROTO=TCP SPT=62797 DPT=22 SEQ=3294969235 ACK=0 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  3 16:48:49 localhost kernel: [3873548.633136] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=181.174.164.66 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=78 ID=55412 DF PROTO=TCP SPT=55773 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  3 16:48:49 localhost kernel: [3873548.633171] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:aa:c1:08:00 SRC=181.174.164.66 DST=[mungedIP2] LEN=40 TOS=0x08 PREC=0x20 TTL=78 ID=55412 DF PROTO=TCP SPT=55773 DPT=22 SEQ=669450212 ACK=0 WINDOW=29200 RES=0x00 SYN URGP=0
2019-10-04 08:37:21
139.59.35.214 attack
firewall-block, port(s): 10000/tcp
2019-10-04 09:05:14
91.207.40.44 attackspam
2019-10-04T00:46:53.377914shield sshd\[12657\]: Invalid user Aa\#321 from 91.207.40.44 port 54592
2019-10-04T00:46:53.386359shield sshd\[12657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.207.40.44
2019-10-04T00:46:55.052112shield sshd\[12657\]: Failed password for invalid user Aa\#321 from 91.207.40.44 port 54592 ssh2
2019-10-04T00:51:21.238394shield sshd\[13075\]: Invalid user Veronique1@3 from 91.207.40.44 port 39522
2019-10-04T00:51:21.243944shield sshd\[13075\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.207.40.44
2019-10-04 08:53:17
35.233.174.178 attack
WordPress login Brute force / Web App Attack on client site.
2019-10-04 08:47:16
46.37.24.226 attackbotsspam
Oct  3 22:48:59 mail sshd\[23720\]: Invalid user ftpuser from 46.37.24.226
Oct  3 22:48:59 mail sshd\[23720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.37.24.226
Oct  3 22:49:01 mail sshd\[23720\]: Failed password for invalid user ftpuser from 46.37.24.226 port 56643 ssh2
...
2019-10-04 08:29:18
165.22.182.168 attack
$f2bV_matches
2019-10-04 08:42:52
138.197.213.233 attackspambots
Oct  4 03:47:42 tuotantolaitos sshd[19393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.213.233
Oct  4 03:47:43 tuotantolaitos sshd[19393]: Failed password for invalid user sidney from 138.197.213.233 port 40792 ssh2
...
2019-10-04 08:50:18

最近上报的IP列表

104.21.63.61 104.16.40.12 104.16.41.196 104.16.41.12
104.16.42.102 104.16.42.19 104.16.43.102 104.16.42.72
104.16.43.19 104.16.42.196 104.16.42.92 104.16.43.62
104.16.40.56 104.16.43.196 104.16.43.92 104.16.43.42
104.21.63.62 104.16.43.72 104.16.44.196 104.16.44.42