DNS operator · Snapshot 23 October 2026
Sites on Azure DNS
547 measured sites rely on Azure DNS as their dns operator. How common it is by popularity band, how its customers configure related checks, and the continuity steps worth taking.
- Sites
- 547
- Median readiness index
- 64/100
- Profiles
- 205
1.4% of all measured sites
all sites: 64
top-50K sites
Share by popularity band
| Chrome UX Report band | Share of measured sites | Sites |
|---|---|---|
| Top 1K | 1.5% | 7 |
| Top 5K | <1% | 20 |
| Top 10K | 1.2% | 31 |
| Top 50K | 1.5% | 272 |
| Top 100K | 1.7% | 92 |
| Top 500K | 1.4% | 73 |
| Top 1M | <1% | 52 |
Related checks among Azure DNS customers
| Check | Lane | Observed | All sites | Measured |
|---|---|---|---|---|
| Nameservers spread across providers | Recover | 2% | 10% | 547 |
| DNSSEC signed | Harden | 7.9% | 8% | 545 |
| CAA records limit who can issue certificates | Harden | 13% | 13% | 544 |
| Reachable over IPv6 | Enable | 39% | 48% | 545 |
| DMARC policy enforces quarantine or reject | Harden | 61% | 39% | 546 |
Continuity steps for Azure DNS customers
- Consider a secondary DNS operator. RFC 2182 recommends nameservers on diverse networks so a single failure cannot make the zone unreachable; many operators support zone transfers or multi-provider setups.
- Export the zone file after every change and keep it somewhere you can reach without the DNS provider's dashboard.
- Know where the registrar's nameserver settings are and who can change them, so delegation can be updated quickly.
- If you sign the zone with DNSSEC and add a second operator, plan signing so both serve consistent records.
RFC 2182: selection of secondary DNS serversStatus Is UP dependency continuity toolkitService guide: Microsoft Azure