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: Tokyo

Region: Tokyo

Country: Japan

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:
No discussion about this subnet yet..
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:       20.192.0.0 - 20.255.255.255
CIDR:           20.192.0.0/10
NetName:        MSFT
NetHandle:      NET-20-192-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-10-18
Updated:        2021-12-14
Ref:            https://rdap.arin.net/registry/ip/20.192.0.0



OrgName:        Microsoft Corporation
OrgId:          MSFT
Address:        One Microsoft Way
City:           Redmond
StateProv:      WA
PostalCode:     98052
Country:        US
RegDate:        1998-07-10
Updated:        2025-06-10
Comment:        To report suspected security issues specific to traffic emanating from Microsoft online services, including the distribution of malicious content or other illicit or illegal material through a Microsoft online service, please submit reports to:
Comment:        * https://cert.microsoft.com.  
Comment:        
Comment:        For SPAM and other abuse issues, such as Microsoft Accounts, please contact:
Comment:        * abuse@microsoft.com.  
Comment:        
Comment:        To report security vulnerabilities in Microsoft products and services, please contact:
Comment:        * secure@microsoft.com.  
Comment:        
Comment:        For legal and law enforcement-related requests, please contact:
Comment:        * msndcc@microsoft.com
Comment:        
Comment:        For routing, peering or DNS issues, please 
Comment:        contact:
Comment:        * IOC@microsoft.com
Ref:            https://rdap.arin.net/registry/entity/MSFT


OrgTechHandle: BEDAR6-ARIN
OrgTechName:   Bedard, Dawn 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  dabedard@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/BEDAR6-ARIN

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-ARIN

OrgAbuseHandle: MAC74-ARIN
OrgAbuseName:   Microsoft Abuse Contact
OrgAbusePhone:  +1-425-882-8080 
OrgAbuseEmail:  abuse@microsoft.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/MAC74-ARIN

OrgTechHandle: IPHOS5-ARIN
OrgTechName:   IPHostmaster, IPHostmaster 
OrgTechPhone:  +1-425-538-6637 
OrgTechEmail:  iphostmaster@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/IPHOS5-ARIN

OrgTechHandle: SINGH683-ARIN
OrgTechName:   Singh, Prachi 
OrgTechPhone:  +1-425-707-5601 
OrgTechEmail:  pracsin@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/SINGH683-ARIN

OrgTechHandle: MRPD-ARIN
OrgTechName:   Microsoft Routing, Peering, and DNS
OrgTechPhone:  +1-425-882-8080 
OrgTechEmail:  IOC@microsoft.com
OrgTechRef:    https://rdap.arin.net/registry/entity/MRPD-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 <<>> 20.222.66.73
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43709
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.222.66.73.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025110901 1800 900 604800 86400

;; Query time: 894 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 10 08:00:04 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 73.66.222.20.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 73.66.222.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
169.55.188.230 attack
Jul 25 13:33:41 ArkNodeAT sshd\[21773\]: Invalid user tomcat from 169.55.188.230
Jul 25 13:33:41 ArkNodeAT sshd\[21773\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=169.55.188.230
Jul 25 13:33:43 ArkNodeAT sshd\[21773\]: Failed password for invalid user tomcat from 169.55.188.230 port 60972 ssh2
2019-07-25 19:58:21
139.59.135.84 attackbots
Invalid user abcd from 139.59.135.84 port 52570
2019-07-25 20:20:06
51.79.69.48 attackbots
Jul 25 07:16:30 tux-35-217 sshd\[1869\]: Invalid user mysql from 51.79.69.48 port 45028
Jul 25 07:16:30 tux-35-217 sshd\[1869\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.69.48
Jul 25 07:16:32 tux-35-217 sshd\[1869\]: Failed password for invalid user mysql from 51.79.69.48 port 45028 ssh2
Jul 25 07:21:15 tux-35-217 sshd\[1883\]: Invalid user teamspeak from 51.79.69.48 port 41778
Jul 25 07:21:15 tux-35-217 sshd\[1883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.69.48
...
2019-07-25 20:23:42
91.228.118.36 attackspambots
Automatic report - Port Scan Attack
2019-07-25 20:20:32
185.164.72.117 spambots
A lockdown event has occurred due to too many failed login attempts or invalid username:
Username: admin
IP Address: 185.164.72.117

IP Range: 185.164.72.*

Log into your site's WordPress administration panel to see the duration of the lockout or to unlock the user.
2019-07-25 20:39:36
150.95.140.160 attackbots
Jul 25 13:42:01 rpi sshd[11992]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.95.140.160 
Jul 25 13:42:03 rpi sshd[11992]: Failed password for invalid user www from 150.95.140.160 port 47764 ssh2
2019-07-25 20:08:58
94.23.208.211 attackbots
Jul 25 18:04:31 vibhu-HP-Z238-Microtower-Workstation sshd\[16403\]: Invalid user blog from 94.23.208.211
Jul 25 18:04:31 vibhu-HP-Z238-Microtower-Workstation sshd\[16403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.208.211
Jul 25 18:04:33 vibhu-HP-Z238-Microtower-Workstation sshd\[16403\]: Failed password for invalid user blog from 94.23.208.211 port 34172 ssh2
Jul 25 18:08:54 vibhu-HP-Z238-Microtower-Workstation sshd\[17431\]: Invalid user aaron from 94.23.208.211
Jul 25 18:08:54 vibhu-HP-Z238-Microtower-Workstation sshd\[17431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.208.211
...
2019-07-25 20:41:25
122.195.200.148 attack
Jul 25 14:41:29 legacy sshd[15982]: Failed password for root from 122.195.200.148 port 18910 ssh2
Jul 25 14:41:39 legacy sshd[15991]: Failed password for root from 122.195.200.148 port 59045 ssh2
Jul 25 14:41:42 legacy sshd[15991]: Failed password for root from 122.195.200.148 port 59045 ssh2
...
2019-07-25 20:52:39
200.181.121.154 attack
Jul 25 08:21:06 microserver sshd[51771]: Invalid user b from 200.181.121.154 port 38558
Jul 25 08:21:06 microserver sshd[51771]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.181.121.154
Jul 25 08:21:08 microserver sshd[51771]: Failed password for invalid user b from 200.181.121.154 port 38558 ssh2
Jul 25 08:26:54 microserver sshd[52604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.181.121.154  user=root
Jul 25 08:26:55 microserver sshd[52604]: Failed password for root from 200.181.121.154 port 33732 ssh2
Jul 25 08:38:44 microserver sshd[54163]: Invalid user test from 200.181.121.154 port 52324
Jul 25 08:38:44 microserver sshd[54163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.181.121.154
Jul 25 08:38:46 microserver sshd[54163]: Failed password for invalid user test from 200.181.121.154 port 52324 ssh2
Jul 25 08:44:34 microserver sshd[54969]: Invalid user system from 2
2019-07-25 20:38:21
167.99.118.194 attackspambots
Automatic report - Banned IP Access
2019-07-25 20:49:50
202.29.70.42 attackspam
Jul 25 08:41:48 plusreed sshd[14354]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.29.70.42  user=root
Jul 25 08:41:50 plusreed sshd[14354]: Failed password for root from 202.29.70.42 port 50282 ssh2
...
2019-07-25 20:47:07
109.172.106.200 attackspam
Jul 25 07:33:33 microserver sshd[44620]: Invalid user sk from 109.172.106.200 port 45332
Jul 25 07:33:33 microserver sshd[44620]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.172.106.200
Jul 25 07:33:35 microserver sshd[44620]: Failed password for invalid user sk from 109.172.106.200 port 45332 ssh2
Jul 25 07:38:01 microserver sshd[45313]: Invalid user position from 109.172.106.200 port 58660
Jul 25 07:38:01 microserver sshd[45313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.172.106.200
Jul 25 07:52:46 microserver sshd[47598]: Invalid user gert from 109.172.106.200 port 42238
Jul 25 07:52:46 microserver sshd[47598]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.172.106.200
Jul 25 07:52:48 microserver sshd[47598]: Failed password for invalid user gert from 109.172.106.200 port 42238 ssh2
Jul 25 07:57:38 microserver sshd[48295]: Invalid user niclas from 109.172.106.200 po
2019-07-25 20:40:01
81.133.73.161 attack
2019-07-25T12:41:48.976808abusebot-2.cloudsearch.cf sshd\[9066\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=host81-133-73-161.in-addr.btopenworld.com  user=root
2019-07-25 20:50:18
139.59.56.121 attackspambots
Invalid user zimbra from 139.59.56.121 port 56568
2019-07-25 20:25:50
125.88.177.12 attackbotsspam
Jul 25 06:47:22 server sshd\[5956\]: Invalid user nagios from 125.88.177.12 port 39212
Jul 25 06:47:22 server sshd\[5956\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.12
Jul 25 06:47:24 server sshd\[5956\]: Failed password for invalid user nagios from 125.88.177.12 port 39212 ssh2
Jul 25 06:49:43 server sshd\[32410\]: Invalid user diana from 125.88.177.12 port 55259
Jul 25 06:49:43 server sshd\[32410\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.88.177.12
2019-07-25 20:40:22

Recently Reported IPs

8.222.154.87 8.219.82.84 8.219.241.183 47.99.62.117
8.219.2.88 47.84.16.14 44.201.212.55 3.91.205.122
34.224.29.202 34.207.182.99 36.133.211.61 34.116.226.212
43.153.99.164 106.75.16.45 112.4.101.72 102.113.130.216
64.139.13.126 43.154.200.147 98.94.66.237 147.93.190.168