dns.pizza standing page

If Microsoft Azure DNS's DNS fails, what goes dark?

Data snapshot of November 1, 2026. Nameservers last checked September 5, 2026 to November 1, 2026. This page is a map of who depends on Microsoft Azure DNS. It is not a live reading and does not say whether Microsoft Azure DNS has a problem right now.

1,457 of the 99,283 top-ranked domains (1.5%) use Microsoft Azure DNS as their only DNS operator. If its nameservers stopped answering, these are the sites whose name could no longer be looked up once cached answers expired. Another 63 use Microsoft Azure DNS together with a another listed operator and may keep resolving, if that operator is independent and working.

DNS is the lookup that turns a name into an address. When none of a domain's nameservers answer, new lookups fail as cached answers run out, which takes from minutes to a day or more depending on each site's settings. People who already have the address, or reach it directly, may still get through.

1,457

depend on Microsoft Azure DNS alone, 1.5% of 99,283

35 of 996

of the top 1,000 sites depend on it alone

63

use it plus another listed operator, so they may stay up

Highest-ranked sites that depend on Microsoft Azure DNS alone

Top 100 of 1,457 by Tranco rank (1 is the most popular). The full list is in the CSV and JSON.

  1. microsoft.com#6
  2. live.com#21
  3. office.com#22
  4. azure.com#26
  5. microsoftonline.com#38
  6. office.net#43
  7. skype.com#45
  8. sharepoint.com#47
  9. windowsupdate.com#57
  10. cloud.microsoft#60
  11. windows.net#68
  12. windows.com#88
  13. office365.com#106
  14. msftncsi.com#133
  15. outlook.com#134
  16. azurefd.net#154
  17. msftconnecttest.com#156
  18. azurewebsites.net#170
  19. static.microsoft#192
  20. sfx.ms#195
  21. azureedge.net#226
  22. openai.com#252
  23. clarity.ms#317
  24. temu.com#383
  25. gamepass.com#459
  26. xboxlive.com#478
  27. exp-tas.com#480
  28. svc.ms#481
  29. visualstudio.com#540
  30. live.net#550
  31. azure-dns.com#563
  32. appcenter.ms#756
  33. frontiersin.org#858
  34. azure-devices.net#908
  35. elmundo.es#975
  36. kwcdn.com#1,012
  37. oecd.org#1,046
  38. marca.com#1,049
  39. onedrive.com#1,133
  40. nelreports.net#1,163
  41. 1drv.com#1,202
  42. cnnbrasil.com.br#1,227
  43. vscode-cdn.net#1,240
  44. azure-api.net#1,432
  45. usercontent.microsoft#1,939
  46. aadrm.com#1,974
  47. azure.net#1,984
  48. unicef.org#2,072
  49. hhs.gov#2,159
  50. lync.com#2,177
  51. dynamics.com#2,204
  52. virtualearth.net#2,216
  53. xboxservices.com#2,300
  54. msappproxy.net#2,335
  55. hotmail.com#2,347
  56. xbox.com#2,349
  57. microsoftpersonalcontent.com#2,371
  58. microsoft365.com#2,381
  59. msecnd.net#2,504
  60. azure-dns.net#2,508
  61. azurecontainerapps.io#2,523
  62. sharepointonline.com#2,533
  63. technologyreview.com#2,581
  64. powerbi.com#2,602
  65. cloudapp.net#2,635
  66. ilo.org#2,704
  67. minecraft.net#2,746
  68. panasonic.com#2,796
  69. microsoft.us#2,837
  70. swishapps.ai#2,853
  71. swiftkey.com#2,895
  72. iea.org#2,914
  73. s-microsoft.com#2,930
  74. 1drv.ms#2,936
  75. powerapps.com#2,996
  76. coca-cola.com#3,011
  77. brookings.edu#3,046
  78. cancer.org#3,069
  79. microsoftazuread-sso.com#3,089
  80. unep.org#3,202
  81. signalr.net#3,302
  82. microsoftonline.us#3,330
  83. hrw.org#3,335
  84. onenote.net#3,676
  85. hbs.edu#3,698
  86. powerplatform.com#3,847
  87. microsoftapp.net#3,878
  88. unfccc.int#3,880
  89. uefa.com#3,911
  90. edgedns-tm.info#3,986
  91. mojang.com#4,008
  92. redcross.org#4,062
  93. goethe.de#4,111
  94. dns-tm.com#4,208
  95. techlab-cdn.com#4,288
  96. adnxs-simple.com#4,303
  97. azure-dns.info#4,307
  98. msdn.com#4,403
  99. zebra.com#4,582
  100. iso.ch#4,679
How many depend on Microsoft Azure DNS alone, by rank
Rank bandAloneOf domains in band
1 to 1,000353.5% of 996
1,001 to 10,0001241.3% of 9,248
10,001 to 100,0001,2981.5% of 89,039

Sites that use Microsoft Azure DNS and also list another operator

All 63, with the other operator. These may keep resolving if Microsoft Azure DNS alone fails, provided the other operator is genuinely independent and working. We do not test that.

  1. linkedin.com#18also on NS1 (IBM)
  2. bing.com#31also on NS1 (IBM)
  3. msn.com#61also on NS1 (IBM)
  4. msidentity.com#572also on Akamai
  5. licdn.com#617also on NS1 (IBM)
  6. msftauth.net#912also on Akamai
  7. msauth.net#1,322also on Akamai
  8. lnkd.in#2,070also on NS1 (IBM)
  9. bing.net#2,092also on NS1 (IBM)
  10. yammer.com#2,514also on Akamai
  11. msftstatic.com#2,777also on NS1 (IBM)
  12. bingapis.com#4,060also on NS1 (IBM)
  13. aip.org#5,027also on Constellix
  14. lnkdns.net#5,525also on NS1 (IBM)
  15. b2clogin.com#5,710also on Akamai
  16. homeoffice.gov.uk#5,871also on Amazon Route 53
  17. vodafone.com#7,306also on its own nameservers
  18. assets-yammer.com#8,518also on Akamai
  19. phonefactor.net#10,710also on Akamai
  20. scitation.org#14,425also on Constellix
  21. msidentity.us#14,778also on Akamai
  22. linkedin-ei.com#17,606also on NS1 (IBM)
  23. lynda.com#18,032also on NS1 (IBM)
  24. unipune.ac.in#19,916also on sppu.in
  25. flinders.edu.au#20,358also on edu.au
  26. passport.net#21,558also on Akamai
  27. totalwine.com#21,795also on Google
  28. proctorauth.com#22,854also on Constellix
  29. adform.com#25,742also on Amazon Route 53
  30. mgm.mo#26,485also on f5clouddns.com
  31. nelogica.com.br#26,574also on Amazon Route 53
  32. brp.com#26,754also on CSC
  33. yammerusercontent.com#28,038also on Akamai
  34. msidentity.net#30,420also on Akamai
  35. adeo.cloud#30,779also on perf1.com, perf1.fr
  36. coop.co.uk#34,184also on CSC
  37. rememberthemilk.com#35,441also on Amazon Route 53, Google
  38. linkedin.cn#45,000also on NS1 (IBM)
  39. citilink.co.id#45,074also on microsoftonline.com
  40. realytics.net#46,395also on Amazon Route 53
  41. universidadeuropea.com#49,710also on rediris.es
  42. parentpay.com#54,038also on dns-pp.com
  43. wtamu.edu#55,484also on its own nameservers
  44. glencore.com.au#58,735also on NS1 (IBM)
  45. reginamaria.ro#58,761also on gts.ro
  46. status.microsoft#58,937also on Akamai
  47. phonak.com#61,507also on Amazon Route 53
  48. udlap.mx#63,705also on its own nameservers
  49. msidentity.cn#68,284also on Akamai
  50. lovelyskin.com#68,291also on Constellix
  51. bizographics.com#69,487also on NS1 (IBM)
  52. auchan.pl#72,754also on internetia.pl
  53. macu.com#72,923also on Amazon Route 53
  54. cypad.net#76,316also on dns-pp.com
  55. sns.it#82,409also on garr.net, its own nameservers
  56. cashcrusaders.co.za#82,525also on voxdns.co.za
  57. cbn.gov.ng#84,024also on gov.ng
  58. drawnames.ph#94,802also on Constellix
  59. linkedin.biz#96,270also on NS1 (IBM)
  60. cgu.edu#97,575also on its own nameservers, claremont.edu
  61. glencore.net#97,883also on NS1 (IBM)
  62. csn.edu#98,051also on its own nameservers
  63. glencore.com#98,954also on NS1 (IBM)

What these figures do not capture

  • Hosting is a separate dependency. We record which nameservers a domain delegates to. We do not record CNAME targets, so we cannot tell a site that depends on a hosting platform (a store or site builder reached through a CNAME) from one that runs its own servers. A site on this list can fail for reasons that have nothing to do with Microsoft Azure DNS, and a site not on it can fail because its host or CDN did.
  • Only the top 100,000 sites, one vote each. Tranco ranks popularity, not traffic. Smaller sites are not in this count, and a busy domain counts the same as a quiet one.
  • "Second operator" is not proof of independence. We treat each unrecognised nameserver zone as its own operator, so two zones owned by one company look like two. The count of sites that depend on Microsoft Azure DNS alone is therefore a floor, and the count with a second operator is a ceiling.
  • Vanity nameservers. A site that runs Microsoft Azure DNS under nameserver names on its own domain (ns1.example.com) is counted as self-hosted, not as a Microsoft Azure DNS customer.
  • Not every failure is total. An operator can fail in one region, one product, or for changes only (existing records keep answering). This page describes the worst case, every nameserver at one operator unreachable.
  • Snapshot timing. Domains move between operators. Records were last checked September 5, 2026 to November 1, 2026; a domain that changed operator after its check shows its old one.

Check right now

dns.pizza does not monitor Microsoft Azure DNS on this page and cannot say whether an outage is happening. To find out:

  • Read Microsoft Azure DNS's own status page: azure.status.microsoft.
  • Look up any one domain's nameservers and whether they answer at this moment with the DNS lookup tool. It reports that one domain only, from our servers.

Use this data

Free to cite and reuse under CC BY 4.0; credit "dns.pizza" and the snapshot date (November 1, 2026). Method and the wider findings are in the research report One Outage From Darkness. Operator names are resolved from nameserver hostnames by the same rules as that report.