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-2025, 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

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.168.122.83
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42438
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.168.122.83.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Oct 12 13:30:33 CST 2025
;; MSG SIZE  rcvd: 106
Host info
83.122.168.20.in-addr.arpa domain name pointer azpdws1jlxky.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
83.122.168.20.in-addr.arpa	name = azpdws1jlxky.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.147.139.216 attackspambots
2020-03-18 14:16:30 server sshd[60722]: Failed password for invalid user root from 190.147.139.216 port 55408 ssh2
2020-03-20 01:15:41
219.129.237.188 attackspam
ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic
2020-03-20 01:14:55
114.79.149.150 attackspambots
20/3/19@12:37:20: FAIL: Alarm-Network address from=114.79.149.150
...
2020-03-20 01:47:04
109.164.120.40 attack
Chat Spam
2020-03-20 01:28:41
203.192.204.168 attackspam
Mar 19 14:17:56 haigwepa sshd[18870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.192.204.168 
Mar 19 14:17:58 haigwepa sshd[18870]: Failed password for invalid user mc from 203.192.204.168 port 46408 ssh2
...
2020-03-20 01:33:31
124.158.179.34 attackbots
Unauthorized connection attempt from IP address 124.158.179.34 on Port 445(SMB)
2020-03-20 01:49:35
187.12.167.85 attack
Mar 19 15:34:42 sigma sshd\[21296\]: Invalid user teamspeak3 from 187.12.167.85Mar 19 15:34:44 sigma sshd\[21296\]: Failed password for invalid user teamspeak3 from 187.12.167.85 port 32818 ssh2
...
2020-03-20 01:29:32
213.204.81.159 attack
(sshd) Failed SSH login from 213.204.81.159 (LB/Lebanon/rev-213-204-81-159.terra.net.lb): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 19 16:42:38 amsweb01 sshd[9746]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.204.81.159  user=root
Mar 19 16:42:40 amsweb01 sshd[9746]: Failed password for root from 213.204.81.159 port 58054 ssh2
Mar 19 17:04:34 amsweb01 sshd[12039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.204.81.159  user=root
Mar 19 17:04:36 amsweb01 sshd[12039]: Failed password for root from 213.204.81.159 port 58594 ssh2
Mar 19 17:15:41 amsweb01 sshd[13313]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.204.81.159  user=root
2020-03-20 01:13:14
31.134.45.130 attackbots
Unauthorized connection attempt from IP address 31.134.45.130 on Port 445(SMB)
2020-03-20 01:05:56
47.252.7.222 attack
Brute forcing email accounts
2020-03-20 01:26:21
193.142.146.21 attackbotsspam
Mar 19 19:05:57 ift sshd\[63495\]: Failed password for root from 193.142.146.21 port 49716 ssh2Mar 19 19:06:00 ift sshd\[63510\]: Failed password for invalid user admin from 193.142.146.21 port 40498 ssh2Mar 19 19:06:00 ift sshd\[63512\]: Invalid user ubnt from 193.142.146.21Mar 19 19:06:02 ift sshd\[63512\]: Failed password for invalid user ubnt from 193.142.146.21 port 34416 ssh2Mar 19 19:06:04 ift sshd\[63529\]: Failed password for root from 193.142.146.21 port 54394 ssh2
...
2020-03-20 01:06:27
66.70.202.121 attackbots
Fail2Ban Ban Triggered
2020-03-20 01:35:11
198.98.60.141 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-03-20 01:42:33
134.209.44.17 attackbots
$f2bV_matches
2020-03-20 01:09:08
178.171.22.148 attackspambots
Chat Spam
2020-03-20 01:18:54

Recently Reported IPs

68.235.46.63 2408:8226:9d2b:4470:c350:b7a2:57a9:73ce 183.7.19.195 162.248.76.150
206.168.34.206 113.215.188.106 11.11.8.4 64.227.190.29
125.200.141.200 129.212.184.242 223.123.92.149 194.187.178.2
194.187.178.118 159.65.194.184 35.203.210.220 196.251.118.110
185.49.57.163 154.44.27.1 137.220.151.243 41.249.202.229