城市(city): unknown
省份(region): unknown
国家(country): IANA Special-Purpose Address
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 172.20.20.20 | bots | Stop hacking |
2024-05-27 11:22:45 |
| 172.20.20.20 | proxy | 2001:0002:14:5:1:2:bf35:2610. |
2024-05-27 11:20:27 |
| 172.20.20.20 | proxy | 2001:0002:14:5:1:2:bf35:2610. |
2024-05-27 11:20:18 |
| 172.20.20.20 | attack | 2001:0002:14:5:1:2:bf35:2610. |
2024-05-27 11:20:04 |
| 172.20.20.20 | attack | Bitches |
2024-05-27 11:18:56 |
| 172.20.20.20 | attack | Bitches |
2024-05-27 11:17:24 |
| 172.20.20.1 | attack | Bitches |
2024-05-27 11:17:09 |
| 172.20.243.93 | spam | Used for SPAM, PHISHING and SCAM on STOLLEN list we don't know, as usual with LIERS and ROBERS ! |
2020-02-10 19:29:18 |
| 172.20.21.30 | attackbots | Port 1433 Scan |
2019-10-12 07:25:27 |
#
# 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: 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-2025, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.20.2.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17626
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;172.20.2.2. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025110901 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 10 11:42:31 CST 2025
;; MSG SIZE rcvd: 103Host 2.2.20.172.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 2.2.20.172.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 64.227.58.213 | attackspam | Apr 17 05:55:04 mout sshd[28575]: Invalid user uv from 64.227.58.213 port 41362 Apr 17 05:55:05 mout sshd[28575]: Failed password for invalid user uv from 64.227.58.213 port 41362 ssh2 Apr 17 05:59:26 mout sshd[28750]: Invalid user postgres from 64.227.58.213 port 58970 |
2020-04-17 12:10:14 |
| 183.89.214.11 | attackbots | Dovecot Invalid User Login Attempt. |
2020-04-17 12:22:47 |
| 162.243.42.225 | attack | Apr 16 18:07:51 hpm sshd\[28701\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.42.225 user=root Apr 16 18:07:53 hpm sshd\[28701\]: Failed password for root from 162.243.42.225 port 35804 ssh2 Apr 16 18:13:03 hpm sshd\[29163\]: Invalid user postgres from 162.243.42.225 Apr 16 18:13:03 hpm sshd\[29163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.42.225 Apr 16 18:13:05 hpm sshd\[29163\]: Failed password for invalid user postgres from 162.243.42.225 port 43844 ssh2 |
2020-04-17 12:13:54 |
| 52.183.95.205 | attackspam | Invalid user zxin10 from 52.183.95.205 port 56952 |
2020-04-17 12:11:22 |
| 182.61.108.39 | attackbotsspam | Apr 17 05:59:19 debian-2gb-nbg1-2 kernel: \[9354936.851016\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=182.61.108.39 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=22421 PROTO=TCP SPT=47516 DPT=10602 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-04-17 12:17:25 |
| 139.59.95.149 | attack | Apr 17 06:23:11 OPSO sshd\[20897\]: Invalid user gd from 139.59.95.149 port 45680 Apr 17 06:23:12 OPSO sshd\[20897\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.95.149 Apr 17 06:23:13 OPSO sshd\[20897\]: Failed password for invalid user gd from 139.59.95.149 port 45680 ssh2 Apr 17 06:28:09 OPSO sshd\[21818\]: Invalid user postgres from 139.59.95.149 port 53104 Apr 17 06:28:09 OPSO sshd\[21818\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.95.149 |
2020-04-17 12:28:40 |
| 89.45.45.178 | attackbotsspam | Apr 16 19:59:46 ny01 sshd[4216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.45.45.178 Apr 16 19:59:47 ny01 sshd[4216]: Failed password for invalid user w from 89.45.45.178 port 54526 ssh2 Apr 16 20:03:37 ny01 sshd[4688]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.45.45.178 |
2020-04-17 08:30:33 |
| 180.250.247.45 | attackbots | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-04-17 08:20:38 |
| 159.89.170.20 | attack | 2020-04-16T23:44:24.287982shield sshd\[23478\]: Invalid user admin from 159.89.170.20 port 39184 2020-04-16T23:44:24.291974shield sshd\[23478\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.170.20 2020-04-16T23:44:25.800874shield sshd\[23478\]: Failed password for invalid user admin from 159.89.170.20 port 39184 ssh2 2020-04-16T23:48:43.054472shield sshd\[24500\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.170.20 user=root 2020-04-16T23:48:45.450192shield sshd\[24500\]: Failed password for root from 159.89.170.20 port 45340 ssh2 |
2020-04-17 08:31:51 |
| 183.89.212.15 | attack | IMAP brute force ... |
2020-04-17 12:28:11 |
| 51.91.212.81 | attackspam | 1587096298 - 04/17/2020 06:04:58 Host: 51.91.212.81/51.91.212.81 Port: 110 TCP Blocked |
2020-04-17 12:19:36 |
| 211.169.249.231 | attackbotsspam | Apr 17 04:14:28 vlre-nyc-1 sshd\[6606\]: Invalid user ol from 211.169.249.231 Apr 17 04:14:28 vlre-nyc-1 sshd\[6606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.231 Apr 17 04:14:30 vlre-nyc-1 sshd\[6606\]: Failed password for invalid user ol from 211.169.249.231 port 43596 ssh2 Apr 17 04:18:34 vlre-nyc-1 sshd\[6735\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.169.249.231 user=root Apr 17 04:18:36 vlre-nyc-1 sshd\[6735\]: Failed password for root from 211.169.249.231 port 52210 ssh2 ... |
2020-04-17 12:21:07 |
| 222.186.190.2 | attack | 2020-04-17T03:59:14.122028abusebot-8.cloudsearch.cf sshd[26495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.2 user=root 2020-04-17T03:59:16.345374abusebot-8.cloudsearch.cf sshd[26495]: Failed password for root from 222.186.190.2 port 2576 ssh2 2020-04-17T03:59:20.233938abusebot-8.cloudsearch.cf sshd[26495]: Failed password for root from 222.186.190.2 port 2576 ssh2 2020-04-17T03:59:14.122028abusebot-8.cloudsearch.cf sshd[26495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.2 user=root 2020-04-17T03:59:16.345374abusebot-8.cloudsearch.cf sshd[26495]: Failed password for root from 222.186.190.2 port 2576 ssh2 2020-04-17T03:59:20.233938abusebot-8.cloudsearch.cf sshd[26495]: Failed password for root from 222.186.190.2 port 2576 ssh2 2020-04-17T03:59:14.122028abusebot-8.cloudsearch.cf sshd[26495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= r ... |
2020-04-17 12:08:38 |
| 129.28.196.215 | attack | frenzy |
2020-04-17 12:23:10 |
| 54.37.14.3 | attack | (sshd) Failed SSH login from 54.37.14.3 (FR/France/3.ip-54-37-14.eu): 2 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 17 05:59:34 ubnt-55d23 sshd[7373]: Invalid user kz from 54.37.14.3 port 38436 Apr 17 05:59:35 ubnt-55d23 sshd[7373]: Failed password for invalid user kz from 54.37.14.3 port 38436 ssh2 |
2020-04-17 12:02:23 |