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: San Antonio

Region: Texas

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.33.0.0 - 20.128.255.255
CIDR:           20.48.0.0/12, 20.64.0.0/10, 20.34.0.0/15, 20.36.0.0/14, 20.40.0.0/13, 20.128.0.0/16, 20.33.0.0/16
NetName:        MSFT
NetHandle:      NET-20-33-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.33.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.65.202.138
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21459
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.202.138.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 05 09:31:08 CST 2026
;; MSG SIZE  rcvd: 106
Host info
138.202.65.20.in-addr.arpa domain name pointer azpdsgwe6dv9.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
138.202.65.20.in-addr.arpa	name = azpdsgwe6dv9.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
110.139.207.18 attackbotsspam
Invalid user peh from 110.139.207.18 port 34986
2019-12-24 22:06:17
222.186.175.163 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
Failed password for root from 222.186.175.163 port 20292 ssh2
Failed password for root from 222.186.175.163 port 20292 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.163  user=root
Failed password for root from 222.186.175.163 port 33034 ssh2
2019-12-24 22:25:40
51.38.93.221 attackspambots
SIP/5060 Probe, BF, Hack -
2019-12-24 22:25:20
134.175.54.130 attack
Dec 24 11:02:45 lnxweb61 sshd[26674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.54.130
2019-12-24 22:17:21
92.118.160.53 attack
firewall-block, port(s): 7547/tcp
2019-12-24 22:11:05
64.50.186.5 attackbots
64.50.186.5 - - [24/Dec/2019:07:41:43 +0000] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
64.50.186.5 - - [24/Dec/2019:07:41:45 +0000] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2019-12-24 22:24:02
119.28.158.60 attackbotsspam
Automatic report - SSH Brute-Force Attack
2019-12-24 22:15:57
46.0.203.166 attackspam
Dec 24 15:11:42 localhost sshd\[22587\]: Invalid user melodee from 46.0.203.166 port 40134
Dec 24 15:11:42 localhost sshd\[22587\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166
Dec 24 15:11:44 localhost sshd\[22587\]: Failed password for invalid user melodee from 46.0.203.166 port 40134 ssh2
2019-12-24 22:22:09
54.38.36.244 attackbots
Automatic report - Banned IP Access
2019-12-24 22:34:32
106.12.46.104 attack
Dec 24 14:22:47 dedicated sshd[13772]: Invalid user 1QAZ3EDC from 106.12.46.104 port 47558
2019-12-24 21:55:45
178.128.25.171 attackspam
$f2bV_matches
2019-12-24 22:12:31
61.178.103.144 attackbotsspam
port scan and connect, tcp 1433 (ms-sql-s)
2019-12-24 22:12:08
185.62.136.55 attackspambots
Automatic report - Banned IP Access
2019-12-24 22:19:32
45.125.66.194 attackbotsspam
Dec 24 09:07:25 web1 postfix/smtpd[22425]: warning: unknown[45.125.66.194]: SASL LOGIN authentication failed: authentication failure
...
2019-12-24 22:18:34
206.189.156.198 attack
Dec 24 13:27:52 lnxweb61 sshd[28559]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.156.198
2019-12-24 22:05:17

Recently Reported IPs

52.4.70.81 200.138.46.7 200.138.46.38 185.216.145.175
13.222.254.172 202.26.128.228 202.126.128.228 240a:42bc:d402:751:289c:c5ff:fe35:d709
113.132.238.102 2408:8220:6a25:4a70:5c54:4fce:88dd:3e03 118.196.75.126 36.34.161.61
221.205.247.142 211.161.118.56 170.64.237.148 165.227.222.40
142.93.228.87 69.165.65.191 153.117.28.170 20.106.51.120