必须是合法有效的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 类型 评论内容 时间
112.80.137.153 attackspambots
Web Server Scan. RayID: 590c5cc7ee296e42, UA: Mozilla/4.049897920 Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729), Country: CN
2020-05-21 04:11:37
112.80.137.72 attack
Unauthorized connection attempt detected from IP address 112.80.137.72 to port 22 [J]
2020-03-02 19:32:51
112.80.137.30 attackspam
Unauthorized connection attempt detected from IP address 112.80.137.30 to port 9991 [T]
2020-01-27 15:42:09
112.80.137.97 attackbotsspam
Unauthorized connection attempt detected from IP address 112.80.137.97 to port 8081 [T]
2020-01-10 08:56:25
112.80.137.144 attack
CN_APNIC-HM_<177>1578575004 [1:2013053:1] ET WEB_SERVER PyCurl Suspicious User Agent Inbound [Classification: Attempted Information Leak] [Priority: 2]:  {TCP} 112.80.137.144:59730
2020-01-10 03:04:32
112.80.137.119 attackspam
Unauthorized connection attempt detected from IP address 112.80.137.119 to port 3128
2019-12-31 08:08:24
112.80.137.14 attackbots
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 05:16:33
112.80.137.34 attackspam
The IP has triggered Cloudflare WAF. CF-Ray: 54101e30ae016e18 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: theme-suka.skk.moe | User-Agent: Mozilla/5.051975669 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 06:43:04
112.80.137.117 attack
The IP has triggered Cloudflare WAF. CF-Ray: 54147ae5dbc76bb4 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Mobile Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 06:04:43
112.80.137.189 attackspambots
The IP has triggered Cloudflare WAF. CF-Ray: 541570716d3c9641 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.062334851 Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 05:07:54
112.80.137.13 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 541062388e246c56 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.051975669 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 03:17:30
112.80.137.39 attackbotsspam
The IP has triggered Cloudflare WAF. CF-Ray: 54104ef0f857ed47 | WAF_Rule_ID: 1025440 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: blog.skk.moe | User-Agent: Mozilla/5.0 (iPad; CPU OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1 | CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-08 01:34:56
WHOIS信息:
b
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.80.137.243
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17004
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.80.137.243.			IN	A

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

;; Query time: 68 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 06:39:48 CST 2022
;; MSG SIZE  rcvd: 107
HOST信息:
Host 243.137.80.112.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 243.137.80.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
177.130.161.20 attackbotsspam
failed_logins
2019-06-29 11:52:54
85.214.46.142 attackspam
Banned for posting to wp-login.php without referer {"redirect_to":"","user_login":"traveltocity@zohomail.eu","wp-submit":"Get+New+Password"}
2019-06-29 12:12:53
168.194.213.164 attackbotsspam
SMTP-sasl brute force
...
2019-06-29 11:50:11
5.196.110.170 attackspambots
Reported by AbuseIPDB proxy server.
2019-06-29 11:40:07
81.15.218.220 attack
2019-06-29T06:15:18.562280enmeeting.mahidol.ac.th sshd\[15905\]: User root from sonet.tychy.pl not allowed because not listed in AllowUsers
2019-06-29T06:15:18.687873enmeeting.mahidol.ac.th sshd\[15905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=sonet.tychy.pl  user=root
2019-06-29T06:15:20.636156enmeeting.mahidol.ac.th sshd\[15905\]: Failed password for invalid user root from 81.15.218.220 port 46806 ssh2
...
2019-06-29 12:11:28
62.210.139.53 attackbotsspam
[portscan] Port scan
2019-06-29 11:31:46
179.126.140.92 attackbots
Jun 29 02:23:37 dev0-dcde-rnet sshd[27848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.126.140.92
Jun 29 02:23:39 dev0-dcde-rnet sshd[27848]: Failed password for invalid user user from 179.126.140.92 port 55760 ssh2
Jun 29 02:25:53 dev0-dcde-rnet sshd[27856]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.126.140.92
2019-06-29 11:38:22
113.172.115.90 attackspambots
SSH Brute Force
2019-06-29 11:57:56
99.37.246.236 attackbots
Jun 29 01:17:17 bouncer sshd\[339\]: Invalid user ts from 99.37.246.236 port 50732
Jun 29 01:17:17 bouncer sshd\[339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.37.246.236 
Jun 29 01:17:19 bouncer sshd\[339\]: Failed password for invalid user ts from 99.37.246.236 port 50732 ssh2
...
2019-06-29 11:29:33
210.211.117.57 attackbotsspam
proto=tcp  .  spt=51605  .  dpt=25  .     (listed on Blocklist de  Jun 28)     (28)
2019-06-29 12:09:22
91.185.189.220 attack
Jun 29 00:48:30 localhost sshd\[22360\]: Invalid user brady from 91.185.189.220 port 60617
Jun 29 00:48:30 localhost sshd\[22360\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.185.189.220
...
2019-06-29 12:14:11
46.101.27.6 attackspambots
Jun 29 05:40:36 62-210-73-4 sshd\[20708\]: Invalid user applmgr from 46.101.27.6 port 44472
Jun 29 05:40:36 62-210-73-4 sshd\[20708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.27.6
...
2019-06-29 11:42:10
162.243.141.204 attack
28.06.2019 23:16:34 Connection to port 111 blocked by firewall
2019-06-29 11:42:44
187.1.40.226 attackspam
failed_logins
2019-06-29 12:01:55
185.220.102.8 attack
Jun 29 01:16:51 vps sshd[28388]: Failed password for root from 185.220.102.8 port 34439 ssh2
Jun 29 01:16:55 vps sshd[28388]: Failed password for root from 185.220.102.8 port 34439 ssh2
Jun 29 01:16:58 vps sshd[28388]: Failed password for root from 185.220.102.8 port 34439 ssh2
Jun 29 01:17:02 vps sshd[28388]: Failed password for root from 185.220.102.8 port 34439 ssh2
...
2019-06-29 11:33:54

最近上报的IP列表

112.80.137.200 112.80.137.25 112.80.138.10 112.80.137.70
112.80.138.108 112.80.137.253 112.80.138.127 112.80.138.125
112.80.137.93 112.80.138.150 112.80.138.155 112.80.138.185
112.80.138.194 112.80.138.170 112.80.138.231 112.80.138.235
112.80.138.240 112.80.138.242 112.80.138.3 112.80.138.50