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.64.0.0/10, 20.33.0.0/16, 20.40.0.0/13, 20.128.0.0/16, 20.36.0.0/14, 20.34.0.0/15, 20.48.0.0/12
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: 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

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


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

;; QUESTION SECTION:
;20.65.195.32.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 16 06:00:27 CST 2026
;; MSG SIZE  rcvd: 105
Host info
32.195.65.20.in-addr.arpa domain name pointer azpdsscmedp5.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
32.195.65.20.in-addr.arpa	name = azpdsscmedp5.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.215.20.248 attack
DATE:2020-02-09 05:47:36, IP:106.215.20.248, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-02-09 20:23:13
180.76.108.151 attack
Feb 09 00:41:44 askasleikir sshd[89792]: Failed password for invalid user lyq from 180.76.108.151 port 47182 ssh2
2020-02-09 20:22:47
27.122.12.248 attackbots
Brute force VPN server
2020-02-09 20:10:21
117.41.200.16 attackbots
Feb  9 09:17:28 work-partkepr sshd\[1511\]: Invalid user top from 117.41.200.16 port 50994
Feb  9 09:17:28 work-partkepr sshd\[1511\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.41.200.16
...
2020-02-09 20:05:16
217.170.205.107 attackspambots
Unauthorized access detected from black listed ip!
2020-02-09 20:46:11
85.132.100.24 attackbotsspam
Feb  9 13:42:00 MK-Soft-VM3 sshd[13580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.132.100.24 
Feb  9 13:42:02 MK-Soft-VM3 sshd[13580]: Failed password for invalid user hma from 85.132.100.24 port 38626 ssh2
...
2020-02-09 20:45:18
219.73.37.142 attack
unauthorized connection attempt
2020-02-09 20:48:07
49.88.112.72 attack
Feb  9 11:01:38 eventyay sshd[11252]: Failed password for root from 49.88.112.72 port 54622 ssh2
Feb  9 11:02:32 eventyay sshd[11256]: Failed password for root from 49.88.112.72 port 60359 ssh2
...
2020-02-09 20:04:50
99.29.90.25 attack
Feb  8 19:17:42 hpm sshd\[20073\]: Invalid user xsk from 99.29.90.25
Feb  8 19:17:42 hpm sshd\[20073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.29.90.25
Feb  8 19:17:44 hpm sshd\[20073\]: Failed password for invalid user xsk from 99.29.90.25 port 50935 ssh2
Feb  8 19:20:52 hpm sshd\[20456\]: Invalid user luh from 99.29.90.25
Feb  8 19:20:52 hpm sshd\[20456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=99.29.90.25
2020-02-09 20:35:30
78.187.179.18 attackbots
Automatic report - Banned IP Access
2020-02-09 20:21:03
114.37.15.87 attack
unauthorized connection attempt
2020-02-09 20:34:05
222.160.173.24 attack
23/tcp
[2020-02-09]1pkt
2020-02-09 20:26:52
45.177.95.87 attackbots
Automatic report - Port Scan Attack
2020-02-09 20:45:42
60.190.114.82 attackspam
Feb  9 15:22:09 gw1 sshd[28396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.190.114.82
Feb  9 15:22:12 gw1 sshd[28396]: Failed password for invalid user jdb from 60.190.114.82 port 53039 ssh2
...
2020-02-09 20:40:12
221.210.237.3 attackspam
unauthorized connection attempt
2020-02-09 20:52:36

Recently Reported IPs

100.26.194.24 103.86.65.196 103.86.65.150 47.128.122.92
66.132.195.68 122.193.247.139 2606:4700:10::6814:8149 2606:4700:10::6814:4362
2606:4700:10::6814:6693 2606:4700:10::6814:7103 2606:4700:10::6814:8839 118.189.97.188
121.230.89.103 2606:4700:10::6814:7307 2606:4700:10::6816:3313 2606:4700:10::6814:6379
2606:4700:10::6814:4535 46.101.46.29 95.85.94.242 222.176.201.165