城市(city): unknown
省份(region): unknown
国家(country): IANA Special-Purpose Address
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 172.16.0.0 - 172.31.255.255
CIDR: 172.16.0.0/12
NetName: PRIVATE-ADDRESS-BBLK-RFC1918-IANA-RESERVED
NetHandle: NET-172-16-0-0-1
Parent: NET172 (NET-172-0-0-0-0)
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1994-03-15
Updated: 2024-05-24
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
Comment:
Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment: http://datatracker.ietf.org/doc/rfc1918
Ref: https://rdap.arin.net/registry/ip/172.16.0.0
OrgName: Internet Assigned Numbers Authority
OrgId: IANA
Address: 12025 Waterfront Drive
Address: Suite 300
City: Los Angeles
StateProv: CA
PostalCode: 90292
Country: US
RegDate:
Updated: 2024-05-24
Ref: https://rdap.arin.net/registry/entity/IANA
OrgTechHandle: IANA-IP-ARIN
OrgTechName: ICANN
OrgTechPhone: +1-310-301-5820
OrgTechEmail: abuse@iana.org
OrgTechRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: ICANN
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: abuse@iana.org
OrgAbuseRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.21.135.90
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16649
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;172.21.135.90. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026032302 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 24 10:33:12 CST 2026
;; MSG SIZE rcvd: 106Host 90.135.21.172.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 90.135.21.172.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 134.19.218.134 | attack | Lines containing failures of 134.19.218.134 (max 1000) Jul 30 18:24:52 mm sshd[15781]: Invalid user holy from 134.19.218.134 p= ort 55090 Jul 30 18:24:52 mm sshd[15781]: pam_unix(sshd:auth): authentication fai= lure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D134.19.218= .134 Jul 30 18:24:54 mm sshd[15781]: Failed password for invalid user holy f= rom 134.19.218.134 port 55090 ssh2 Jul 30 18:24:56 mm sshd[15781]: Received disconnect from 134.19.218.134= port 55090:11: Bye Bye [preauth] Jul 30 18:24:56 mm sshd[15781]: Disconnected from invalid user holy 134= .19.218.134 port 55090 [preauth] Jul 30 18:51:00 mm sshd[15997]: Invalid user adine from 134.19.218.134 = port 38136 Jul 30 18:51:00 mm sshd[15997]: pam_unix(sshd:auth): authentication fai= lure; logname=3D uid=3D0 euid=3D0 tty=3Dssh ruser=3D rhost=3D134.19.218= .134 Jul 30 18:51:02 mm sshd[15997]: Failed password for invalid user adine = from 134.19.218.134 port 38136 ssh2 Jul 30 18:51:02 mm sshd[15997]:........ ------------------------------ |
2019-07-31 11:47:56 |
| 118.163.67.139 | attack | Honeypot attack, port: 445, PTR: 118-163-67-139.HINET-IP.hinet.net. |
2019-07-31 12:39:01 |
| 185.175.93.27 | attackbotsspam | firewall-block, port(s): 3637/tcp, 33991/tcp |
2019-07-31 12:26:30 |
| 170.83.161.202 | attackspambots | Unauthorized connection attempt from IP address 170.83.161.202 on Port 445(SMB) |
2019-07-31 12:27:31 |
| 122.121.26.92 | attackspambots | port 23 attempt blocked |
2019-07-31 11:51:42 |
| 89.133.126.22 | attackspambots | 31.07.2019 00:33:32 - Login Fail on hMailserver Detected by ELinOX-hMail-A2F |
2019-07-31 12:48:28 |
| 164.52.12.210 | attackspam | Jul 31 02:47:56 mail sshd\[6953\]: Invalid user chuan from 164.52.12.210 port 56036 Jul 31 02:47:56 mail sshd\[6953\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.52.12.210 ... |
2019-07-31 11:44:49 |
| 94.182.189.212 | attackbotsspam | Jul 31 01:09:57 vtv3 sshd\[18476\]: Invalid user beginner from 94.182.189.212 port 49168 Jul 31 01:09:57 vtv3 sshd\[18476\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.182.189.212 Jul 31 01:09:59 vtv3 sshd\[18476\]: Failed password for invalid user beginner from 94.182.189.212 port 49168 ssh2 Jul 31 01:14:57 vtv3 sshd\[20892\]: Invalid user hz from 94.182.189.212 port 43508 Jul 31 01:14:57 vtv3 sshd\[20892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.182.189.212 Jul 31 01:29:32 vtv3 sshd\[28171\]: Invalid user lijia from 94.182.189.212 port 54758 Jul 31 01:29:32 vtv3 sshd\[28171\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.182.189.212 Jul 31 01:29:34 vtv3 sshd\[28171\]: Failed password for invalid user lijia from 94.182.189.212 port 54758 ssh2 Jul 31 01:34:30 vtv3 sshd\[30558\]: Invalid user igor from 94.182.189.212 port 49094 Jul 31 01:34:30 vtv3 sshd\[305 |
2019-07-31 11:38:01 |
| 186.213.145.64 | attackbotsspam | Lines containing failures of 186.213.145.64 (max 1000) Jul 30 21:28:06 localhost sshd[30188]: Invalid user asterisk from 186.213.145.64 port 56774 Jul 30 21:28:06 localhost sshd[30188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.213.145.64 Jul 30 21:28:08 localhost sshd[30188]: Failed password for invalid user asterisk from 186.213.145.64 port 56774 ssh2 Jul 30 21:28:10 localhost sshd[30188]: Received disconnect from 186.213.145.64 port 56774:11: Bye Bye [preauth] Jul 30 21:28:10 localhost sshd[30188]: Disconnected from invalid user asterisk 186.213.145.64 port 56774 [preauth] Jul 30 21:39:00 localhost sshd[31579]: User postgres from 186.213.145.64 not allowed because none of user's groups are listed in AllowGroups Jul 30 21:39:00 localhost sshd[31579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.213.145.64 user=postgres Jul 30 21:39:03 localhost sshd[31579]: Failed passwor........ ------------------------------ |
2019-07-31 12:25:21 |
| 178.176.174.131 | attack | Brute force attempt |
2019-07-31 11:54:10 |
| 185.86.164.100 | attack | B: Abusive content scan (301) |
2019-07-31 11:48:52 |
| 185.33.203.190 | attackbotsspam | Unauthorized connection attempt from IP address 185.33.203.190 on Port 445(SMB) |
2019-07-31 12:35:38 |
| 163.172.58.50 | attack | 163.172.58.50 - - [31/Jul/2019:04:31:43 +0200] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 163.172.58.50 - - [31/Jul/2019:04:31:43 +0200] "POST /wp-login.php HTTP/1.1" 200 1503 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 163.172.58.50 - - [31/Jul/2019:04:31:43 +0200] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 163.172.58.50 - - [31/Jul/2019:04:31:44 +0200] "POST /wp-login.php HTTP/1.1" 200 1486 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 163.172.58.50 - - [31/Jul/2019:04:31:44 +0200] "GET /wp-login.php HTTP/1.1" 200 1122 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 163.172.58.50 - - [31/Jul/2019:04:31:45 +0200] "POST /wp-login.php HTTP/1.1" 200 1486 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2019-07-31 12:31:01 |
| 113.176.70.172 | attackbotsspam | Unauthorized connection attempt from IP address 113.176.70.172 on Port 445(SMB) |
2019-07-31 11:57:16 |
| 187.248.23.157 | attackspambots | Unauthorized connection attempt from IP address 187.248.23.157 on Port 445(SMB) |
2019-07-31 11:53:24 |