City: unknown
Region: unknown
Country: IANA Special-Purpose Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 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.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20566
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;172.20.2.1. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025110901 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 10 11:42:45 CST 2025
;; MSG SIZE rcvd: 103Host 1.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 1.2.20.172.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 119.193.27.90 | attackspam | May 2 10:38:54 itv-usvr-01 sshd[11200]: Invalid user ef from 119.193.27.90 May 2 10:38:54 itv-usvr-01 sshd[11200]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.193.27.90 May 2 10:38:54 itv-usvr-01 sshd[11200]: Invalid user ef from 119.193.27.90 May 2 10:38:57 itv-usvr-01 sshd[11200]: Failed password for invalid user ef from 119.193.27.90 port 43409 ssh2 May 2 10:46:55 itv-usvr-01 sshd[11584]: Invalid user elizabeth from 119.193.27.90 |
2020-05-02 20:17:26 |
| 177.30.47.9 | attack | May 2 14:01:01 piServer sshd[2936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.30.47.9 May 2 14:01:02 piServer sshd[2936]: Failed password for invalid user nancy from 177.30.47.9 port 41536 ssh2 May 2 14:05:31 piServer sshd[3378]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.30.47.9 ... |
2020-05-02 20:08:40 |
| 181.211.247.233 | attackbots | Unauthorized connection attempt from IP address 181.211.247.233 on Port 445(SMB) |
2020-05-02 20:22:38 |
| 116.247.81.99 | attack | Invalid user renjiawei from 116.247.81.99 port 46294 |
2020-05-02 20:07:44 |
| 208.107.64.68 | attackspambots | Brute forcing email accounts |
2020-05-02 20:27:25 |
| 212.33.240.140 | attack | email spam |
2020-05-02 20:00:01 |
| 170.33.14.19 | attackbotsspam | Port scanning |
2020-05-02 20:33:12 |
| 89.97.218.142 | attack | May 2 10:36:36 *** sshd[7405]: Invalid user mri from 89.97.218.142 |
2020-05-02 19:59:35 |
| 35.239.187.6 | attack | Port scan(s) denied |
2020-05-02 20:10:30 |
| 103.84.131.10 | attackbotsspam | Unauthorized connection attempt from IP address 103.84.131.10 on Port 445(SMB) |
2020-05-02 20:32:39 |
| 82.118.236.186 | attack | SSH brutforce |
2020-05-02 20:01:32 |
| 66.70.130.151 | attackspambots | Automatic report BANNED IP |
2020-05-02 19:58:13 |
| 167.71.102.186 | attackbotsspam | May 2 14:47:33 hosting sshd[23578]: Invalid user brian from 167.71.102.186 port 47408 ... |
2020-05-02 19:56:06 |
| 152.67.67.89 | attackspambots | May 2 10:47:42 vlre-nyc-1 sshd\[10592\]: Invalid user stue from 152.67.67.89 May 2 10:47:42 vlre-nyc-1 sshd\[10592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.67.67.89 May 2 10:47:45 vlre-nyc-1 sshd\[10592\]: Failed password for invalid user stue from 152.67.67.89 port 59756 ssh2 May 2 10:53:22 vlre-nyc-1 sshd\[10828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.67.67.89 user=root May 2 10:53:24 vlre-nyc-1 sshd\[10828\]: Failed password for root from 152.67.67.89 port 58784 ssh2 ... |
2020-05-02 20:03:36 |
| 218.92.0.198 | attackbots | May 2 13:39:08 vmanager6029 sshd\[14165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.198 user=root May 2 13:39:09 vmanager6029 sshd\[14093\]: error: PAM: Authentication failure for root from 218.92.0.198 May 2 13:39:12 vmanager6029 sshd\[14166\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.198 user=root |
2020-05-02 20:08:20 |