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

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

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

;; QUESTION SECTION:
;222.202.104.139.		IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 17:28:13 CST 2025
;; MSG SIZE  rcvd: 108
HOST信息:
Host 139.104.202.222.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 139.104.202.222.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
68.183.150.254 attackbots
Aug 25 08:49:29 hanapaa sshd\[2765\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.150.254  user=man
Aug 25 08:49:32 hanapaa sshd\[2765\]: Failed password for man from 68.183.150.254 port 57684 ssh2
Aug 25 08:53:28 hanapaa sshd\[3078\]: Invalid user orders from 68.183.150.254
Aug 25 08:53:28 hanapaa sshd\[3078\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.150.254
Aug 25 08:53:30 hanapaa sshd\[3078\]: Failed password for invalid user orders from 68.183.150.254 port 48456 ssh2
2019-08-26 03:07:27
213.47.38.104 attackspam
Aug 25 18:53:28 sshgateway sshd\[7246\]: Invalid user helpdesk from 213.47.38.104
Aug 25 18:53:28 sshgateway sshd\[7246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.47.38.104
Aug 25 18:53:31 sshgateway sshd\[7246\]: Failed password for invalid user helpdesk from 213.47.38.104 port 36078 ssh2
2019-08-26 03:08:15
210.56.28.219 attackbots
Automated report - ssh fail2ban:
Aug 25 13:09:55 authentication failure 
Aug 25 13:09:57 wrong password, user=buddy, port=33578, ssh2
Aug 25 13:15:05 authentication failure
2019-08-26 02:35:26
77.42.115.178 attackbotsspam
Automatic report - Port Scan Attack
2019-08-26 02:39:54
36.156.24.43 attack
Aug 25 13:58:14 aat-srv002 sshd[23880]: Failed password for root from 36.156.24.43 port 57412 ssh2
Aug 25 13:58:23 aat-srv002 sshd[23882]: Failed password for root from 36.156.24.43 port 58404 ssh2
Aug 25 13:58:32 aat-srv002 sshd[23884]: Failed password for root from 36.156.24.43 port 60040 ssh2
...
2019-08-26 03:02:32
96.57.28.210 attack
Automatic report - Banned IP Access
2019-08-26 02:29:47
185.176.27.6 attack
08/25/2019-12:03:06.243983 185.176.27.6 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-08-26 02:34:29
203.110.166.51 attackspambots
Aug 25 08:41:54 vtv3 sshd\[11270\]: Invalid user bret from 203.110.166.51 port 47720
Aug 25 08:41:54 vtv3 sshd\[11270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51
Aug 25 08:41:56 vtv3 sshd\[11270\]: Failed password for invalid user bret from 203.110.166.51 port 47720 ssh2
Aug 25 08:44:21 vtv3 sshd\[12262\]: Invalid user annie from 203.110.166.51 port 47721
Aug 25 08:44:21 vtv3 sshd\[12262\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51
Aug 25 08:56:35 vtv3 sshd\[18669\]: Invalid user shirley from 203.110.166.51 port 47726
Aug 25 08:56:35 vtv3 sshd\[18669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.110.166.51
Aug 25 08:56:37 vtv3 sshd\[18669\]: Failed password for invalid user shirley from 203.110.166.51 port 47726 ssh2
Aug 25 08:59:12 vtv3 sshd\[19721\]: Invalid user ee from 203.110.166.51 port 47727
Aug 25 08:59:12 vtv3 sshd\[19721\
2019-08-26 02:51:21
193.32.160.144 attackspam
Aug 25 20:53:24 relay postfix/smtpd\[17671\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.144\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 25 20:53:24 relay postfix/smtpd\[17671\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.144\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 25 20:53:24 relay postfix/smtpd\[17671\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.144\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.139\]\>
Aug 25 20:53:24 relay postfix/smtpd\[17671\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.144\]: 554 5.7.1 \: Relay access denied\; from=\ to=\
2019-08-26 03:12:44
118.126.96.40 attack
2019-08-25T09:28:58.033260abusebot-8.cloudsearch.cf sshd\[19190\]: Invalid user flame from 118.126.96.40 port 50490
2019-08-26 02:43:22
209.97.154.151 attackspam
Aug 25 19:43:49 srv206 sshd[14891]: Invalid user ts3 from 209.97.154.151
...
2019-08-26 02:49:10
59.120.240.217 attackspam
TW Taiwan 59-120-240-217.HINET-IP.hinet.net Hits: 11
2019-08-26 03:17:20
184.168.193.128 attackspambots
invalid username 'tectus.net'
2019-08-26 03:15:18
159.89.162.118 attackbotsspam
Aug 25 08:49:04 php1 sshd\[16444\]: Invalid user sandeep from 159.89.162.118
Aug 25 08:49:04 php1 sshd\[16444\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118
Aug 25 08:49:06 php1 sshd\[16444\]: Failed password for invalid user sandeep from 159.89.162.118 port 47784 ssh2
Aug 25 08:53:33 php1 sshd\[16818\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118  user=sync
Aug 25 08:53:35 php1 sshd\[16818\]: Failed password for sync from 159.89.162.118 port 36044 ssh2
2019-08-26 03:04:54
212.64.74.136 attack
[SunAug2509:54:16.5316942019][:error][pid13140:tid46947727656704][client212.64.74.136:23899][client212.64.74.136]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"/wp-config.php"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/99_asl_jitp.conf"][line"3498"][id"381206"][rev"1"][msg"Atomicorp.comWAFRules-VirtualJustInTimePatch:AccesstoWordPressconfigurationfileblocked"][data"/wp-config.php"][severity"CRITICAL"][hostname"136.243.224.50"][uri"/wp-config.php"][unique_id"XWI@qDXYB@7mck7e5Vt4mgAAANY"][SunAug2509:55:27.2810682019][:error][pid13139:tid46947694036736][client212.64.74.136:36072][client212.64.74.136]ModSecurity:Accessdeniedwithcode404\(phase2\).Patternmatch"\(\?:/images/stories/\|/components/com_smartformer/files/\|/uploaded_files/user/\|uploads/job-manager-uploads/\).\*\\\\\\\\.php"atREQUEST_URI.[file"/etc/apache2/conf.d/modsec_rules/50_asl_rootkits.conf"][line"71"][id"318812"][rev"2"][msg"Atomicorp.comWAFRules:PossibleAttempttoAccessunauthorizedshellor
2019-08-26 02:38:46

最近上报的IP列表

136.82.2.244 126.192.233.45 90.190.177.31 64.99.41.182
232.203.16.70 228.253.181.133 126.206.187.113 116.112.72.202
199.94.25.155 107.78.207.151 27.39.163.150 13.48.30.32
86.159.110.75 103.156.93.196 171.207.27.156 155.133.113.66
147.122.58.81 182.141.239.208 24.37.57.226 236.164.131.45