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

Region: Arizona

Country: United States

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-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       20.160.0.0 - 20.175.255.255
CIDR:           20.160.0.0/12
NetName:        MSFT
NetHandle:      NET-20-160-0-0-1
Parent:         NET20 (NET-20-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Microsoft Corporation (MSFT)
RegDate:        2017-02-22
Updated:        2017-02-22
Ref:            https://rdap.arin.net/registry/ip/20.160.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

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

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

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


#
# 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-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 20.169.85.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2936
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.169.85.11.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 06 11:31:57 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 11.85.169.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 11.85.169.20.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
151.73.109.81 attackspambots
Unauthorized connection attempt detected from IP address 151.73.109.81 to port 23 [J]
2020-01-17 21:54:57
51.161.12.231 attackbots
Unauthorized connection attempt detected from IP address 51.161.12.231 to port 8545 [J]
2020-01-17 21:39:33
112.85.42.172 attack
(sshd) Failed SSH login from 112.85.42.172 (CN/China/-): 5 in the last 3600 secs
2020-01-17 21:53:27
129.204.67.235 attack
2020-01-17T13:43:29.070868shield sshd\[24004\]: Invalid user 14 from 129.204.67.235 port 45228
2020-01-17T13:43:29.076027shield sshd\[24004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.67.235
2020-01-17T13:43:31.488816shield sshd\[24004\]: Failed password for invalid user 14 from 129.204.67.235 port 45228 ssh2
2020-01-17T13:46:10.326412shield sshd\[24348\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.67.235  user=root
2020-01-17T13:46:12.174204shield sshd\[24348\]: Failed password for root from 129.204.67.235 port 35988 ssh2
2020-01-17 21:58:01
18.162.225.45 attackbots
Unauthorized connection attempt detected from IP address 18.162.225.45 to port 2220 [J]
2020-01-17 21:57:19
197.98.201.122 attack
20/1/17@08:03:58: FAIL: Alarm-Network address from=197.98.201.122
20/1/17@08:03:58: FAIL: Alarm-Network address from=197.98.201.122
...
2020-01-17 22:12:24
106.13.54.207 attackbotsspam
Jan 17 13:54:59 vps58358 sshd\[24764\]: Invalid user uuu from 106.13.54.207Jan 17 13:55:01 vps58358 sshd\[24764\]: Failed password for invalid user uuu from 106.13.54.207 port 55012 ssh2Jan 17 13:59:27 vps58358 sshd\[24809\]: Invalid user user from 106.13.54.207Jan 17 13:59:30 vps58358 sshd\[24809\]: Failed password for invalid user user from 106.13.54.207 port 54158 ssh2Jan 17 14:03:57 vps58358 sshd\[24846\]: Invalid user sy from 106.13.54.207Jan 17 14:03:59 vps58358 sshd\[24846\]: Failed password for invalid user sy from 106.13.54.207 port 53296 ssh2
...
2020-01-17 22:11:13
117.84.156.147 attackbots
Telnet/23 MH Probe, BF, Hack -
2020-01-17 22:01:15
51.89.147.11 attackspambots
Mail/25/465/587-993/995 Probe, Reject, BadAuth, Hack, SPAM -
2020-01-17 21:55:30
222.252.16.154 attackbotsspam
Jan 17 14:04:42 amit sshd\[32120\]: Invalid user sftpuser from 222.252.16.154
Jan 17 14:04:42 amit sshd\[32120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.252.16.154
Jan 17 14:04:44 amit sshd\[32120\]: Failed password for invalid user sftpuser from 222.252.16.154 port 10416 ssh2
...
2020-01-17 21:30:13
178.221.245.120 attackspam
Unauthorized connection attempt detected from IP address 178.221.245.120 to port 80 [J]
2020-01-17 21:44:47
162.243.41.112 attackbots
Jan 17 14:03:43 rotator sshd\[31314\]: Failed password for root from 162.243.41.112 port 42291 ssh2Jan 17 14:03:46 rotator sshd\[31316\]: Failed password for root from 162.243.41.112 port 43993 ssh2Jan 17 14:03:51 rotator sshd\[31318\]: Failed password for root from 162.243.41.112 port 45844 ssh2Jan 17 14:03:53 rotator sshd\[31320\]: Invalid user zxin from 162.243.41.112Jan 17 14:03:55 rotator sshd\[31320\]: Failed password for invalid user zxin from 162.243.41.112 port 48559 ssh2Jan 17 14:04:00 rotator sshd\[31323\]: Failed password for root from 162.243.41.112 port 50734 ssh2
...
2020-01-17 22:04:30
85.108.3.33 attackspambots
1579266274 - 01/17/2020 14:04:34 Host: 85.108.3.33/85.108.3.33 Port: 445 TCP Blocked
2020-01-17 21:42:38
136.243.147.169 attack
Jan 17 14:27:36 eventyay sshd[17647]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.243.147.169
Jan 17 14:27:37 eventyay sshd[17647]: Failed password for invalid user mc from 136.243.147.169 port 56026 ssh2
Jan 17 14:28:09 eventyay sshd[17661]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=136.243.147.169
...
2020-01-17 21:37:31
140.143.199.169 attackspambots
2020-01-17T13:38:27.366203shield sshd\[22575\]: Invalid user fs from 140.143.199.169 port 56506
2020-01-17T13:38:27.373905shield sshd\[22575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.199.169
2020-01-17T13:38:29.325781shield sshd\[22575\]: Failed password for invalid user fs from 140.143.199.169 port 56506 ssh2
2020-01-17T13:40:48.066800shield sshd\[23376\]: Invalid user lily from 140.143.199.169 port 43014
2020-01-17T13:40:48.075585shield sshd\[23376\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.199.169
2020-01-17 21:53:00

Recently Reported IPs

42.234.6.211 223.89.11.196 222.138.40.104 211.97.115.165
163.125.248.219 129.28.95.210 1.28.90.113 118.24.70.191
115.49.163.209 112.32.4.68 110.16.3.255 20.168.124.97
104.208.73.227 182.122.92.179 221.232.8.143 169.40.142.190
183.250.118.51 140.224.166.122 47.95.201.46 39.100.77.193