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

;; QUESTION SECTION:
;112.80.137.71.			IN	A

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

;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 16:08:51 CST 2022
;; MSG SIZE  rcvd: 106
HOST信息:
Host 71.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 71.137.80.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
176.31.182.125 attackbotsspam
2020-07-26T14:02:47.079805shield sshd\[7881\]: Invalid user master from 176.31.182.125 port 49495
2020-07-26T14:02:47.091579shield sshd\[7881\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.182.125
2020-07-26T14:02:48.582907shield sshd\[7881\]: Failed password for invalid user master from 176.31.182.125 port 49495 ssh2
2020-07-26T14:05:52.098524shield sshd\[8498\]: Invalid user nobe from 176.31.182.125 port 36817
2020-07-26T14:05:52.111242shield sshd\[8498\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.182.125
2020-07-26 23:52:41
109.94.120.2 attack
Port probing on unauthorized port 8080
2020-07-26 23:47:16
112.85.42.238 attackbotsspam
Jul 26 16:11:34 jumpserver sshd[253187]: Failed password for root from 112.85.42.238 port 47904 ssh2
Jul 26 16:12:41 jumpserver sshd[253191]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.238  user=root
Jul 26 16:12:43 jumpserver sshd[253191]: Failed password for root from 112.85.42.238 port 18280 ssh2
...
2020-07-27 00:13:37
35.196.37.206 attackspambots
35.196.37.206 - - \[26/Jul/2020:17:50:06 +0200\] "POST /wp-login.php HTTP/1.0" 200 2797 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
35.196.37.206 - - \[26/Jul/2020:17:50:08 +0200\] "POST /wp-login.php HTTP/1.0" 200 2796 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
35.196.37.206 - - \[26/Jul/2020:17:50:10 +0200\] "POST /wp-login.php HTTP/1.0" 200 2770 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-07-27 00:04:29
118.24.99.161 attackspambots
SSH Brute-Forcing (server1)
2020-07-27 00:00:33
62.210.251.54 attack
[portscan] Port scan
2020-07-27 00:06:09
90.93.188.157 attack
Jul 26 13:05:30 jumpserver sshd[251075]: Invalid user tariq from 90.93.188.157 port 51063
Jul 26 13:05:32 jumpserver sshd[251075]: Failed password for invalid user tariq from 90.93.188.157 port 51063 ssh2
Jul 26 13:10:36 jumpserver sshd[251126]: Invalid user apptest from 90.93.188.157 port 39670
...
2020-07-27 00:17:29
182.254.163.137 attackbotsspam
2020-07-26T14:31:35.990935abusebot-8.cloudsearch.cf sshd[30451]: Invalid user testing from 182.254.163.137 port 43500
2020-07-26T14:31:36.000022abusebot-8.cloudsearch.cf sshd[30451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.163.137
2020-07-26T14:31:35.990935abusebot-8.cloudsearch.cf sshd[30451]: Invalid user testing from 182.254.163.137 port 43500
2020-07-26T14:31:37.380723abusebot-8.cloudsearch.cf sshd[30451]: Failed password for invalid user testing from 182.254.163.137 port 43500 ssh2
2020-07-26T14:36:59.358567abusebot-8.cloudsearch.cf sshd[30460]: Invalid user mc from 182.254.163.137 port 39318
2020-07-26T14:36:59.364504abusebot-8.cloudsearch.cf sshd[30460]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.163.137
2020-07-26T14:36:59.358567abusebot-8.cloudsearch.cf sshd[30460]: Invalid user mc from 182.254.163.137 port 39318
2020-07-26T14:37:01.226627abusebot-8.cloudsearch.cf sshd[
...
2020-07-27 00:13:23
27.72.105.41 attackbotsspam
Auto Fail2Ban report, multiple SSH login attempts.
2020-07-26 23:51:41
95.216.21.236 attackspambots
sae-12 : Block return, carriage return, ... characters=>/index.php?option=com_content'[0]&view=article&id=124&Itemid=481(')
2020-07-26 23:49:29
190.129.47.148 attackbotsspam
SSH BruteForce Attack
2020-07-27 00:13:02
85.92.108.246 attackbotsspam
Jul 26 18:09:01 ns382633 sshd\[11065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.92.108.246  user=root
Jul 26 18:09:02 ns382633 sshd\[11065\]: Failed password for root from 85.92.108.246 port 56528 ssh2
Jul 26 18:11:26 ns382633 sshd\[11800\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.92.108.246  user=root
Jul 26 18:11:28 ns382633 sshd\[11800\]: Failed password for root from 85.92.108.246 port 43339 ssh2
Jul 26 18:25:57 ns382633 sshd\[14512\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.92.108.246  user=root
2020-07-27 00:26:43
125.104.35.3 attackspam
Jul 26 07:04:34 mailman postfix/smtpd[6974]: NOQUEUE: reject: RCPT from unknown[125.104.35.3]: 554 5.7.1 Service unavailable; Client host [125.104.35.3] blocked using sbl-xbl.spamhaus.org; https://www.spamhaus.org/query/ip/125.104.35.3; from= to=<[munged][at][munged]> proto=ESMTP helo=
Jul 26 07:04:36 mailman postfix/smtpd[6974]: NOQUEUE: reject: RCPT from unknown[125.104.35.3]: 554 5.7.1 Service unavailable; Client host [125.104.35.3] blocked using sbl-xbl.spamhaus.org; https://www.spamhaus.org/query/ip/125.104.35.3; from= to=<[munged][at][munged]> proto=ESMTP helo=
2020-07-26 23:54:28
61.55.158.20 attack
"fail2ban match"
2020-07-27 00:01:24
222.186.175.202 attack
Unauthorised connection attempt detected at AUO FR1 NODE2. System is sshd. Protected by AUO Stack Web Application Firewall (WAF)
2020-07-27 00:12:02

最近上报的IP列表

112.80.137.37 112.80.137.64 112.80.137.230 112.80.137.8
112.80.137.90 112.80.138.114 112.80.138.136 112.80.138.145
112.80.138.149 112.80.138.160 112.80.138.201 112.80.138.186
112.80.138.205 112.80.138.207 112.80.138.215 112.80.138.241
112.80.138.229 112.80.138.31 112.80.138.44 112.80.138.45