Readiness check · Recover lane · weight 2

Nameservers spread across providers

The domain's NS records point to at least two distinct DNS providers.

Observed on: 10%
Top 1K sites: 14%
Top 1M band: 11%
Not measured: 436

Why it matters

If every nameserver belongs to one provider, a problem at that provider can stop your domain resolving. RFC 2182 (BCP 16) recommends spreading secondary servers across diverse networks.

How to fix it

Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.

Dependency continuity toolkit

How we check

The domain's NS records point to at least two distinct DNS providers.

Observed: Two or more DNS providers.

Not observed: All nameservers belong to one provider.

Limit: Read from public DNS at the time of the check; records may have changed since.

Stack-specific steps

Cloudflare: Cloudflare supports zone transfers for primary or secondary DNS setups on eligible plans.

By popularity band

Chrome UX Report band	Observed	Measured
Top 1K	14%	459
Top 5K	11%	2,087
Top 10K	11%	2,507
Top 50K	9.6%	18,531
Top 100K	11%	5,236
Top 500K	11%	5,314
Top 1M	11%	5,525

Categories most likely to do this

Categories least likely

By stack

Adobe Experience Manager on Amazon CloudFront28%
Adobe Experience Manager23%
Nuxt on Amazon CloudFront22%
Sitecore22%
Drupal17%
Next.js on Akamai15%
Angular14%
Magento / Adobe Commerce13%
Nuxt13%
PrestaShop12%
Astro11%
Next.js on Google edge10%
Next.js on Fastly9.3%
Next.js7.5%
Drupal on Cloudflare7.2%
WordPress6.6%
Next.js on Amazon CloudFront6%
Blogger5.6%
Webflow5.3%
Shopify4.5%
Next.js on Vercel4.2%
Next.js on Cloudflare3.9%
WordPress on Amazon CloudFront3.4%
WordPress on Cloudflare<1%
Nuxt on Cloudflare<1%

By provider

Popular sites where we observed this

Sources and guides

Guide: Website Uptime Readiness: Prepare Before Traffic Arrives Check your own site