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-2025, American Registry for Internet Numbers, Ltd.
#


NetRange:       20.33.0.0 - 20.128.255.255
CIDR:           20.64.0.0/10, 20.34.0.0/15, 20.48.0.0/12, 20.36.0.0/14, 20.33.0.0/16, 20.128.0.0/16, 20.40.0.0/13
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

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


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

;; QUESTION SECTION:
;20.64.105.169.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 26 12:30:38 CST 2025
;; MSG SIZE  rcvd: 106
Host info
169.105.64.20.in-addr.arpa domain name pointer azpdsggyr6jk.stretchoid.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
169.105.64.20.in-addr.arpa	name = azpdsggyr6jk.stretchoid.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
185.208.208.198 attackspambots
Splunk® : port scan detected:
Jul 20 09:29:35 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=185.208.208.198 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=18082 PROTO=TCP SPT=48149 DPT=9947 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-20 23:11:21
23.226.135.105 attack
Malware
2019-07-20 23:17:51
185.148.243.190 attack
domain scam spam
2019-07-20 23:14:00
176.67.84.158 attackbots
Bruteforcing port 3389 (Remote Desktop) - Exceed maximum 10 attempts/hour
2019-07-20 23:01:04
182.61.160.15 attackspambots
Jul 20 15:16:02 ncomp sshd[14822]: Invalid user banner from 182.61.160.15
Jul 20 15:16:02 ncomp sshd[14822]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.160.15
Jul 20 15:16:02 ncomp sshd[14822]: Invalid user banner from 182.61.160.15
Jul 20 15:16:04 ncomp sshd[14822]: Failed password for invalid user banner from 182.61.160.15 port 49110 ssh2
2019-07-20 23:12:24
212.64.91.66 attack
Jul 20 17:40:43 eventyay sshd[5484]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.91.66
Jul 20 17:40:45 eventyay sshd[5484]: Failed password for invalid user bert from 212.64.91.66 port 51114 ssh2
Jul 20 17:44:53 eventyay sshd[6465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.64.91.66
...
2019-07-20 23:46:39
206.189.129.55 attackbots
Auto reported by IDS
2019-07-21 00:09:56
83.163.103.185 attackspambots
php WP PHPmyadamin ABUSE blocked for 12h
2019-07-20 23:46:02
103.97.125.49 attack
2019-07-20T15:41:22.957150abusebot-3.cloudsearch.cf sshd\[27728\]: Invalid user marco from 103.97.125.49 port 37718
2019-07-20 23:52:39
185.36.81.37 attack
GET wp-login
2019-07-21 00:31:02
186.159.114.227 attackbotsspam
19/7/20@07:37:58: FAIL: Alarm-Intrusion address from=186.159.114.227
...
2019-07-20 23:47:10
165.227.91.164 attackbotsspam
Caught in portsentry honeypot
2019-07-20 23:52:03
176.31.60.52 attackspam
2019-07-20T11:38:29.061416abusebot.cloudsearch.cf sshd\[1613\]: Invalid user jboss from 176.31.60.52 port 47026
2019-07-20 23:27:33
213.149.62.57 attackbots
C1,WP GET /lappan/wp-login.php
2019-07-20 23:06:07
177.184.245.92 attackbotsspam
failed_logins
2019-07-20 23:25:00

Recently Reported IPs

61.142.42.201 192.168.74.23 138.197.15.182 125.94.174.65
185.177.72.13 183.7.149.126 192.168.31.63 172.71.154.145
168.119.246.192 45.82.78.116 122.119.4.95 10.3.244.16
10.100.100.250 4.227.36.67 10.165.54.222 203.84.143.141
205.185.125.20 209.132.243.173 172.237.124.14 42.229.133.232