No — windows.net is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
windows.net has no AAAA record.		no
www over IPv6
www.windows.net has no AAAA record.		no
Mail servers (MX) have IPv6
No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record.		no
Nameservers have IPv6
4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns1-39.azure-dns.com ✓ns2-39.azure-dns.net ✓ns3-39.azure-dns.org ✓ns4-39.azure-dns.info ✓
yes

What's keeping windows.net from an A

  1. Give windows.net an IPv6 address
    Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
  2. www.windows.net is an alias of windows.net, which has no IPv6
    www.windows.net is a CNAME, so it can't also have its own AAAA record. Ask whoever runs windows.net to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6
  3. Mail servers without IPv6
    Your domain's mail goes to its own address, which has no AAAA record.

Check again

windows.net  IPv4 only

A (IPv4)20.76.201.171
20.112.250.133
20.236.44.162
20.231.239.246
20.70.246.20
AAAA (IPv6)none

www.windows.net  IPv4 only

Alias ofwindows.net
A (IPv4)20.112.250.133
20.231.239.246
20.236.44.162
20.70.246.20
20.76.201.171
AAAA (IPv6)none

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Checked 2026-10-30 14:52:01 UTC — one of the top 1,000 sites, re-checked weekly. Re-check now. Full DNS report: dns.pizza/domain/windows.net · JSON: /api/v1/windows.net