城市(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-2025, American Registry for Internet Numbers, Ltd.
#
NetRange: 10.0.0.0 - 10.255.255.255
CIDR: 10.0.0.0/8
NetName: PRIVATE-ADDRESS-ABLK-RFC1918-IANA-RESERVED
NetHandle: NET-10-0-0-0-1
Parent: ()
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate:
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/10.0.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
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
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
#
# 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-2025, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.20.74.26
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29160
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;10.20.74.26. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025100901 1800 900 604800 86400
;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 10 09:30:07 CST 2025
;; MSG SIZE rcvd: 104Host 26.74.20.10.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 26.74.20.10.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 192.241.185.120 | attack | Oct 3 00:24:01 server sshd\[25884\]: Invalid user pruebas from 192.241.185.120 port 46923 Oct 3 00:24:01 server sshd\[25884\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.185.120 Oct 3 00:24:03 server sshd\[25884\]: Failed password for invalid user pruebas from 192.241.185.120 port 46923 ssh2 Oct 3 00:29:39 server sshd\[26812\]: Invalid user user from 192.241.185.120 port 39039 Oct 3 00:29:39 server sshd\[26812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.185.120 |
2019-10-03 05:49:04 |
| 110.80.17.26 | attackbotsspam | SSH Brute-Force attacks |
2019-10-03 06:02:55 |
| 193.77.216.143 | attackbots | SSH Brute-Force reported by Fail2Ban |
2019-10-03 06:13:43 |
| 222.186.52.86 | attack | Oct 2 17:52:48 ny01 sshd[26420]: Failed password for root from 222.186.52.86 port 46818 ssh2 Oct 2 17:52:49 ny01 sshd[26419]: Failed password for root from 222.186.52.86 port 17293 ssh2 Oct 2 17:52:50 ny01 sshd[26420]: Failed password for root from 222.186.52.86 port 46818 ssh2 |
2019-10-03 05:54:59 |
| 80.211.171.195 | attack | Oct 2 23:29:03 pornomens sshd\[27976\]: Invalid user cisco from 80.211.171.195 port 57034 Oct 2 23:29:03 pornomens sshd\[27976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.171.195 Oct 2 23:29:06 pornomens sshd\[27976\]: Failed password for invalid user cisco from 80.211.171.195 port 57034 ssh2 ... |
2019-10-03 06:15:30 |
| 222.186.42.163 | attack | 2019-10-03T05:08:12.709847enmeeting.mahidol.ac.th sshd\[32651\]: User root from 222.186.42.163 not allowed because not listed in AllowUsers 2019-10-03T05:08:13.063122enmeeting.mahidol.ac.th sshd\[32651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.163 user=root 2019-10-03T05:08:15.112668enmeeting.mahidol.ac.th sshd\[32651\]: Failed password for invalid user root from 222.186.42.163 port 39036 ssh2 ... |
2019-10-03 06:08:44 |
| 198.84.140.3 | attackbotsspam | Port scan on 1 port(s): 5555 |
2019-10-03 06:30:01 |
| 222.186.42.15 | attackbots | Oct 3 00:22:35 vmanager6029 sshd\[6955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.15 user=root Oct 3 00:22:36 vmanager6029 sshd\[6955\]: Failed password for root from 222.186.42.15 port 62042 ssh2 Oct 3 00:22:38 vmanager6029 sshd\[6955\]: Failed password for root from 222.186.42.15 port 62042 ssh2 |
2019-10-03 06:27:51 |
| 172.104.211.194 | attackbotsspam | Automatic report - Port Scan Attack |
2019-10-03 06:24:55 |
| 65.181.121.246 | attackspam | 2019-10-02T21:27:37.295576abusebot.cloudsearch.cf sshd\[28566\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=tor-exit-node.readme.tor-exit.xyz user=root |
2019-10-03 06:12:18 |
| 114.108.175.184 | attack | Oct 2 17:41:40 xtremcommunity sshd\[114771\]: Invalid user tomcat5 from 114.108.175.184 port 33852 Oct 2 17:41:40 xtremcommunity sshd\[114771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.108.175.184 Oct 2 17:41:42 xtremcommunity sshd\[114771\]: Failed password for invalid user tomcat5 from 114.108.175.184 port 33852 ssh2 Oct 2 17:45:44 xtremcommunity sshd\[114854\]: Invalid user tomee from 114.108.175.184 port 52694 Oct 2 17:45:44 xtremcommunity sshd\[114854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.108.175.184 ... |
2019-10-03 06:04:04 |
| 13.124.235.225 | attackspambots | 10/02/2019-18:00:15.741752 13.124.235.225 Protocol: 6 ET SCAN Potential SSH Scan |
2019-10-03 06:01:00 |
| 73.189.112.132 | attackbotsspam | Oct 3 00:16:29 dedicated sshd[3490]: Invalid user db2fenc1 from 73.189.112.132 port 42366 |
2019-10-03 06:24:00 |
| 138.68.93.14 | attack | Oct 2 23:25:27 tux-35-217 sshd\[20399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.93.14 user=root Oct 2 23:25:28 tux-35-217 sshd\[20399\]: Failed password for root from 138.68.93.14 port 35712 ssh2 Oct 2 23:29:32 tux-35-217 sshd\[20435\]: Invalid user basil from 138.68.93.14 port 48130 Oct 2 23:29:32 tux-35-217 sshd\[20435\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.93.14 ... |
2019-10-03 05:56:27 |
| 83.13.150.206 | attackbotsspam | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/83.13.150.206/ PL - 1H : (96) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : PL NAME ASN : ASN5617 IP : 83.13.150.206 CIDR : 83.8.0.0/13 PREFIX COUNT : 183 UNIQUE IP COUNT : 5363456 WYKRYTE ATAKI Z ASN5617 : 1H - 8 3H - 15 6H - 15 12H - 23 24H - 29 DateTime : 2019-10-02 23:29:17 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery |
2019-10-03 06:07:21 |