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.128.0.0/16, 20.36.0.0/14, 20.48.0.0/12, 20.64.0.0/10, 20.34.0.0/15, 20.40.0.0/13, 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: 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.193.189
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10944
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.193.189.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon May 18 05:00:30 CST 2026
;; MSG SIZE  rcvd: 106
Host info
189.193.65.20.in-addr.arpa domain name pointer azpdssk37fij.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
189.193.65.20.in-addr.arpa	name = azpdssk37fij.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
95.70.235.167 attack
DATE:2020-05-31 05:53:20, IP:95.70.235.167, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-05-31 14:52:03
86.69.2.215 attack
5x Failed Password
2020-05-31 14:43:05
37.49.226.55 attackspambots
Invalid user user from 37.49.226.55 port 57208
2020-05-31 14:39:11
146.185.130.101 attack
Invalid user es from 146.185.130.101 port 55392
2020-05-31 14:32:01
144.217.93.78 attackbots
prod11
...
2020-05-31 15:02:28
104.131.189.4 attack
Triggered by Fail2Ban at Ares web server
2020-05-31 14:59:19
154.92.15.208 attackbotsspam
$f2bV_matches
2020-05-31 15:01:21
35.232.185.125 attackbotsspam
$f2bV_matches
2020-05-31 14:21:27
201.219.50.217 attack
May 30 02:16:00 pl1server sshd[13781]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.219.50.217  user=r.r
May 30 02:16:02 pl1server sshd[13781]: Failed password for r.r from 201.219.50.217 port 44358 ssh2
May 30 02:16:02 pl1server sshd[13781]: Received disconnect from 201.219.50.217: 11: Bye Bye [preauth]
May 30 02:25:14 pl1server sshd[16194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.219.50.217  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=201.219.50.217
2020-05-31 14:49:30
147.158.157.6 attack
Fail2Ban - HTTP Auth Bruteforce Attempt
2020-05-31 14:46:27
51.68.44.13 attack
SSH auth scanning - multiple failed logins
2020-05-31 14:45:49
202.148.28.83 attackspam
May 31 06:50:34 cdc sshd[4818]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.148.28.83  user=root
May 31 06:50:37 cdc sshd[4818]: Failed password for invalid user root from 202.148.28.83 port 56724 ssh2
2020-05-31 14:41:00
211.23.125.95 attackbotsspam
May 30 19:17:31 web1 sshd\[6786\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.23.125.95  user=root
May 30 19:17:34 web1 sshd\[6786\]: Failed password for root from 211.23.125.95 port 53608 ssh2
May 30 19:20:15 web1 sshd\[7044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.23.125.95  user=root
May 30 19:20:16 web1 sshd\[7044\]: Failed password for root from 211.23.125.95 port 39892 ssh2
May 30 19:22:55 web1 sshd\[7250\]: Invalid user zyuser from 211.23.125.95
May 30 19:22:55 web1 sshd\[7250\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.23.125.95
2020-05-31 14:49:42
149.56.107.118 attack
TCP port 3388: Scan and connection
2020-05-31 14:53:56
106.52.80.21 attack
May 31 06:30:16 melroy-server sshd[17690]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.80.21 
May 31 06:30:18 melroy-server sshd[17690]: Failed password for invalid user admin from 106.52.80.21 port 37156 ssh2
...
2020-05-31 15:00:45

Recently Reported IPs

69.5.169.142 118.14.235.243 2606:4700:10::6814:9360 109.162.246.221
2606:4700:10::6814:9430 54.208.25.95 18.206.156.151 47.114.101.166
43.159.57.144 159.223.231.115 115.29.199.209 104.248.197.12
45.79.122.161 129.226.95.137 66.132.195.98 110.77.248.91
164.155.74.116 128.241.235.26 27.47.27.24 182.242.168.71