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

城市(city): unknown

省份(region): unknown

国家(country): Republic of China (ROC)

运营商(isp): unknown

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
IP 类型 评论内容 时间
118.99.213.33 attackbotsspam
Automatic report - Banned IP Access
2019-11-15 21:30:28
118.99.213.33 attackspam
Automatic report - Port Scan Attack
2019-09-03 12:49:12
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 118.99.213.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33147
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;118.99.213.105.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 06:53:29 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
105.213.99.118.in-addr.arpa domain name pointer 105-213-99-118.savecom.net.tw.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
105.213.99.118.in-addr.arpa	name = 105-213-99-118.savecom.net.tw.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
94.23.223.165 attackbots
Jun 29 21:00:43 smtp postfix/smtpd[11141]: NOQUEUE: reject: RCPT from unknown[94.23.223.165]: 554 5.7.1 Service unavailable; Client host [94.23.223.165] blocked using cbl.abuseat.org; Blocked - see http://www.abuseat.org/lookup.cgi?ip=94.23.223.165; from= to= proto=ESMTP helo=
...
2019-06-30 05:44:43
68.183.94.158 attack
68.183.94.158 - - [29/Jun/2019:20:58:37 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
68.183.94.158 - - [29/Jun/2019:20:58:39 +0200] "POST /wp-login.php HTTP/1.1" 200 1632 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
68.183.94.158 - - [29/Jun/2019:20:58:42 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
68.183.94.158 - - [29/Jun/2019:20:58:43 +0200] "POST /wp-login.php HTTP/1.1" 200 1607 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
68.183.94.158 - - [29/Jun/2019:20:58:46 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
68.183.94.158 - - [29/Jun/2019:20:58:48 +0200] "POST /wp-login.php HTTP/1.1" 200 1608 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-06-30 06:16:24
112.185.245.232 attack
112.185.245.232 - - [29/Jun/2019:20:54:59 +0200] "GET /mysql/admin/index.php?lang=en HTTP/1.1" 404 219 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.119 Safari/537.36"
2019-06-30 06:08:49
113.176.15.3 attackspambots
Unauthorized connection attempt from IP address 113.176.15.3 on Port 445(SMB)
2019-06-30 05:42:36
37.29.2.79 attackspam
[portscan] Port scan
2019-06-30 06:09:51
150.95.129.150 attackspam
2019-06-29T22:05:13.960572abusebot-5.cloudsearch.cf sshd\[18916\]: Invalid user oracle2 from 150.95.129.150 port 39192
2019-06-30 06:08:33
159.89.8.230 attackspambots
Jun 29 20:58:55 ns37 sshd[12410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.8.230
Jun 29 20:58:55 ns37 sshd[12410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.8.230
2019-06-30 06:14:26
162.255.116.224 attackspambots
162.255.116.224 - - [29/Jun/2019:20:59:24 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
162.255.116.224 - - [29/Jun/2019:20:59:25 +0200] "POST /wp-login.php HTTP/1.1" 200 1632 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
162.255.116.224 - - [29/Jun/2019:20:59:25 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
162.255.116.224 - - [29/Jun/2019:20:59:26 +0200] "POST /wp-login.php HTTP/1.1" 200 1607 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
162.255.116.224 - - [29/Jun/2019:20:59:26 +0200] "GET /wp-login.php HTTP/1.1" 200 1237 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
162.255.116.224 - - [29/Jun/2019:20:59:27 +0200] "POST /wp-login.php HTTP/1.1" 200 1608 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
.
2019-06-30 05:51:53
37.59.104.76 attack
Invalid user zimbra from 37.59.104.76 port 40542
2019-06-30 05:45:27
182.61.21.197 attack
Jun 29 20:57:06 tux-35-217 sshd\[18096\]: Invalid user guest from 182.61.21.197 port 51416
Jun 29 20:57:06 tux-35-217 sshd\[18096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.21.197
Jun 29 20:57:08 tux-35-217 sshd\[18096\]: Failed password for invalid user guest from 182.61.21.197 port 51416 ssh2
Jun 29 20:59:29 tux-35-217 sshd\[18098\]: Invalid user webadmin from 182.61.21.197 port 46054
Jun 29 20:59:29 tux-35-217 sshd\[18098\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.21.197
...
2019-06-30 05:50:10
222.239.78.88 attackbotsspam
2019-06-29T22:51:50.9192961240 sshd\[16026\]: Invalid user zimbra from 222.239.78.88 port 50710
2019-06-29T22:51:50.9257191240 sshd\[16026\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.239.78.88
2019-06-29T22:51:53.1683341240 sshd\[16026\]: Failed password for invalid user zimbra from 222.239.78.88 port 50710 ssh2
...
2019-06-30 05:39:01
39.134.26.20 attackbots
firewall-block, port(s): 80/tcp, 6379/tcp, 6380/tcp, 7001/tcp
2019-06-30 05:38:13
139.59.35.148 attackspambots
Invalid user fake from 139.59.35.148 port 35620
2019-06-30 05:53:23
106.12.35.126 attack
Invalid user image from 106.12.35.126 port 34012
2019-06-30 06:13:37
171.100.119.102 attackbots
[SatJun2920:59:48.0969992019][:error][pid5391:tid47523490191104][client171.100.119.102:26030][client171.100.119.102]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"/wp-config.php"atREQUEST_FILENAME.[file"/usr/local/apache.ea3/conf/modsec_rules/99_asl_jitp.conf"][line"3411"][id"381206"][rev"1"][msg"Atomicorp.comWAFRules-VirtualJustInTimePatch:AccesstoWordPressconfigurationfileblocked"][data"/wp-config.php"][severity"CRITICAL"][hostname"148.251.104.82"][uri"/wp-config.php"][unique_id"XRe1JFw1tYC4Eem9skTdIgAAARM"][SatJun2921:00:08.7992932019][:error][pid5391:tid47523500697344][client171.100.119.102:34395][client171.100.119.102]ModSecurity:Accessdeniedwithcode404\(phase2\).Patternmatch"\(\?:/images/stories/\|/components/com_smartformer/files/\|/uploaded_files/user/\|uploads/job-manager-uploads/\).\*\\\\\\\\.php"atREQUEST_URI.[file"/usr/local/apache.ea3/conf/modsec_rules/50_asl_rootkits.conf"][line"71"][id"318812"][rev"2"][msg"Atomicorp.comWAFRules:PossibleAttempttoAcces
2019-06-30 05:55:10

最近上报的IP列表

118.99.124.186 118.99.79.11 118.99.73.220 118.99.87.23
118.99.98.227 119.0.19.95 119.100.172.16 119.0.197.195
119.100.56.125 119.102.12.243 119.102.14.131 119.102.8.200
119.108.57.92 119.109.18.89 119.109.106.244 119.109.231.196
119.112.196.155 119.112.30.18 119.113.158.25 119.113.230.68