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

;; QUESTION SECTION:
;112.80.137.0.			IN	A

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

;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 13:33:15 CST 2022
;; MSG SIZE  rcvd: 105
HOST信息:
Host 0.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 0.137.80.112.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
222.186.30.167 attackbotsspam
Jul 10 09:06:34 santamaria sshd\[1574\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.167  user=root
Jul 10 09:06:36 santamaria sshd\[1574\]: Failed password for root from 222.186.30.167 port 42488 ssh2
Jul 10 09:06:38 santamaria sshd\[1574\]: Failed password for root from 222.186.30.167 port 42488 ssh2
...
2020-07-10 15:09:38
192.99.5.94 attack
192.99.5.94 - - [10/Jul/2020:08:14:50 +0100] "POST /wp-login.php HTTP/1.1" 200 5881 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
192.99.5.94 - - [10/Jul/2020:08:17:24 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
192.99.5.94 - - [10/Jul/2020:08:19:32 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36"
...
2020-07-10 15:21:34
35.185.133.141 attackbotsspam
$f2bV_matches
2020-07-10 15:22:43
54.37.21.211 attackbotsspam
Automatic report - XMLRPC Attack
2020-07-10 15:01:53
112.85.42.104 attackbots
Jul 10 09:22:46 minden010 sshd[25610]: Failed password for root from 112.85.42.104 port 54594 ssh2
Jul 10 09:22:48 minden010 sshd[25610]: Failed password for root from 112.85.42.104 port 54594 ssh2
Jul 10 09:22:50 minden010 sshd[25610]: Failed password for root from 112.85.42.104 port 54594 ssh2
...
2020-07-10 15:24:19
157.230.184.120 attackspambots
Jul 10 08:58:09 debian-2gb-nbg1-2 kernel: \[16622879.998207\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=157.230.184.120 DST=195.201.40.59 LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=34684 PROTO=TCP SPT=1784 DPT=4722 WINDOW=65535 RES=0x00 SYN URGP=0
2020-07-10 15:34:43
103.48.190.32 attackspam
Jul 10 04:17:42 bchgang sshd[28126]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.48.190.32
Jul 10 04:17:44 bchgang sshd[28126]: Failed password for invalid user root-admin from 103.48.190.32 port 36162 ssh2
Jul 10 04:21:18 bchgang sshd[28192]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.48.190.32
...
2020-07-10 15:24:48
2.226.157.66 attackspam
Jul 10 07:07:47 *** sshd[24670]: Invalid user pi from 2.226.157.66
2020-07-10 15:14:26
31.36.181.181 attackspambots
Jul 10 06:49:31 journals sshd\[7943\]: Invalid user longhui from 31.36.181.181
Jul 10 06:49:31 journals sshd\[7943\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.36.181.181
Jul 10 06:49:32 journals sshd\[7943\]: Failed password for invalid user longhui from 31.36.181.181 port 50152 ssh2
Jul 10 06:53:55 journals sshd\[8455\]: Invalid user wilson from 31.36.181.181
Jul 10 06:53:55 journals sshd\[8455\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.36.181.181
...
2020-07-10 15:19:59
61.107.72.165 attack
Jul 10 12:00:52 ns1 postfix/smtpd\[17899\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:00:55 ns1 postfix/smtpd\[17899\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:27:32 ns1 postfix/smtpd\[18330\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:27:35 ns1 postfix/smtpd\[18330\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
Jul 10 12:54:02 ns1 postfix/smtpd\[18675\]: warning: unknown\[61.107.72.165\]: SASL LOGIN authentication failed: authentication failure
...
2020-07-10 15:12:27
178.128.88.244 attackbots
Jul 10 06:49:40 srv sshd[6252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.88.244
2020-07-10 15:35:41
218.92.0.249 attackbotsspam
Jul  9 21:04:48 web9 sshd\[5040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.249  user=root
Jul  9 21:04:51 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:04:54 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:04:57 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
Jul  9 21:05:00 web9 sshd\[5040\]: Failed password for root from 218.92.0.249 port 20428 ssh2
2020-07-10 15:09:59
176.31.250.160 attack
Jul 10 13:53:36 localhost sshd[3949552]: Invalid user wldai from 176.31.250.160 port 34418
...
2020-07-10 15:34:29
35.234.28.121 attack
WordPress wp-login brute force :: 35.234.28.121 0.096 BYPASS [10/Jul/2020:04:08:37  0000] [censored_2] "POST /wp-login.php HTTP/1.1" 200 2003 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-07-10 15:03:21
51.254.37.156 attackbots
Jul 10 06:12:05 vm1 sshd[23764]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.37.156
Jul 10 06:12:07 vm1 sshd[23764]: Failed password for invalid user oracle from 51.254.37.156 port 58214 ssh2
...
2020-07-10 15:00:24

最近上报的IP列表

112.80.137.107 112.80.137.192 112.80.137.179 112.80.137.209
112.80.137.199 112.80.137.245 112.80.137.225 112.80.137.24
112.80.137.35 112.80.137.247 112.80.137.182 112.80.137.246
112.80.137.41 112.80.137.171 112.80.137.190 112.80.137.45
112.80.137.51 112.80.137.60 112.80.137.48 112.80.137.54