Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: IANA Special-Purpose Address

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
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
Whois info:
#
# 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 info:
; <<>> 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: 103
Host info
Host 2.2.20.172.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 2.2.20.172.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
46.219.215.51 attackspambots
Unauthorized connection attempt from IP address 46.219.215.51 on Port 445(SMB)
2020-07-14 05:28:34
122.160.199.154 attack
Unauthorized connection attempt from IP address 122.160.199.154 on Port 445(SMB)
2020-07-14 05:57:40
111.95.141.34 attackspam
2020-07-13T23:46:08.250868vps751288.ovh.net sshd\[22263\]: Invalid user postgres from 111.95.141.34 port 47991
2020-07-13T23:46:08.268057vps751288.ovh.net sshd\[22263\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.95.141.34
2020-07-13T23:46:10.555790vps751288.ovh.net sshd\[22263\]: Failed password for invalid user postgres from 111.95.141.34 port 47991 ssh2
2020-07-13T23:47:05.314888vps751288.ovh.net sshd\[22269\]: Invalid user deploy from 111.95.141.34 port 55215
2020-07-13T23:47:05.327492vps751288.ovh.net sshd\[22269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.95.141.34
2020-07-14 05:59:50
134.209.97.42 attackbots
Invalid user postgres from 134.209.97.42 port 34916
2020-07-14 05:34:01
14.165.20.45 attackbotsspam
Unauthorized connection attempt from IP address 14.165.20.45 on Port 445(SMB)
2020-07-14 05:59:27
218.92.0.138 attack
Jul 13 23:31:54 eventyay sshd[4720]: Failed password for root from 218.92.0.138 port 15156 ssh2
Jul 13 23:32:07 eventyay sshd[4720]: error: maximum authentication attempts exceeded for root from 218.92.0.138 port 15156 ssh2 [preauth]
Jul 13 23:32:12 eventyay sshd[4723]: Failed password for root from 218.92.0.138 port 41196 ssh2
...
2020-07-14 05:39:54
188.166.230.236 attackspambots
2020-07-13T16:37:33.622522mail.thespaminator.com sshd[9549]: Invalid user nora from 188.166.230.236 port 36138
2020-07-13T16:37:35.676795mail.thespaminator.com sshd[9549]: Failed password for invalid user nora from 188.166.230.236 port 36138 ssh2
...
2020-07-14 06:02:27
113.88.113.105 attackspam
Unauthorized connection attempt from IP address 113.88.113.105 on Port 445(SMB)
2020-07-14 05:52:21
217.11.65.146 attack
Jul 13 22:31:18 smtp postfix/smtpd[25548]: NOQUEUE: reject: RCPT from unknown[217.11.65.146]: 554 5.7.1 Service unavailable; Client host [217.11.65.146] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?217.11.65.146; from= to= proto=ESMTP helo=<[217.11.65.146]>
...
2020-07-14 05:41:48
179.222.115.170 attack
Unauthorized connection attempt from IP address 179.222.115.170 on Port 445(SMB)
2020-07-14 05:33:40
45.138.74.46 spamattack
attack on 2020-07-13

Return-Path: 
Received: from [217.72.192.66] ([217.72.192.66]) by mx.emig.kundenserver.de
 (mxeue112 [217.72.192.66]) with ESMTP (Nemesis) id 1MNMAm-1kFToG3oRW-00Oqlo
 for ; Mon, 13 Jul 2020 20:32:19 +0200
Received: from kjtyz.hjgdfsdbgfgh.bw ([45.138.74.46]) by
 mx.emig.kundenserver.de (mxeue112 [217.72.192.66]) with ESMTP (Nemesis) id
 1N8YgJ-1kzEkF3lon-014X2V for ; Mon, 13 Jul 2020 20:32:18
 +0200
Received: from thing.nutrimment.nl () by mx.emig.kundenserver.de (mxeue110 ) with ESMTP (Nemesis) id 1MeBpR-1kTyvO0IHX-00bLGO for ; Mon, 13 Jul 2020 11:23:53 +0200
Date: Tue, 31 Dec 2105 23:59:59 +0100
From: =?UTF-8?B?TWNEb25hbGRcJ3M=?= 
To: lilly@online.de
Message-ID: 
2020-07-14 05:49:19
27.109.129.83 attack
Automatic report - Port Scan Attack
2020-07-14 05:52:58
1.119.131.102 attackbots
Jul 13 22:24:44 server sshd[65262]: Failed password for invalid user el from 1.119.131.102 port 40831 ssh2
Jul 13 22:28:10 server sshd[2939]: Failed password for invalid user lab from 1.119.131.102 port 28858 ssh2
Jul 13 22:31:28 server sshd[5435]: Failed password for invalid user office from 1.119.131.102 port 16884 ssh2
2020-07-14 05:33:12
222.239.124.19 attackspambots
644. On Jul 13 2020 experienced a Brute Force SSH login attempt -> 3 unique times by 222.239.124.19.
2020-07-14 06:03:10
162.247.74.202 attackspambots
Brute forcing RDP port 3389
2020-07-14 05:40:22

Recently Reported IPs

98.94.66.237 147.93.190.168 47.98.164.140 91.230.168.24
91.230.168.20 59.96.139.164 219.136.105.136 183.186.228.202
49.4.32.31 159.138.86.200 121.36.117.176 49.4.17.87
49.4.43.77 116.179.37.227 10.50.111.235 172.20.2.1
157.175.76.105 170.64.173.170 162.216.150.179 183.82.110.60