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.34.0.0/15, 20.33.0.0/16, 20.36.0.0/14, 20.40.0.0/13, 20.128.0.0/16, 20.64.0.0/10, 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

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

OrgRoutingHandle: CHATU3-ARIN
OrgRoutingName:   Chaturmohta, Somesh 
OrgRoutingPhone:  +1-425-882-8080 
OrgRoutingEmail:  someshch@microsoft.com
OrgRoutingRef:    https://rdap.arin.net/registry/entity/CHATU3-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.201.227
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4455
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;20.65.201.227.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 29 22:31:31 CST 2026
;; MSG SIZE  rcvd: 106
Host info
227.201.65.20.in-addr.arpa domain name pointer azpdss4yu8gw.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
227.201.65.20.in-addr.arpa	name = azpdss4yu8gw.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
13.76.94.26 attackspambots
$f2bV_matches
2020-07-18 06:22:09
217.219.23.161 attack
Unauthorised access (Jul 18) SRC=217.219.23.161 LEN=40 TOS=0x10 PREC=0x40 TTL=240 ID=35668 TCP DPT=1433 WINDOW=1024 SYN
2020-07-18 06:28:12
37.59.43.63 attackbots
k+ssh-bruteforce
2020-07-18 06:18:32
148.223.120.122 attack
2020-07-17T22:01:41.428218shield sshd\[24241\]: Invalid user sergey from 148.223.120.122 port 33839
2020-07-17T22:01:41.439559shield sshd\[24241\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.223.120.122
2020-07-17T22:01:44.006116shield sshd\[24241\]: Failed password for invalid user sergey from 148.223.120.122 port 33839 ssh2
2020-07-17T22:05:48.011627shield sshd\[24752\]: Invalid user administrator from 148.223.120.122 port 36490
2020-07-17T22:05:48.024851shield sshd\[24752\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.223.120.122
2020-07-18 06:09:15
79.136.70.159 attack
Jul 17 23:49:11 minden010 sshd[29467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.136.70.159
Jul 17 23:49:13 minden010 sshd[29467]: Failed password for invalid user avi from 79.136.70.159 port 57798 ssh2
Jul 17 23:56:06 minden010 sshd[30498]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.136.70.159
...
2020-07-18 06:19:15
45.116.112.22 attack
Jul 18 00:10:56 haigwepa sshd[12104]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.116.112.22 
Jul 18 00:10:59 haigwepa sshd[12104]: Failed password for invalid user w from 45.116.112.22 port 49136 ssh2
...
2020-07-18 06:32:51
38.68.48.11 attackbots
Suspicious access to SMTP/POP/IMAP services.
2020-07-18 06:25:54
139.199.85.241 attackbotsspam
Jul 17 18:21:25 NPSTNNYC01T sshd[10967]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.85.241
Jul 17 18:21:27 NPSTNNYC01T sshd[10967]: Failed password for invalid user m from 139.199.85.241 port 55418 ssh2
Jul 17 18:25:20 NPSTNNYC01T sshd[11174]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.85.241
...
2020-07-18 06:38:43
168.62.7.174 attack
Jul 18 00:30:20 serwer sshd\[8929\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.7.174  user=admin
Jul 18 00:30:20 serwer sshd\[8930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.62.7.174  user=admin
Jul 18 00:30:22 serwer sshd\[8929\]: Failed password for admin from 168.62.7.174 port 18868 ssh2
Jul 18 00:30:22 serwer sshd\[8930\]: Failed password for admin from 168.62.7.174 port 18875 ssh2
...
2020-07-18 06:37:38
104.211.245.131 attack
Brute-force attempt banned
2020-07-18 06:10:42
118.69.161.67 attackbots
2020-07-18T04:53:29.984341hostname sshd[1209]: Invalid user h1 from 118.69.161.67 port 50047
2020-07-18T04:53:32.361979hostname sshd[1209]: Failed password for invalid user h1 from 118.69.161.67 port 50047 ssh2
2020-07-18T04:58:42.720584hostname sshd[3839]: Invalid user nathan from 118.69.161.67 port 36095
...
2020-07-18 06:24:44
113.125.118.93 attackspambots
Jul 18 00:07:56 home sshd[30640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.118.93
Jul 18 00:08:06 home sshd[30640]: Failed password for invalid user cron from 113.125.118.93 port 55944 ssh2
Jul 18 00:14:42 home sshd[31887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.125.118.93
...
2020-07-18 06:25:38
148.70.195.242 attack
$f2bV_matches
2020-07-18 06:20:09
185.39.9.14 attackbots
firewall-block, port(s): 10014/tcp, 10049/tcp, 10057/tcp, 10066/tcp, 10067/tcp, 10091/tcp, 10137/tcp, 10204/tcp, 10284/tcp, 10287/tcp, 10297/tcp, 10301/tcp, 10354/tcp, 10358/tcp, 10364/tcp, 10366/tcp, 10373/tcp, 10386/tcp, 10395/tcp, 10411/tcp, 10412/tcp, 10416/tcp, 10421/tcp, 10504/tcp, 10535/tcp, 10539/tcp, 10547/tcp, 10630/tcp, 10683/tcp, 10694/tcp, 10743/tcp, 10760/tcp, 10776/tcp
2020-07-18 06:12:24
218.92.0.251 attackbotsspam
Jul 18 00:16:38 sshgateway sshd\[24792\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.251  user=root
Jul 18 00:16:40 sshgateway sshd\[24792\]: Failed password for root from 218.92.0.251 port 27834 ssh2
Jul 18 00:16:55 sshgateway sshd\[24792\]: error: maximum authentication attempts exceeded for root from 218.92.0.251 port 27834 ssh2 \[preauth\]
2020-07-18 06:24:05

Recently Reported IPs

43.106.101.195 169.40.142.224 39.154.5.12 39.154.10.91
223.88.237.182 183.199.180.161 183.197.169.44 120.82.85.163
120.230.21.90 120.230.107.93 167.99.229.144 193.34.212.94
213.136.68.185 218.78.5.81 178.128.251.47 216.180.246.16
106.75.66.241 167.71.72.195 47.43.253.169 157.230.138.173