webatla Blog

Websites Created Using Wix: 4.9M Live (2026)

2026-07-11T15:00:00.000Z

About webatla. webatla is a domain-intelligence platform. We crawl and fingerprint domains across the web and record which technology each site runs — the same class of tool as BuiltWith or Wappalyzer, with wider coverage. Every number on this page comes from the webatla index, last refreshed on 7 July 2026.

There are 4,930,392 websites created using Wix live in the webatla index right now — 1.6% of every domain we track, and the second-largest DIY website builder on the web behind only Squarespace. For anyone building the small-business web, that makes Wix one of only two builders — with Squarespace — operating at real scale.

What Wix actually is

Wix is a hosted (SaaS) website builder founded in 2006 and headquartered in Tel Aviv, Israel. A user does not install Wix or manage a server — they build a site in a drag-and-drop editor, and Wix runs it on Wix's own infrastructure behind a custom domain or a Wix-hosted address. That hosting model matters for the data below: it changes what "where a site lives" means, and it is why sites powered by Wix look different in the index from self-hosted platforms like WordPress.

How many websites are created using Wix?

The headline figure: 4,930,392 live sites run Wix in the webatla index — 1.6% of all indexed domains. The DIY-builder category is a tight race, and Wix sits firmly in second.

Bar chart of websites created using Wix versus other website builders in the webatla index, Squarespace 7.6M leading Wix 4.9M, GoDaddy Builder, Weebly and Webflow

Live sites by DIY website builder. Source: webatla index, July 2026.

Squarespace — 7,597,107 sites
Wix — 4,930,392 sites
GoDaddy Website Builder — 4,653,566 sites
Weebly — 504,102 sites
Webflow — 502,062 sites

Two facts stand out. First, the builder market has a clear top three — Squarespace, Wix and GoDaddy Website Builder — and then a steep drop to Weebly and Webflow, which sit at roughly a tenth of Wix's size. Second, GoDaddy's builder is far bigger than most people assume: at 4,653,566 sites it trails Wix by under 280,000, close enough that the #2 and #3 spots are effectively a dead heat. Wix's real competition is not the developer-favorite Webflow — it is the two mass-market builders directly above and below it.

What the domain endings say

Domain endings are a useful fingerprint. Most sites made using Wix sit on .com, but the tail says something about who builds on it.

Column chart of the top-level domains of websites created using Wix: .com 67.2%, .org 4.7%, .uk 4.1%, .net 3.4%, .br 2.5%

Top TLDs among Wix sites. Source: webatla index, July 2026.

.com dominates at 67.2% (3,313,258 domains), even higher than the web-wide norm — a sign of small businesses and personal brands reaching for the default commercial ending. The tail is telling: .org at 4.7% (232,734 sites) points to nonprofits, clubs and community groups that picked a builder over a developer, and .uk at 4.1% plus .net (3.4%) and .br (2.5%) show meaningful adoption in the UK and Brazil. Wix is not a US-only tool for shops; the TLD spread is the fingerprint of a general-purpose builder used by small organizations worldwide.

What kinds of sites are built on Wix

The TLD data points to a consistent profile: Wix is the tool of the small organization that wants a site without a developer. Each of these archetypes is a fingerprint webatla counts directly rather than a guess.

Small businesses and personal brands. The 67.2% .com share — higher than the web-wide average — is the signature of sole traders, local services and personal sites reaching for the default commercial ending.
Nonprofits and community groups. The 4.7% .org share (232,734 sites) is unusually high for a builder; it maps to clubs, charities and community projects that chose drag-and-drop over code.
The international small web. The .uk (4.1%), .net (3.4%) and .br (2.5%) tail shows Wix is not a US-only product — real clusters sit in the UK and Brazil, even though the hosting geolocation below hides them.

Together, these are the long tail of the small web — businesses, creators and organizations that traded control for a site they could build themselves.

Where webatla geolocates Wix sites — read this carefully

In the index, 99.2% of Wix sites geolocate to the United States, with every other country at 0.1% or below.

Bar chart of where webatla geolocates Wix sites: United States 99.2%, then Germany, Netherlands, British Virgin Islands and Australia at 0.1% each

Geolocation of Wix sites. Source: webatla index, July 2026.

This does not mean 99% of Wix users are American. It is a hosted-platform artifact. Wix serves every site from its own infrastructure, and that infrastructure resolves to the United States — so webatla geolocates almost the entire population there, regardless of where the site owner actually is. Note that Wix itself is headquartered in Tel Aviv, Israel, not the US; the country signal tracks the servers, not the company and not the users. This is the same pattern hosted platforms always produce, and the mirror image of self-hosted WordPress, whose sites scatter across thousands of independent hosts worldwide. When you want to read who actually builds on Wix, trust the TLD split — where owners register their names — over the geolocation.

Who uses Wix — the builder in context

Zoom out to every platform and Wix takes its place in the wider map of how the web is built. It is not the biggest way to make a website — that is still self-hosted WordPress, roughly five times larger at 23,589,840 sites — but among hosted, no-code builders it is a clear second, and it out-counts the hosted commerce leader Shopify (2,850,244). The picture is a market split between one giant self-hosted CMS and a cluster of hosted builders and store platforms fighting for the no-code majority, with Wix at the front of that cluster alongside Squarespace.

See the full list of websites created using Wix, filterable by TLD, on the Wix technology page. →

Trends: the year-over-year number is an index recount

The webatla index records a -71.52% year-over-year change in detected live Wix sites. As with any single snapshot delta, the honest reading requires looking sideways at the rest of the category.

Every website builder in the index fell in the same window: Weebly -88.95%, Webflow -73.88%, Squarespace -58.13% and GoDaddy Website Builder -20.43%. When an entire category drops together like that, the cause is a recalibration in how the index counts live installations between crawls — a recount — not millions of sites vanishing overnight. What is worth noting is the relative result: GoDaddy's builder held up best at -20.43%, while Wix and its peers saw larger detected drops. Read the recount as a caution about absolute year-over-year deltas, and anchor on the standing instead.

The durable signal is that standing: Wix is the #2 website builder on the web, ahead of GoDaddy's builder and every developer-focused tool, and behind only Squarespace.

How to see the list of websites using Wix

You do not have to estimate any of this. The Wix technology page on webatla is a live, filterable view of every site we detect. On it you can:

Browse the running count of live websites created using Wix (4,930,392 and updated as we re-crawl).
Filter by top-level domain to separate .com from .org, .uk and other country endings.
Compare Wix side by side with Squarespace, GoDaddy Website Builder and Webflow to see the whole builder field.

That is the fastest way to turn "Wix is popular" into an actual, workable list of websites that use Wix.

Get the full list of websites created using Wix

webatla maintains a live, filterable list of every Wix site in the index — all 4,930,392 of them, sortable by TLD. It is the same data behind every chart above, kept current as we re-crawl the web.

→ Open the Wix technology page to browse and filter the full list of sites built with Wix.

FAQ

How many websites are created using Wix? webatla indexes 4,930,392 live websites created using Wix as of July 2026 — 1.6% of every domain in the index, and the second-largest website builder behind Squarespace.

Is Wix or Squarespace bigger? Squarespace is bigger by site count, at 7,597,107 versus Wix's 4,930,392. Wix is second, narrowly ahead of GoDaddy Website Builder (4,653,566).

Why do 99.2% of Wix sites show as US-based? Because Wix is a hosted platform that serves every site from its own US-resolving infrastructure. The country breakdown reflects where the sites are served from, not where the owners live. Wix itself is headquartered in Tel Aviv, Israel.

What domain endings do Wix sites use? .com leads at 67.2%, followed by .org (4.7%), .uk (4.1%), .net (3.4%) and .br (2.5%).

Where can I see a list of websites using Wix? Open the Wix technology page on webatla, where the full list of live Wix sites is filterable by TLD.

Websites Made With Shopify: 2.85M Live Stores (2026)

2026-07-10T15:00:00.000Z

There are 2,850,244 websites made with Shopify live in the webatla index right now — 0.9% of every domain we track, and the second-largest dedicated commerce platform on the web behind only WooCommerce. This article breaks down where those stores sit, what their domains reveal, why the country data is not what it first looks like, and how to pull the full list of sites yourself.

What Shopify actually is

Shopify is a hosted (SaaS) e-commerce platform founded in 2006 and headquartered in Ottawa, Canada. Unlike a self-hosted stack, a merchant does not install Shopify on their own server — the store runs on Shopify's infrastructure, behind a custom domain or a myshopify.com address. That hosting model matters for the data below: it changes what "where a site lives" even means, and it is the reason sites powered by Shopify look different in the index from sites built on WordPress.

How many websites are made with Shopify?

The headline figure: 2,850,244 live stores run Shopify in the webatla index — 0.9% of all indexed domains. On its own that 0.9% sounds small, but the commerce category is narrow and concentrated. Here is how the count of websites made with Shopify compares with the other dedicated e-commerce platforms merchants choose.

Bar chart of websites made with Shopify versus other commerce platforms in the webatla index, WooCommerce 3.4M and Shopify 2.85M leading Magento, PrestaShop and BigCommerce

Live sites by dedicated e-commerce platform. Source: webatla index, July 2026.

WooCommerce — 3,377,108 sites
Shopify — 2,850,244 sites
Magento — 75,035 sites
PrestaShop — 70,633 sites
BigCommerce — 26,333 sites

Two facts jump out. First, the commerce web is a duopoly: WooCommerce and Shopify together account for the overwhelming majority of detected stores, and everything else is a rounding error by comparison — Magento, PrestaShop and BigCommerce sit in the tens of thousands, not the millions. Second, Shopify is the largest hosted commerce platform, but it is not the largest commerce platform overall. WooCommerce — an open-source plugin that runs on WordPress — edges it by roughly 527,000 sites. Compare only SaaS platforms and Shopify wins outright; the one thing bigger is the self-hosted alternative on WordPress.

What the domain endings say

Domain endings are a useful fingerprint, and Shopify's are distinctive. Most sites that use Shopify sit on .com, but the next tier is unlike any general-purpose platform: purpose-built commerce TLDs.

Column chart of the top-level domains of websites made with Shopify: .com 64.8%, .store 5.0%, .shop 4.0%, .uk 2.7%, .au 2.1%

Top TLDs among Shopify sites. Source: webatla index, July 2026.

.com leads at 64.8% (1,846,439 domains), which is unremarkable. What stands out is second and third place: .store at 5.0% and .shop at 4.0%. Those are retail-only domain endings, and their prominence is a signal you rarely see outside commerce — a fresh crop of stores that registered a name that literally says "shop." After that come .uk (2.7%) and .au (2.1%), pointing to strong adoption in the UK and Australia. The .store/.shop cluster is the clearest domain-level tell that a population of sites is commercial rather than editorial.

Where webatla geolocates Shopify sites — read this carefully

Now the number that looks dramatic and needs context. In the index, 93.8% of Shopify sites geolocate to Canada, with the United States a distant second at 4.8%.

Bar chart of where webatla geolocates Shopify sites: Canada 93.8%, United States 4.8%, Germany 0.3%, Vietnam 0.2%, Cyprus 0.2%

Geolocation of Shopify sites. Source: webatla index, July 2026.

This does not mean 94% of Shopify merchants are Canadian. It is a hosted-platform artifact. Because a store made on Shopify runs on Shopify's own infrastructure — and Shopify is a Canadian company — the domains resolve to that infrastructure, and webatla geolocates them accordingly. Canada here is Shopify's home, not the merchant's. This is the mirror image of self-hosted WordPress, whose sites scatter across thousands of independent hosts in dozens of countries because each owner picks their own server. The lesson is a data-literacy one: for any SaaS platform, the country breakdown tracks where the platform is served from, not where its customers are. Trust the TLD split — where merchants actually register their names — over the geolocation when you want to read demand.

Who builds on Shopify

The webatla index also detects the broader commerce landscape around Shopify — the platforms and features that show up when you fingerprint a shopping cart. Set against the wider field, Shopify sits mid-pack by raw count, because "commerce-capable" site builders inflate the top of the list.

Shopify's own detected examples are a fair cross-section of what the platform hosts: household retail names alongside niche shops. Among the live sites the index surfaces are myfonts.com, fleetfeet.com and fashionnova.com — a font marketplace, a running-shoe chain and a fashion brand — plus Shopify's own shopify.com. That spread, from single-product shops to nine-figure brands, is why the platform's store count is both large and commercially dense: nearly every one of these 2.85M domains exists to sell something.

See the full list of websites made with Shopify, filterable by country and TLD, on the Shopify technology page. →

Shopify in the wider commerce picture

Dedicated platforms are only part of the story. webatla also fingerprints commerce capability — the shopping-cart features bundled into general-purpose site builders — and by that broader measure the field reshuffles. Commerce on Squarespace shows up on roughly 7.6M sites and Wix eCommerce on about 1.4M, while WooCommerce sits near 3.5M in the same cut. The distinction matters: a site builder with a store feature switched on is not the same thing as a purpose-built shop. Shopify's 2,850,244 domains are overwhelmingly the latter — sites that exist to sell — which is why its store count carries more commercial weight per domain than a builder's optional commerce toggle. When someone asks which platform the real stores are on, the honest answer is Shopify and WooCommerce; the builders trail once you separate active shops from merely shop-capable pages.

Trends: the year-over-year number is an index recount

The webatla index records a -32.61% year-over-year change in detected live Shopify stores. As with any single snapshot delta, the honest reading requires looking sideways at the rest of the category.

Every commerce platform in the index fell in the same window: WooCommerce -61.70%, Magento -70.02%, PrestaShop -90.31% and BigCommerce -92.02%. When an entire category moves down together like that, the cause is a recalibration in how the index counts live installations between crawls — a recount — not millions of stores closing overnight. What is genuinely notable is the relative result: at -32.61%, Shopify shed the smallest share of any major commerce platform in this recount. Whatever the absolute counting method, Shopify held its detected footprint better than its rivals, which is consistent with a hosted platform that keeps stores live and reachable rather than leaving stale self-hosted installs to age out.

The durable signal is the standing: Shopify is the #2 commerce platform overall, the #1 hosted one, and more than 100× larger than the next dedicated hosted platform, BigCommerce.

How to see the list of websites using Shopify

You do not have to estimate any of this. The Shopify technology page on webatla is a live, filterable view of every store we detect. On it you can:

Browse the running count of live websites made with Shopify (2,850,244 and updated as we re-crawl).
Filter by top-level domain to isolate .store, .shop, .com or country TLDs.
Compare Shopify side by side with WooCommerce, Magento and BigCommerce to see the full commerce field.

That is the fastest way to turn "Shopify is big" into an actual, workable list of websites that use Shopify.

Get the full list of websites made with Shopify

webatla maintains a live, filterable list of every Shopify store in the index — all 2,850,244 of them, sortable by TLD and country. It is the same data behind every chart above, kept current as we re-crawl the web.

→ Open the Shopify technology page to browse and filter the full list of sites powered by Shopify.

FAQ

How many websites are made with Shopify? webatla indexes 2,850,244 live websites made with Shopify as of July 2026 — 0.9% of every domain in the index, and the second-largest dedicated commerce platform behind WooCommerce.

Is Shopify or WooCommerce bigger? By raw site count, WooCommerce is slightly bigger (3,377,108 vs 2,850,244). Shopify is the largest hosted commerce platform; WooCommerce is a self-hosted WordPress plugin.

Why do 93.8% of Shopify sites show as Canadian? Because Shopify is a hosted platform based in Canada, its stores resolve to Shopify's own infrastructure. The country breakdown reflects where the platform is served from, not where merchants are based.

What domain endings do Shopify stores use? .com leads at 64.8%, followed by the commerce-specific .store (5.0%) and .shop (4.0%), then .uk (2.7%) and .au (2.1%).

Where can I see a list of websites using Shopify? Open the Shopify technology page on webatla, where the full list of live Shopify stores is filterable by country and TLD.

Websites That Use Cloudflare: 54.4M Live (2026)

2026-07-09T15:00:00.000Z

There are 54,437,496 websites that use Cloudflare live in the webatla index right now — 17.7% of every domain we track, which makes it the single most common technology in the entire index, ahead of any CMS, server or analytics tool. Nearly one in six sites on the web sits behind Cloudflare.

What Cloudflare actually is

Cloudflare is a reverse proxy: it sits in front of a website, between visitors and the origin server. From that position it delivers three things at once — a content delivery network (CDN) that caches and speeds up pages, a security layer (WAF, DDoS mitigation, bot filtering) that is why so many say their sites are "protected by Cloudflare," and managed DNS. Because a site points its domain at Cloudflare, the fingerprint is unambiguous and served on every request, which matters for the data below. Founded in 2009, Cloudflare now fronts a larger share of the web than any other single technology webatla tracks.

Websites that use Cloudflare vs the rest of the CDN market

The headline figure — 54,437,496 live sites, 17.7% of all indexed domains — only lands once you see the competition. Cloudflare is not the leading CDN. It is the only CDN operating at web scale.

Bar chart of websites that use Cloudflare vs other reverse-proxy CDNs in the webatla index, Cloudflare 54.4M dwarfing Amazon CloudFront, Fastly and Akamai

Live sites by reverse-proxy CDN. Source: webatla index, July 2026.

Cloudflare — 54,437,496 sites (17.7%)
Amazon CloudFront — 1,482,887 sites (0.5%)
Fastly — 1,030,468 sites (0.3%)
Akamai — 25,532 sites (0.0%)

The gap is not a lead; it is a different scale entirely. Cloudflare runs on 37× as many sites as Amazon CloudFront, the next reverse-proxy CDN, and more than 50× Fastly. Akamai — the CDN that effectively invented the category — now shows just 25,532 live sites in the index. Add every dedicated reverse-proxy competitor together and the total is under 2.6M, less than 5% of Cloudflare's footprint. For anyone reasoning about the web's delivery and security layer, there is one name that matters and a long tail of everyone else.

To feel the absolute scale, set Cloudflare against the platforms people call giants: its 54,437,496 sites are more than double the entire WordPress install base (23,589,840). The web's most common way to sit in front of a site out-counts its most common way to build one, two to one. That is why Cloudflare shows up in front of sites built on every CMS, server and store platform in the index — it is not a competitor to those tools but the layer wrapped around all of them.

What the domain endings say

Domain endings are a useful fingerprint, and Cloudflare's confirm that it spans the whole web rather than any one niche.

Column chart of the top-level domains of websites that use Cloudflare: .com 46.8%, .org 3.4%, .net 2.8%, .shop 2.3%, .info 2.1%

Top TLDs among Cloudflare sites. Source: webatla index, July 2026.

.com leads at 46.8% (25,477,102 domains), close to the web-wide average — Cloudflare is not skewed toward one type of site. What stands out lower down is the breadth: .org (3.4%) for nonprofits, .net (2.8%) for infrastructure and legacy sites, and then two commerce-and-content signals, .shop (2.3%) and .info (2.1%). The presence of .shop in the top five is notable — it means a large slice of the web's newer online stores route through Cloudflare for speed and protection. The spread is the point: sites protected by Cloudflare are drawn from every corner of the web, not a single vertical.

Who puts Cloudflare in front of their site

Cloudflare's reach is broad because it solves three problems every site has. As a CDN it caches content close to visitors, so pages load faster. As a security layer it absorbs DDoS attacks and filters bots — the reason so many operators describe their sites as protected by Cloudflare. And as managed DNS it is often the fastest, simplest place to point a domain. Those three jobs apply to a personal blog and a bank alike, which is why the TLD spread above runs from .shop stores to .org nonprofits to .com businesses. There is no single Cloudflare customer profile; at 17.7% of the web, the profile is the web itself. That ubiquity is what makes the list useful — filter it and you are effectively filtering a representative cross-section of every live site online, by country, TLD or the other technologies each site runs.

Where webatla geolocates Cloudflare sites — read this carefully

The country breakdown needs context, because Cloudflare is a proxy. In the index, 74.4% of Cloudflare sites geolocate to the United States, followed by Canada at 9.5%.

Bar chart of where webatla geolocates Cloudflare sites: United States 74.4%, Canada 9.5%, Germany 3.4%, Hong Kong 1.3%, Australia 1.1%

Geolocation of Cloudflare sites. Source: webatla index, July 2026.

Because Cloudflare answers for a domain from its own anycast edge, the country webatla records is the location of the Cloudflare IP serving the request, not the origin server and not the site owner. Cloudflare's address space is predominantly US-registered, so the map skews heavily to the United States regardless of where a site is actually run or read. This is the same effect hosted platforms produce — sites resolving to the vendor's infrastructure rather than the customer — and the mirror image of self-hosted WordPress, whose sites scatter across independent hosts worldwide. Read Cloudflare's geography as network geography, not audience geography.

Cloudflare and the wider delivery layer

The reverse-proxy count is only part of Cloudflare's footprint. The web also leans on asset and script CDNs, and Cloudflare sits in that layer too. Google Cloud CDN appears on 9,141,337 sites, cdnjs — a free script CDN maintained by Cloudflare — on 6,077,234, and jsDelivr on 5,086,086. Even setting the proxy business aside, one of the largest script CDNs on the web is a Cloudflare project. Counted together, the delivery and asset layer is one of the densest technology categories webatla tracks, and Cloudflare is either the leader or a major presence in every part of it.

Trends: the number that barely moved

Cloudflare's year-over-year change is -9.67% — a small move against an index full of steep drops. That matters because most technologies in this snapshot show large negative swings that reflect an index recount (a change in how live installations are counted between crawls): its own CDN rivals fell far harder, with Fastly down 42.00%, Amazon CloudFront down 47.01%, Google Cloud CDN down 68.83% and Akamai down 89.13%.

Cloudflare barely moved. The reason is its fingerprint: a site behind Cloudflare announces it on every response, unambiguously, so re-crawls detect it consistently while fuzzier signals get recounted. In practice that makes 54,437,496 the most reliable large number in the index — the one technology whose count you can quote with the least caveat. That stability, not just the size, is what marks Cloudflare as the web's default infrastructure.

How to see the list of websites using Cloudflare

You do not have to estimate any of this. The Cloudflare technology page on webatla is a live, filterable view of every site we detect behind Cloudflare. On it you can:

Browse the running count of live websites that use Cloudflare (54,437,496 and updated as we re-crawl).
Filter by top-level domain to isolate .com, .shop, .org or country endings.
Compare Cloudflare against Amazon CloudFront, Fastly and Akamai to see the full delivery-layer field.

That is the fastest way to turn "everything runs on Cloudflare" into an actual, workable list of sites that use Cloudflare.

Get the full list of websites that use Cloudflare

webatla maintains a live, filterable list of every Cloudflare site in the index — all 54,437,496 of them, sortable by TLD and country. It is the same data behind every chart above, kept current as we re-crawl the web.

→ Open the Cloudflare technology page to browse and filter the full list of sites protected by Cloudflare.

FAQ

How many websites use Cloudflare? webatla indexes 54,437,496 live websites that use Cloudflare as of July 2026 — 17.7% of every domain in the index, and the single most common technology tracked.

Is Cloudflare the biggest CDN? By a wide margin. At 54,437,496 sites it runs on 37× as many domains as Amazon CloudFront and more than 50× Fastly; Akamai shows just 25,532 live sites.

Why do most Cloudflare sites show as US-based? Because Cloudflare is a reverse proxy answering from its own US-registered anycast IPs. The country reflects the Cloudflare edge serving each domain, not the origin server or the site owner.

Does "protected by Cloudflare" mean hosted by Cloudflare? No. Cloudflare sits in front of a site as a CDN and security layer; the origin is usually hosted elsewhere. The site's domain points at Cloudflare, which is why webatla detects it on every request.

Where can I see a list of websites that use Cloudflare? Open the Cloudflare technology page on webatla, where the full list of live Cloudflare sites is filterable by country and TLD.

Websites created using WordPress: 23.6M Live (July 2026)

2026-07-08T13:19:00.000Z

There are 23,589,840 websites created using WordPress live in the webatla index right now — 7.7% of every domain we track, and more than the next five website platforms in our index combined. This article breaks down who runs WordPress, where those sites live, which plugins hold the ecosystem together, and how to pull the full list of sites yourself.

What WordPress actually is

WordPress is an open-source content management system (CMS) first released in 2003. It renders pages from a PHP core, a theme, and a stack of plugins, and it powers everything from single-author blogs to enterprise publishers and online stores. Because it is free, self-hostable, and endlessly extensible, it became the default way to build a website — which is exactly why the count of sites built with WordPress dwarfs every alternative. The WordPress fingerprint is measurable, and that is what webatla counts.

How many websites are created using WordPress?

The headline figure: 23,589,840 live sites run WordPress in the webatla index — 7.7% of all indexed domains. To put that share in context, here is how the count of websites created using WordPress compares with the other platforms people choose instead.

Bar chart of websites created using WordPress versus other platforms in the webatla index, WordPress 23.6M leading Squarespace, Wix, Shopify, Joomla and Drupal

Live sites by platform. Source: webatla index, July 2026.

WordPress — 23,589,840 sites (7.7%)
Squarespace — 7,240,492 sites (2.4%)
Wix — 4,617,356 sites (1.5%)
Shopify — 2,746,823 sites (0.9%)
Joomla — 554,966 sites (0.2%)
Drupal — 240,289 sites (0.1%)

WordPress runs on 3.3× as many sites as Squarespace, the next-biggest platform, and on more domains than Squarespace, Wix, Shopify, Joomla and Drupal put together. When people say most of the web is built on WordPress, this is the shape of the claim: one platform, a 7.7% slice of everything we index, and a long tail of everyone else.

Who builds sites with WordPress — the plugin and theme layer

A raw WordPress install is rarely the whole story. Most websites made using WordPress are assembled from a page builder, an SEO plugin, a caching layer, and a theme. Counting those add-ons tells you what kind of sites are being built, and the webatla index tracks each one separately.

Bar chart of the top WordPress plugins and themes by live installs in the webatla index: Elementor, Yoast SEO, LiteSpeed Cache, WooCommerce and Astra

Top WordPress plugins and themes by live installs. Source: webatla index, July 2026.

Elementor — 7,887,817 sites (2.6%). A drag-and-drop page builder; roughly one in three WordPress sites we detect ships with it.
Yoast SEO — 7,333,886 sites (2.4%). The dominant SEO plugin, a signal these are sites built to be found in search.
LiteSpeed Cache — 3,927,733 sites (1.3%). Server-level caching, a marker of performance-conscious hosting.
WooCommerce — 3,377,108 sites (1.1%). The commerce layer that turns WordPress into a store; every one of these is a shop.
Astra — 2,077,184 sites (0.7%). A lightweight theme built to pair with page builders.

The mix is telling. The two most common add-ons are a page builder and an SEO plugin, which describes the median WordPress project: a marketing or content site that someone wants ranking. The 3.4 million WooCommerce installs show the second-largest use case — WordPress as an e-commerce engine, competing directly with the standalone Shopify sites counted above.

What kinds of sites are built with WordPress

The plugin mix maps to three recurring archetypes among sites that use WordPress, and each one is a fingerprint webatla counts directly rather than a guess:

Content and marketing sites. The single largest group. The 7.3 million Yoast SEO installs and 7.9 million Elementor builds point to blogs, media outlets, agencies and lead-generation pages — sites designed to rank and convert. For most of the web, "build a website" still means a WordPress content site.
Online stores. The 3.4 million WooCommerce installs are all shops. That makes WordPress one of the largest e-commerce footprints on the web on its own, before you even count hosted platforms like Shopify.
Performance-tuned and managed sites. The 3.9 million LiteSpeed Cache installs cluster on hosts that ship server-level caching — a marker of sites where speed and scale matter enough to tune for.

Add those together and you get the practical answer to what all these websites made by WordPress actually are: mostly content and commerce, built by people who wanted to own their own stack instead of renting it.

Where websites made by WordPress live

WordPress adoption is not evenly spread. The United States alone accounts for four in ten WordPress sites in the index, and the top five countries cover roughly two-thirds of the total.

Column chart of the top five countries by websites created using WordPress: United States 9.5M, Germany 3.3M, France 1.2M, Japan 1.1M, Netherlands 0.73M

Top countries by WordPress sites. Source: webatla index, July 2026.

Country	WordPress sites	Share
United States	9,495,696	40.8%
Germany	3,339,666	14.3%
France	1,194,882	5.1%
Japan	1,053,931	4.5%
Netherlands	729,970	3.1%

The domain endings line up with that geography. Nearly half of all sites powered by WordPress — 11,116,459 domains, 47.1% — sit on .com, followed by .de (5.5%), .org (4.1%), .uk (2.9%) and .br (2.7%). A .com-heavy, US-and-Europe-weighted footprint is the profile of the global commercial web, which is precisely where WordPress lives.

See the full list of websites created using WordPress, filtered by country, TLD or version, on the WordPress technology page. →

Versions: half the web runs one release

Across every live install, the version fingerprint is remarkably concentrated. Per webatla's detection, 49.2% of WordPress sites report version 6.9.4 — a single release accounting for nearly half of all detected installs. Another 18.2% sit on the 7.0 branch, and the remaining share trails off across 6.8.5 (6.8%), 6.7.5 (2.5%) and 6.6.5 (1.3%). That concentration matters for anyone doing security or compatibility research: patch one dominant version and you have effectively described half the WordPress web.

Trends: read the year-over-year number carefully

The webatla index records a -66.17% year-over-year change in detected live WordPress installs between snapshots. Taken at face value that looks dramatic — but it is not 23 million sites disappearing. The same recount shows large negative swings across many technologies at once: WooCommerce -61.70%, Yoast SEO -75.52%, Astra -45.01%, LiteSpeed Cache -37.77% and Drupal -87.84%. When an entire class of technologies moves together like that, the cause is a change in how the index counts live installations between crawls — a recalibration of coverage and fingerprinting — not a real-world collapse of any one platform.

The durable signal is the share, not the swing: WordPress still holds 7.7% of the indexed web and a 3.3× lead over the next platform.

How to see the list of websites using WordPress

You do not have to estimate any of this. The WordPress technology page on webatla is a live, filterable view of every WordPress site we detect. On it you can:

Browse the running count of live sites built on WordPress (23,589,840 and updated as we re-crawl).
Filter by country, top-level domain, and detected version.
Cross-reference the ecosystem — see which of those sites also run WooCommerce, Elementor or Yoast SEO.

That is the fastest way to turn "most of the web uses WordPress" into an actual, workable list of websites that use WordPress.

Get the full list of websites created using WordPress

webatla maintains a live, filterable list of every WordPress site in the index — all 23,589,840 of them, sortable by country, TLD and version. It is the same data behind every chart above, kept current as we re-crawl the web.

→ Open the WordPress technology page to browse and filter the full list of sites powered by WordPress.

How to Download all DNS Records

2026-07-01T17:25:00.000Z

Every DNS record for every domain on the internet, in one file. That is what getting the full picture really comes down to, and there is one clean way to do it. You do not want a script that hammers resolvers for a week and still times out on half the internet. You want the A, MX, TXT, and NS entries for hundreds of millions of names, already collected, parsed, and ready to query. This is what you buy.

What is a DNS record?

A DNS record is one line in the internet's address book. It tells the world where a name lives and the way to reach it. Which server answers on the web, where its email goes, which nameservers are authoritative, and more. Every active name carries a handful of them, and together they are the operational fingerprint of that domain.

There are a few record types you meet again and again:

Record	What it does	Example value
`A`	points a domain at an IPv4 address	`93.184.216.34`
`AAAA`	points a domain at an IPv6 address	`2606:2800:220:1::`
`CNAME`	aliases one name onto another, never at a zone apex	`cdn.example.com`
`MX`	routes the domain's email	`mail.example.com` (priority 10)
`TXT`	free-form text, holds SPF and verification tokens	`v=spf1 include:_spf.google.com ~all`
`NS`	the domain's authoritative nameservers	`ns1.cloudflare.com`
`SOA`	start-of-authority metadata for the zone	primary NS, serial, refresh, retry, expire
`CAA`	which authorities may issue its certificates	`letsencrypt.org`

Pull all of these for one name and you know the way it is hosted, who runs its mail, and the security its owner set. Pull them for every name at once and you hold a map of the entire internet's infrastructure. That second dataset is the one worth having, and the one nobody hands out for free.

The records that do the heavy lifting

A handful of these types carry most of the signal. The A record is the one most people picture, mapping a name to an IPv4 address so a browser knows which server to reach. The MX record does the same job for email, naming the servers that accept a message and ranking them by priority. The TXT record is the quiet workhorse of email security. On the domain itself, the SPF record lists who may send mail as you. The matching DKIM signing keys and DMARC policy live on dedicated subnames (_domainkey and _dmarc), and together the three tell you how well an address is protected, since it is the DMARC policy, not the mere presence of records, that enforces anything. The NS record names the authoritative servers that answer for the zone, which tells you who really runs a name's resolution.

Why you cannot pull every DNS record yourself

In theory you could resolve every name with dig in a loop. In practice that plan dies fast. There are hundreds of millions of domains, and each one needs several queries to capture every type, so you are staring at billions of lookups. Public resolvers rate-limit and then block you long before you finish. Authoritative servers throttle. Timeouts, retries, and transient failures mean a single pass is never complete, and it keeps changing while the crawl runs, so the answer is stale before it lands.

Then there is parsing. Raw responses are wire-format packets, not a tidy export. Turning billions of them into clean, typed entries you can actually query is its own engineering project on top of the crawl. Most teams start this, watch it eat a quarter, and quietly give up.

The failures are not even random. Large providers deliberately throttle bulk resolution, so the more thorough your crawl, the faster it gets shut down. Authoritative servers using GeoDNS hand back different answers by location, so a single vantage point silently misses records that only appear in one region. By the time you have engineered around all of it, you have built a small distributed system whose only output is data someone already sells finished.

That is the problem webatla already solved. We resolve the whole namespace on a rolling schedule, parse every answer into structured JSON, and hand you the finished dataset. You skip the crawl, the bans, and the parsing, and go straight to the data.

How webatla collects every record

The difference from a DIY crawl is distribution and patience. webatla resolves the namespace from many vantage points on a rolling schedule, so no single resolver is ever hammered, and every answer is validated and parsed into a typed entry before it reaches the export. A name that fails one pass is retried on the next, so coverage climbs over time instead of decaying. The result is the part you actually wanted all along. A clean, typed entry for every name, not a pile of packets to debug.

Every DNS record, in one file

The webatla DNS dataset is the answer to getting all DNS records at once. Every domain we track, with its A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and DNSSEC entries collected and parsed into one clean dataset. It spans every TLD, it is rebuilt on a rolling basis, and it arrives as JSONL you can query the moment it lands.

No resolver farm to run, no packets to parse, no per-domain rate limit to fight. You buy it once and pull every record on the internet from a single account, ready for analysis in minutes rather than months.

What each line looks like

Each line is one name and its full picture. Alongside the values themselves, every row carries when the data was last checked and whether the lookup succeeded, so you always know how fresh each answer is:

{"domain":"example.com","dnsAt":"2026-06-22","dnsStatus":"TRUE","dnsRecords":{"A":["93.184.216.34"],"MX":[{"host":"mail.example.com","priority":10}],"NS":["a.iana-servers.net","b.iana-servers.net"],"TXT":["v=spf1 -all"],"SOA":{"mname":"ns.icann.org","serial":2026062201,"refresh":7200}}}

Field	Meaning
`domain`	the domain the records belong to
`dnsRecords`	every type keyed by name (`A`, `MX`, `TXT`, and the rest)
`dnsAt`	the date this domain's DNS was last checked
`dnsStatus`	whether the lookup succeeded

Need the registration details behind each domain too? Layer the RDAP and WHOIS dataset. Want DNS, registration, and technologies in one place? The all-data bundle joins them for you.

How to work with the file

Because it is JSONL, one domain per line, the data streams into jq, DuckDB, pandas, or Spark without loading into memory. A few examples.

Pull every name and its mail servers:

jq -c '{domain, mx: .dnsRecords.MX}' dns.jsonl

Find every name whose nameservers run on Cloudflare:

jq -c 'select(.dnsRecords.NS[]? | test("cloudflare"))' dns.jsonl > cloudflare-dns.jsonl

Count the names that publish an SPF record, straight over the data:

grep -c '"v=spf1' dns.jsonl

That last line answers an email-security question across the whole internet in seconds. We used the same data to map nameserver and registrar concentration, and the method is identical. One file, one pass, a real answer.

What a full DNS dataset unlocks

Once every entry sits in one queryable dataset, a lot of expensive problems collapse into one-line filters. The value is not any single lookup, which anyone can run by hand. It is holding them at once, so a question that used to mean crawling a million names becomes a scan of a dataset you already have.

The pattern is always the same. The hard part was never the analysis. It was getting complete, current, structured data in the first place, and doing it without a team babysitting a crawler for a quarter. Remove that bottleneck and the questions you can answer in an afternoon are the ones that used to need a project and a budget. What you are paying for is not a clever query. It is the clean, finished input that makes the clever query trivial.

Email security at scale. Read the SPF record and mail setup for every name to find spoofable inboxes, audit a customer base, or size a market by email provider.
Attack-surface mapping. Follow A, AAAA, and CNAME records to see where a domain and its subdomains actually resolve, and which shared hosts cluster together. Grouping those A records by IP turns the export into a hosted domains database.
Provider intelligence. Group domains by NS or MX to measure who runs DNS and email for the internet, and track migrations as they happen.
DNSSEC adoption. Count DS, DNSKEY, and RRSIG records to see which zones are signed and which are not.
Certificate hygiene. A CAA record shows which authorities a name trusts to issue its certificates, so a misconfiguration across a whole portfolio surfaces in one pass.
Migration tracking. When a company moves email or hosting, its MX and NS entries change first, so watching those two record types over time reveals the move before any announcement.

Each of these needs the same starting point. One complete, current set of DNS records for the whole domain namespace, not a sample you resolved by hand.

Always fresh, never a one-time dump

DNS is not static. An A record moves when a site changes host, MX records change during an email migration, and a TXT record shifts every time someone updates a security policy. A file you resolved six months ago is a museum piece.

The webatla DNS dataset is rebuilt on a rolling schedule, and every name carries its own dnsAt timestamp, so you always see how current each entry is. Re-pull on whatever cadence your work needs, and each file reflects the DNS of today.

Frequently asked questions

Which DNS record types are included? The common ones every domain uses, including A, AAAA, CNAME, MX, TXT, NS, SOA, and CAA, plus DNSSEC records like DS, DNSKEY, and RRSIG where present. Everything is parsed into typed JSON, so you never touch a raw packet.

How many domains does it cover? DNS records for the domains across every TLD that webatla tracks, hundreds of millions of them, in one file.

Can I get just MX or just TXT records? Yes. The file holds every record type per domain, so a single jq or SQL filter gives you only the MX records, only the SPF strings, or whatever slice you need. It is a filter, not a separate purchase.

What format is it? Clean JSONL, one domain per line, with DNS records as structured JSON. It drops straight into jq, DuckDB, pandas, and BigQuery.

How current is the data? Rebuilt on a rolling schedule, and each domain carries a dnsAt date so you can see how fresh its records are. Never a stale one-time dump.

Can I match records to IP ownership or location? The A and AAAA records give you the IP addresses, which you join to an IP-intelligence source for ASN reliably and geography approximately.

Do the records cover subdomains? The set is keyed by the registered name, and it captures the entries published at that name.

What does it cost? One flat price for a month of access on a single account. See pricing for the current figure.

Download every DNS record

Stop building a resolver farm that gets you banned before it finishes. Download the webatla DNS dataset → and have every DNS record for every domain, A through DNSSEC, as clean JSONL you can query today. Want registration and technology data alongside it? The all-data bundle carries DNS and the rest in one place. It is the fastest way from "I need all the DNS records" to actually having them.

How to download list of all registered domains

2026-07-01T12:11:00.000Z

Every registered domain on the internet, in one file — that is what you are really after, and there is exactly one practical way to have it. Not a sample, not a single extension, not a scrape that dies at the first rate limit. You want the complete set of domains across every TLD — clean, current, and ready to query. Here is how you get it, and why building it yourself is a trap.

How big is a list of all registered domains?

Bigger than most people expect. Hundreds of millions of domains are registered across the world's TLDs right now, and the number moves every day as new names appear and old ones drop. That is not a file you keep in a spreadsheet; it is a serious dataset.

.com alone is past 160 million domains — roughly 40% of the whole namespace on its own. Add .net and .org, the newer extensions (.io, .ai, .xyz, .shop), and hundreds of country codes, and the full picture runs to hundreds of millions of individual domain names. That scale is exactly why a complete set of every domain is one of the most valuable datasets on the internet: it sits under sales pipelines, brand protection, security research, and market intelligence. It is also why nobody hands it out for free.

The .com question everyone starts with

Most people who want "all the domains" really start with .com, because .com is the market — at over 160 million names it dwarfs every other extension, and any serious plan has to handle it first. The good news: once you have the complete set, isolating it is a one-line filter. Every .com domain sits in the same file as every .net, .org, and country-code name, so you slice it out the moment you need it and keep the long tail for later.

That is the difference between a .com-only export and a complete dataset: with the whole set in hand, .com is a view, not a separate project — you never re-buy .net next quarter because the first file only covered one extension.

Why you cannot assemble it yourself

There is no master registry of everything. Each TLD runs on its own operator's infrastructure, under its own rules, in its own format — and the overwhelming majority never publish a usable feed at all. Stitching a complete, de-duplicated, current picture together across every one of them is not a weekend script; it is a standing data operation that most teams start, badly underestimate, and quietly abandon three months in. The ones who push through end up maintaining brittle scrapers, chasing format changes across dozens of registries, and explaining to their team why the domain list is a week out of date again.

That is the problem webatla already solved. Rather than burn a quarter chasing hundreds of incompatible sources and still ending up with gaps, you get one file that already holds every domain we track, refreshed daily.

What makes it a complete, usable set

A pile of raw registry dumps is not a dataset — it is homework. The value is in the work that turns hundreds of fragmented sources into one file you can actually query, and that is exactly what you are buying:

Coverage — every TLD, from .com and .net down to the smallest country code, in a single set. Nothing missing because one registry was hard to reach.
De-duplication — one clean row per domain, no collisions from overlapping sources.
Normalisation — a consistent schema across every extension, so example.com and example.co.uk parse the same way.
Freshness — rebuilt daily, so the set reflects the domains that exist today, not last quarter.

That combination is the difference between "I technically have the data" and "I can answer a question with it before lunch."

The whole set, in one file

webatla's full domains dataset is the list itself: every domain across every TLD, de-duplicated and normalised into one clean file, rebuilt every day. No applications, no approvals, no per-registry paperwork — buy it once and pull the entire namespace as fresh JSONL.

It is deliberately the cheapest, highest-volume product we sell, because it is the base everything else builds on: one flat price, a month of downloads, and every domain on your disk in minutes rather than months.

What each line looks like

Each line is one domain name, structured so you can filter and segment hundreds of millions of records without standing up a database. A single row is as simple as this:

{"domain": "example.com", "tld": "com", "suffix": "com", "domainType": "ICANN"}

Field	Example	Use
`domain`	`example.com`	the registration itself
`tld`	`com`	filter by TLD
`suffix`	`co.uk`	handle multi-level suffixes correctly
`domainType`	`ICANN`	separate gTLD from private namespaces

The base set tells you which domains exist. When you need the registration record behind each one — who owns it, when it was created, and through which registrar — layer the RDAP & WHOIS dataset. Add the DNS dataset for nameservers, or Technologies for what each site runs. Same set of domains, enriched from whatever angle you need.

Working with a file this large

Every webatla dataset ships as JSONL — one JSON object per line, the only format that scales to hundreds of millions of domains. It streams line by line and drops straight into jq, pandas, DuckDB, BigQuery, or Spark, so you never load the whole file into memory.

Rank every extension by domain count with one line of jq:

cat domains.jsonl | jq -r .tld | sort | uniq -c | sort -rn | head

Pull just the .com domains into their own file:

jq -c 'select(.tld == "com")' domains.jsonl > com.jsonl

Or query the whole set in place with DuckDB — no database, no index:

SELECT tld, count(*) AS domains
FROM 'domains.jsonl'
GROUP BY tld
ORDER BY domains DESC;

That single query turns the raw file into a per-extension map of the entire domain market in seconds. We ran the same data to break down DNS and registrar concentration and the fastest-growing TLDs of Q1 2026.

Who relies on a complete domains set

The teams that buy the full set of domains span every industry, but they share one problem: partial data quietly breaks their work, and the gaps stay invisible until something downstream goes wrong.

Sales and go-to-market — a total-addressable-market view is only accurate if it starts from every domain. Filter to a .com niche, a country code, or a technology footprint and you are prospecting the whole market, not a slice of it.
Brand and trademark teams — find every domain that contains your brand across all extensions, and a dormant .com typo-squat surfaces before it is weaponised.
Security and threat intel — sweep the whole namespace for phishing patterns, suspicious nameserver clusters, and new look-alikes that a partial feed would miss.
Domain investors and registrars — track domain movement per extension over time and spot where demand is shifting.
Data and ML teams — train and evaluate on a clean, deduplicated set of real domain names, not a scraped sample that skews the model.

Every one of these needs the same starting point: one complete, current set of domains you can trust, not a stale export or a half-finished scrape.

The real cost of an incomplete list

A partial list fails silently, and that is what makes it dangerous. A total-addressable-market number looks solid until you learn it was built from a fraction of the domains that actually exist. A brand sweep comes back clean — not because there are no look-alikes, but because the data never contained them. A model trains on a skewed sample and nobody notices until the predictions quietly drift.

Completeness is the whole point of a domains list, not a nice-to-have. A set that is missing the country codes, or last week's registrations, or the parked long tail, biases every count and every match built on top of it. Buying one authoritative file instead of stitching fragments together is exactly what removes that blind spot — one file, every domain, so the answer you get is the one that is actually true.

From file to first answer in minutes

There is no ETL project to run before you get value. You open one file, point jq or DuckDB at it, and you are querying the entire domain namespace immediately — count .com versus .net, isolate a country code, or pattern-match a brand across every extension in a single pass. Because it is plain JSONL, the same file feeds a Python notebook, a Spark job, or a BigQuery load without conversion. The gap between buying the data and answering a real question is measured in minutes, not sprints. That is the practical case for buying the set outright: the moment it lands it is already doing work, and your time goes to the analysis instead of the plumbing.

Always current, never stale

A domains file ages fast. Names are registered and dropped every minute, so a file from six months ago is mostly noise for anything time-sensitive — and the fresh domains that signal a launch or a campaign are exactly the ones a stale set misses. That is why the dataset is rebuilt daily and every export is versioned by date: you always know precisely what you are holding and when it was cut. If catching brand-new registrations the day they appear is the point, the Domain Investor dataset is built around fresh domains across every extension.

Frequently asked questions

How many registered domains are there? Hundreds of millions across every extension combined, and the figure moves daily. .com alone is past 160 million — roughly 40% of the total. Because it changes constantly, a dated, daily-rebuilt set is the only version worth working from.

Can I download all .com domains on their own? Yes. Filter the full dataset by tld == "com" and you have every .com domain in its own file. .com is the largest extension by a wide margin, so expect a big one — but it is a filter, not a separate purchase.

Does the file include more than .com? Yes — .com is just the largest slice. The set spans .net, .org, .io, .ai, and every other extension down to the smallest country code, all in the same file.

Can I get only newly-registered domains? Yes — filter by registration date, or start from the Domain Investor dataset, which focuses on fresh registrations across TLDs.

What format is it, and how current? Clean JSONL, one domain per line, rebuilt daily and versioned by date — never a stale historical dump.

Can I use the full list commercially? Yes — sales, security, brand protection, research, and product features are all standard uses. One flat price covers a month of access for whatever you are building on top of the data.

What does it cost? One flat price for a month of access, no subscription. See pricing for the current figure; it is the lowest-cost way to put every domain on your disk.

Download the full list

Stop trying to reassemble the internet's domains one registry at a time — it is a project that never finishes. Download webatla's full domains dataset → and have every registered domain across every TLD, .com and the long tail alike, as clean, current JSONL today. Or browse all datasets to see everything you can layer on top. No registries to chase and no approvals to wait on — just the complete set of domains, working the moment it lands. It is the fastest path from "I need all the domains" to actually having them.

Who Controls the Internet's Plumbing? DNS and Registrar Market Share in 2026

2026-06-23T18:33:00.000Z

Two companies answer DNS for a quarter of all domains, and one company registers nearly a fifth of them — once you untangle the shell entities it hides behind. I pulled webatla's full index of roughly 405 million domains — a June 2026 snapshot — joined its authoritative nameserver and registry records, and measured who actually controls the internet's plumbing. This is the DNS provider market share 2026 and domain registrar market share 2026 picture, with the consolidation the raw leaderboards quietly understate — plus a tour of the oldest domains still online.

How concentrated is DNS?

Start with DNS, because it is the layer most people never think about and every request depends on. I grouped all ~405M domains by their authoritative nameserver provider. Here is the top of the table.

DNS provider market share 2026 - share of all domains by nameserver provider

Rank	Nameserver provider	Operator	Share of all domains
1	domaincontrol.com	GoDaddy	14.24%
2	cloudflare.com	Cloudflare	10.65%
3	googledomains.com	Google Cloud DNS	2.81%
4	registrar-servers.com	Namecheap	2.79%
5	afternic.com	GoDaddy / Afternic	2.49%
6	ui-dns.biz	IONOS	2.32%
7	dns-parking.com	—	2.27%
8	wixdns.net	Wix	1.76%
9	hichina.com	Alibaba Cloud	1.52%
10	share-dns.com	—	1.01%

The headline: just two providers — GoDaddy's domaincontrol.com and Cloudflare — answer DNS for 24.90% of all domains. (GoDaddy's real footprint is larger still: afternic.com at #5, another 2.49%, is also GoDaddy.) The top five reach 32.98%, the top ten 41.87%, and the top twenty 49.23%. The 37 providers I could attribute cover 55.23% of all domains. That is what DNS concentration looks like in 2026: a long tail of self-hosted and niche nameservers, sitting under a very short head.

Why DNS concentration is systemic risk

This matters beyond trivia. DNS is a single point of failure: if your nameserver provider goes dark, your domain effectively vanishes even though your servers are fine. When a provider answers for 10%+ of all domains, its bad day is the internet's bad day. The textbook case is the October 2016 DDoS attack on the managed-DNS provider Dyn, which made Twitter, Spotify, Reddit, Netflix and PayPal unreachable for hours — not because those companies failed, but because they shared one DNS dependency. It keeps happening: a single Cloudflare internal error on 18 November 2025 took down X, ChatGPT, Claude and Shopify at once. Concentration trades resilience for convenience. Cloudflare at 10.65% and GoDaddy at ~14% are not just big businesses; they are shared dependencies for a meaningful slice of the web. If you run infrastructure, security, or you're underwriting risk, the DNS dataset lets you measure your own exposure rather than guess at it.

Domain registration tells a similar story — but the largest-registrars leaderboard is actively misleading if you read it raw, because the giants register under many legal entities at once.

Domain registrar market share 2026, raw vs consolidated by owner

Here is the raw leaderboard — share of all domains by single legal entity:

Rank	Registrar (legal entity)	Share of all domains
1	GoDaddy.com LLC	16.91%
2	NameCheap Inc	5.29%
3	Tucows	2.55%
4	Squarespace Domains II	2.02%
5	Hostinger	1.95%
6	Dynadot Inc	1.88%
7	Gname	1.78%
8	GMO / Onamae	1.75%
9	Spaceship	1.67%
10	IONOS SE	1.66%

Raw, the top five hold 28.72% and the top ten 37.45%; the 100 registrars listed cover 70.52% of all domains.

What the raw leaderboard hides: shell entities

The problem is that "GoDaddy.com LLC" is only one of GoDaddy's ICANN-accredited registrars. GoDaddy owns Wild West Domains, LLC (a separate accredited entity, IANA ID 440) and operates several others. When I consolidated the multiple legal names each owner registers under — webatla's own grouping methodology, mapped by hand against the IANA registrar-ID registry — the picture shifts:

Owner	Consolidated share	Legal entities	Biggest single entity
GoDaddy	19.64%	7	16.91%
Namecheap	6.06%	2	5.29%
Squarespace / ex-Google Domains	3.13%	2	2.02%
Tucows	2.55%	1	2.55%
Dynadot	2.40%	2	—
Alibaba Cloud / HiChina	2.20%	3	—
Hostinger	1.95%	1	1.95%
IONOS	1.90%	2	—
NameSilo	1.78%	2	—
Gname	1.78%	1	1.78%

GoDaddy jumps from 16.91% to 19.64% once you merge the seven GoDaddy entities in our data — almost three full points of market share invisible on the raw leaderboard. Consolidated, the top three owners control 28.83% of all domain registrations.

The most striking re-grouping is at #4. "Squarespace Domains II LLC" is literally the renamed Google Domains registrar. The proof is clean: IANA registrar IDs are permanent and never reassigned. Google's registrar held IANA ID 895; the IANA registry now lists ID 895 as "Squarespace Domains II LLC." Squarespace bought the ~10M-domain Google Domains book in 2023 and inherited the entity outright. (Confusingly, the googledomains.com nameservers back in the DNS table are still Google's own Cloud DNS — only the registrar business moved to Squarespace.) Similarly, Alibaba Cloud, HiChina, and Wanwang are one registrar (IANA ID 1599); Network Solutions, Register.com, and Domain.com all roll up to Newfold Digital. If you want to study this lineage yourself, the registrar and creation-date fields live in the RDAP/WHOIS dataset — and our post on RDAP vs WHOIS explains why we standardised on RDAP.

Brand-protection vs mass-market registrars

Here is the counterintuitive part. The volume giants do not hold the internet's marquee domains. In our data, the famous, high-value names cluster at corporate brand-protection registrars instead:

Registrar	Holds in our data (examples)
MarkMonitor	google.com, googleapis.com, youtube.com, gstatic.com
CSC Corporate Domains	twitter.com, ibm.com, att.com, nginx.org
Cloudflare Registrar	cloudflare.com, discord.com, ietf.org

GoDaddy, Namecheap, and Hostinger own the mass volume — tens of millions of ordinary domains — but the names a Fortune 500 legal team loses sleep over sit at MarkMonitor and CSC, where the pitch is security and trademark defense, not price. Market share by count and market share by value are two different maps. The all-data join lets you draw both.

The oldest domains on the internet

Joining registry creation dates onto the active-domain list surfaces the internet's living fossils — the oldest domains still registered and resolving today.

Timeline of the oldest domains still registered, from symbolics.com 1985

Domain	Registered	Registrar now (our data)
symbolics.com	1985-03-15	—
think.com	1985-05-24	MarkMonitor
mitre.org	1985-07-10	—
dec.com	1985-09-30	Squarespace
northrop.com	1985-11-07	CSC
xerox.com	1986-01-09	MarkMonitor
hp.com	1986-03-03	—
bellcore.com	1986-03-05	CSC
ibm.com	1986-03-19	CSC
intel.com	1986-03-25	MarkMonitor
att.com	1986-04-25	CSC

symbolics.com, registered 1985-03-15, is the first .com domain ever — and it is still online. Behind it sits a roll call of 1980s computing: a Lisp-machine maker, Digital Equipment, Xerox, HP, IBM, Intel, AT&T. Notice how many of these now sit at MarkMonitor and CSC — the same brand-protection pattern, applied to the oldest and most valuable names on the network.

An honesty caveat on the dates

A few records in the data carry obviously fake timestamps: nordu.net is stamped 1985-01-01, and a cluster of .se domains all read 1985-01-17. Those dates predate symbolics.com — but they are almost certainly registry default/placeholder values, not real registrations, so I will not claim them as "older than the first .com." The verifiable first .com is symbolics.com on 1985-03-15. Stating that plainly matters more than a flashier number; if the data has a soft spot, you should hear it from me, not discover it later.

"Concentration this deep is a systemic-risk question, not a trivia question. The point of owning the raw data is that you can measure your own exposure — you don't have to trust a vendor's dashboard to tell you how exposed you are to the vendor." — Alan, webatla CEO

Methodology

A few notes so you can judge — and reproduce — the analysis:

Scope and date. This analysis was run in June 2026; every figure is a point-in-time snapshot of that month and will drift as domains are registered, dropped and transferred. All figures are shares of webatla's full active-domain index of ~405 million domains. DNS shares are computed from each domain's authoritative nameserver provider; registrar and creation-date figures come from registry/RDAP records.
Entity consolidation is ours. The raw registrar table reflects single legal entities exactly as registries report them. The consolidated table is webatla's grouping: we map each accredited legal entity to its true owner — verified against the IANA registrar-ID registry — so that GoDaddy's seven entities, Alibaba's three, and Squarespace's inherited Google book count once, under the right parent. We publish both so you can see exactly what we merged.
No SQL required. This is creation-date and nameserver data joined across two files. Every number here traces to a column you can pivot in a spreadsheet — no query engine needed.
We flag soft data. Placeholder registration dates (the 1985-01-01 / 1985-01-17 records) are kept in the raw data but excluded from the "first .com" claim.

FAQ

What is the most popular DNS provider in 2026? GoDaddy's domaincontrol.com, the authoritative nameserver for 14.24% of all domains, followed by Cloudflare at 10.65%. Together those two answer 24.90% of the internet's DNS.

Which registrar has the most domains? GoDaddy. Its flagship entity, GoDaddy.com LLC, holds 16.91% of all domains on its own; consolidating the GoDaddy entities in our data brings the group to 19.64% — comfortably the largest registrar by domain count. The registrar field comes from the RDAP/WHOIS dataset.

What was the first .com domain? symbolics.com, registered 1985-03-15, and it is still online today. Some records in the raw data carry earlier placeholder dates (e.g. 1985-01-01), but those are registry defaults, not real registrations.

Is Squarespace really the old Google Domains registrar? Yes. "Squarespace Domains II LLC" is the renamed entity that held Google Domains — IANA registrar ID 895, which is permanent and never reassigned, still points to that same registrar of record.

How concentrated is the domain market overall? The top two DNS providers cover 24.90% of domains and the top ten cover 41.87%; on the registrar side, the top ten legal entities cover 37.45% — or about 43.4% once you consolidate them by owner. Concentration is high at the head and falls off into a long tail.

Get the data and measure it yourself

Vendor dashboards show you their slice. The raw data lets you measure the whole market — DNS concentration, registrar ownership, domain age — on your own terms.

DNS dataset — €199 → authoritative nameserver records per domain. Powers the DNS-concentration analysis above.
RDAP/WHOIS dataset — €299 → registrar and creation date per domain. Powers the registrar-consolidation and oldest-domains analysis.
All-data join — €599 → everything joined into one file — do all of the above in a single pivot.
All active domains — €29 → the base domain list everything builds on.

Browse the full catalogue on the datasets page and pricing →. If you're new to the data, start with how to download a list of all active domains, then see what the AI domain boom and the fastest-growing TLDs of Q1 2026 are doing to the TLD landscape.

We've upgraded webatla — please reset your password and regenerate your API keys

2026-06-13T21:53:00.000Z

We've completed a major upgrade to webatla's platform and the infrastructure behind it. The site now runs on rebuilt, faster application servers, sits behind Cloudflare, and ships with hardened TLS and an improved account and API layer.

As part of that work we rotated the security keys that protect login sessions and API tokens. So that only you hold the keys to your account going forward, we're asking every account holder to take two quick steps.

What you need to do

Reset your password. Open Reset your password, enter your email, and follow the link we send to choose a new one.
Regenerate your API keys. Go to your API settings, generate a fresh key, and update any scripts or integrations that use the old one.

Both steps take less than a minute, and you only need to do them once.

Your datasets and access are safe

Nothing you paid for has changed. Every dataset you've purchased — along with your download access and full order history — carried over to the new platform untouched. You don't need to buy anything again, and no files or entitlements were lost.

Why we're asking

Rotating credentials after an infrastructure change is routine security hygiene. It guarantees a clean break so that, going forward, you are the only person holding the keys to your account and API access. It's a precaution, not a sign that anything went wrong — and your data was never exposed.

Questions?

If you have any trouble resetting your password or regenerating a key, reach us through our contact page and we'll help you right away.

— The webatla team

RDAP vs WHOIS: How Domain Lookups Work in 2026

2026-06-13T16:28:20.775Z

For four decades, WHOIS was how you looked up who registered a domain. That era is ending. RDAP — the Registration Data Access Protocol — has replaced it as the standard, and as of 2025 registries are no longer required to run the legacy WHOIS service at all. Here's what changed, why it matters, and how to query registration data the modern way.

What is WHOIS?

WHOIS is a simple request/response protocol that dates to 1982 (RFC 812, later RFC 3912). You connect to a server on port 43, send a domain name, and get back a blob of text describing the registrant, registrar, key dates, and nameservers.

It worked — but it was built for a different internet:

Unstructured text. Every registry formatted its output differently, so parsing was a perpetual game of regex whack-a-mole.
No internationalization. It was ASCII-oriented, and non-Latin registrant data was a mess.
No standard access control. All-or-nothing output collided badly with privacy law like GDPR.
No standard discovery. You had to already know each TLD's WHOIS server.

What is RDAP?

RDAP (RFCs 7480–7484, updated by 9082/9083) is the modern replacement. Same goal — registration data — but redesigned from the ground up:

JSON over HTTPS. Structured, predictable responses you can parse reliably.
A standard query scheme. Consistent URLs like https://rdap.example/domain/example.com.
Bootstrapping. IANA publishes a registry that tells you which RDAP server is authoritative for any TLD, so discovery is automatic.
Differentiated access. It's authentication-aware, so a registry can return more data to authorized users while showing the public a redacted view — the GDPR-friendly model.
Internationalization and redaction are first-class concerns, not afterthoughts.

RDAP vs WHOIS: the key differences

	WHOIS	RDAP
Format	Free-text	Structured JSON
Transport	Port 43 (plaintext)	HTTPS
Discovery	Manual, per registry	IANA bootstrap registry
Access control	None	Standardized, auth-aware
Internationalization	Poor	Built-in
Status	Being retired	Current standard

Why the industry switched

ICANN ratified RDAP as the successor to WHOIS and required gTLD registries and registrars to implement it. The decisive moment came in 2025, when contracted parties were no longer obligated to operate the legacy port-43 WHOIS service — formally ending WHOIS's run for gTLDs. If you're still building on WHOIS text parsing, you're building on a deprecated foundation.

How to query RDAP

A lookup is just an HTTPS GET. To find the right server you can consult the IANA bootstrap file, or hit a router endpoint that resolves it for you:

curl -s https://rdap.org/domain/example.com | jq '{
  domain: .ldhName,
  status: .status,
  registrar: (.entities[]? | select(.roles[]? == "registrar") | .vcardArray[1][1][3]),
  created: (.events[]? | select(.eventAction == "registration") | .eventDate)
}'

Because the response is structured JSON, pulling a specific field — registration date, status, nameservers — is a one-liner instead of a fragile parser.

Querying registration data at scale

RDAP is ideal for one domain at a time. For millions of domains you run into two walls: rate limits and per-TLD server quirks — every registry runs its own endpoint, with its own throttling and redaction rules.

That's the gap the RDAP & WHOIS dataset fills. We resolve registration data across every active domain and ship it as normalized JSONL — registrar, key dates, status, and nameservers in a single consistent schema — so you can analyze the whole namespace without running a distributed crawler or babysitting rate limits.

Frequently asked questions

Is WHOIS dead? For gTLDs, effectively yes — RDAP is the required protocol and the port-43 mandate has ended. Some ccTLDs still run legacy WHOIS, but the direction of travel is one-way.

Is RDAP data different from WHOIS data? It's the same registration data, exposed in a structured, access-controlled way. Public responses are often redacted for privacy; authenticated access can return more.

Can I bulk-download registration data? Per-domain RDAP is rate-limited, so live bulk work is impractical. A prepared dataset is the scalable route.

How do I find the RDAP server for a TLD? Use IANA's bootstrap registry, or a router like rdap.org that resolves it for you. You can browse coverage by TLD.

Work with registration data the modern way

Stop parsing port-43 text. Get the RDAP & WHOIS dataset → for structured registration data across every domain, or see all datasets to combine it with technologies, ranking, and DNS.

The .ai Domain Boom: From 900 to 71,000 New Registrations a Month

2026-06-01T18:37:00.000Z

The .ai domain didn't grow. It detonated. In 2018, webatla logged 10,807 new .ai registrations across the whole year — a sleepy little ccTLD ticking over at roughly 900 a month. In 2025, we logged 478,794. That is the same TLD, a little over 44 times bigger, and the inflection point lines up almost to the day with the moment the world started talking to chatbots.

This is the story of how a Caribbean country-code domain became the default address bar of the AI era, told entirely through webatla's own monthly new-registration counts. The numbers below are our series and ours alone — no estimates, no round-tripping through third-party totals.

Monthly new .ai domain registrations, Jan 2018 - May 2026

The quiet years (2018-2021)

For most of its life, .ai was a curiosity. It's the country-code domain (ccTLD) for Anguilla, a British Overseas Territory in the Caribbean, delegated by IANA back on 16 February 1995. The two letters just happened to also spell the abbreviation for "artificial intelligence" — a coincidence worth, as we'll see, tens of millions of dollars a year.

But for a long time nobody cared. Here's what the early run looked like in our data:

Year	New .ai registrations	Avg / month
2018	10,807	901
2019	11,850	988
2020	17,446	1,454
2021	21,097	1,758

2018 was a flat plateau — somewhere between 800 and 1,100 registrations every month, all year. The pandemic nudged things up: 2020 stepped to a 1,454/month average as the whole web swelled, and 2021 kept that drift going to 1,758. Respectable, organic, boring. If you'd told a domain investor in 2021 that this TLD would soon out-register most of the legacy gTLDs, they'd have laughed.

The inflection: late 2022 and a chatbot

ChatGPT launched on 30 November 2022. You can see it land in our data within weeks.

December 2022 posted 3,868 new .ai registrations — already the first real spike, well above that year's 2,238/month average. Then January 2023 hit 6,715. That's a +74% jump month over month, December to January, with no holiday season, no registry promotion — just a sudden, global realization that "ai" was now the most valuable two letters in tech.

The full-year comparison is the part that still looks like a typo:

Year	Total	Avg / month	vs. prior year
2022	26,851	2,238	—
2023	141,620	11,802	~5.3x
2024	244,799	20,400	~1.7x
2025	478,794	39,900	~2.0x

2023's monthly average of 11,802 is roughly 5.3 times the 2022 average of 2,238. The TLD didn't grow into demand gradually; it got yanked upward the instant a consumer product made "AI" a household word. This is one of the cleanest single-event signals you'll find anywhere in domain data, which is exactly why we keep datasets that let you watch fresh registrations by TLD over time.

The new plateau — and a record run

What's notable is that 2023 wasn't a one-off bubble that popped. The new level held and then kept climbing. 2024 nearly doubled 2023 (244,799), and 2025 nearly doubled again to 478,794 — by itself 44.3 times the entire 2018 total. Across 2018 to 2025 that works out to a compound annual growth rate of about 72% per year.

Then the run got even hotter at the turn of 2026:

Month (2026)	New .ai registrations
January	46,081
February	60,818
March	71,227
April	25,715 (partial)
May	9,104 (partial)

March 2026's 71,227 is the single biggest month in our entire .ai series — the all-time peak on record. To put the whole arc in one number: from January 2018 through May 2026, this series contains 1,166,209 new .ai registrations.

A necessary, honest caveat

Look at that table again and you'll see April (25,715) and May (9,104) fall off a cliff after March's record. Do not read that as a decline in .ai demand. Today is 22 June 2026, and registration data takes time to settle — there's collection lag, late-arriving records, and reconciliation that hasn't finished yet for the most recent weeks. Those last one or two months are almost certainly incomplete, not evidence that the AI domain rush is over. Every prior month in this series filled in over time, and these will too. We'd rather show you partial data clearly flagged than quietly hide it and pretend the curve is smooth.

What .ai actually is — and Anguilla's windfall

The reason this matters beyond a pretty chart: a tiny Caribbean government is funding itself off the AI hype cycle.

.ai's namespace is owned by the Government of Anguilla, which sets policy as the sponsoring organization of record. For roughly three decades the registry was administered by Vince Cate, a US expatriate who'd moved to the island in the mid-1990s and, by his own account, was handed the ccTLD by IANA's Jon Postel and passed most of the revenue to the government. In an early-2024 interview, Cate pegged the registry at "about US$3 million per month" — "already like a third of the government's budget."

The IMF put 2023 .ai revenue at roughly EC$87 million (about US$32 million), just over 20% of Anguilla's total government revenue, rising to around US$39 million in 2024. By late 2024 the TLD had passed 500,000 registrations and the government signed a five-year deal — announced 15 October 2024 — handing back-end registry services to Identity Digital, the US provider behind hundreds of gTLDs. Identity Digital took over operations on 15 January 2025, reportedly returning about 90% of revenue to Anguilla.

A couple of practical quirks worth knowing if you actually register one:

.ai requires a minimum 2-year term, available from 2 up to 10 years. There is no one-year option.
There are no residency requirements. Despite being Anguilla's ccTLD, anyone worldwide can register; open second-level registration has been available globally since 15 September 2009.

What this means if you track domains

If you watch TLDs for a living — investing, brand protection, competitive intelligence, or just trend-spotting — .ai is the textbook case for why fresh-registration data beats a static snapshot. A point-in-time count would tell you .ai is "big." Only the monthly series tells you when it got big, how fast, and whether the curve is still bending up. That timing is the signal.

The same approach surfaces the next .ai before it's obvious. The TLD that's quietly stepping from 900 to 1,700 a month — the way .ai did in 2019-2021 — is the one worth watching, and you can only spot it if you're tracking new registrations month over month rather than reacting to headlines.

Once a TLD is on your radar, the follow-up questions are about what sits behind those domains: what each site runs, and the registration record for each one. And if you're starting from zero, our guide to downloading the full list of active domains walks through the realistic options. You can always browse the full TLD directory to see where .ai sits among everything else.

FAQ

Is .ai really an AI domain? No — that's the fun part. .ai is the official country-code TLD for Anguilla, a Caribbean British Overseas Territory, and has been since 1995. The "AI" meaning is a happy coincidence the market ran with.

Are .ai registrations actually declining in 2026? No. The low April and May 2026 figures in our data are incomplete — recent months are still settling as of this writing (22 June 2026). The most complete recent month, March 2026, was the highest on record at 71,227.

Why does .ai cost more than other domains? The registry mandates a minimum 2-year registration term (you can't buy a single year), and .ai is a significant revenue source for the Anguillan government, which keeps the bulk of the proceeds.

How many new .ai domains has webatla counted? From January 2018 through May 2026, 1,166,209 new .ai registrations in this series — with 2025 alone accounting for 478,794 of them.

Get the data

This entire post is one TLD pulled from data we refresh every day. Download the All Active Domains dataset → and you'll have every live domain across every TLD — .ai included — as clean JSONL for a flat €29, ready to slice however you like. If it's the fresh registrations you're after — the early-warning signal that caught .ai's inflection — the Domain Investor dataset is built for tracking which TLDs are heating up right now. Or browse all datasets to see what you can layer on top.

The Fastest-Growing TLDs of Q1 2026 (and Which Growth Is Actually Real)

2026-04-06T19:18:00.000Z

A +4,851% growth number can be perfectly accurate and still tell you almost nothing. Here are the fastest growing TLDs of Q1 2026, ranked by quarter-over-quarter growth, alongside the one question that actually matters: which of these spikes is a real trend, and which is a registry promotion dressed up as demand. I ran the query on webatla's own registration data. Below is the full ranking, the method, and a teardown of how to tell signal from noise.

The headline number first: across the top 50 TLDs in this query, new registrations went from 414,056 in Q4 2025 to 1,109,663 in Q1 2026 — a combined +168% quarter-over-quarter. That is a genuinely large move. But "combined" hides almost everything interesting, because the top of the percentage ranking is dominated by extensions growing from a base so small that the percentage is nearly meaningless.

The fastest-growing TLDs of Q1 2026

Here are the top 15 domain extensions by QoQ growth. Read the "Q4 base" column as carefully as the percentage — it's where the story is.

TLD	QoQ growth	Q1 2026	Q4 2025 base	Net adds
.makeup	+4,851.84%	114,338	2,309	+112,029
.garden	+1,678.23%	27,776	1,562	+26,214
.lol	+579.05%	295,727	43,550	+252,177
.mobile	+463.70%	3,478	617	+2,861
.boutique	+401.39%	5,786	1,154	+4,632
.fyi	+325.79%	11,292	2,652	+8,640
.delivery	+238.01%	3,664	1,084	+2,580
.ooo	+228.18%	2,294	699	+1,595
.immo	+227.73%	2,458	750	+1,708
.beauty	+217.52%	30,155	9,497	+20,658
.cv	+202.37%	5,621	1,859	+3,762
.best	+190.25%	9,050	3,118	+5,932
.food	+182.19%	7,718	2,735	+4,983
.date	+135.91%	1,281	543	+738
.link	+133.28%	47,324	20,286	+27,038

The 15 fastest-growing TLDs in Q1 2026 by quarter-over-quarter growth

.makeup tops the list at +4,851%. That is not a typo, and it is also not a market signal. It went from 2,309 registrations in Q4 to 114,338 in Q1 — a 49x jump from a base of barely two thousand domains. That is what a bulk or promotional registration event looks like, not what a new wave of beauty brands discovering the web looks like. .mobile (+463% from a base of 617) is the purest version of the trap: tiny base, big multiplier, and a genuinely small gain of just +2,861 domains. .garden is trickier — +1,678% and +26,214 net adds — a number that's big and fast, which we'll stress-test below.

The trap is treating the percentage column as a ranking of demand. It isn't. It's mostly a ranking of how small last quarter was.

Where the volume actually went

If you want to know which extensions real registrants are actually choosing, sort by net adds — Q1 minus Q4 — not by percentage. The ranking reshuffles completely.

TLD	Net adds	QoQ growth	Q1 2026 volume
.lol	+252,177	+579.05%	295,727
.makeup	+112,029	+4,851.84%	114,338
.asia	+85,580	+78.68%	194,345
.life	+32,892	+62.26%	85,719
.link	+27,038	+133.28%	47,324
.tech	+26,487	+50.29%	79,160
.garden	+26,214	+1,678.23%	27,776
.beauty	+20,658	+217.52%	30,155
.one	+19,048	+83.45%	41,875
.studio	+9,613	+53.26%	27,662

Net new .domain registrations added per TLD in Q1 2026

Look at .asia: +85,580 net adds, but only +78.68% QoQ. It never appears on the percentage leaderboard, yet it added more real domains than every TLD except .lol and .makeup. .life (+32,892, +62%), .tech (+26,487, +50%) and .one (+19,048, +83%) tell the same story — moderate, double-digit-percentage growth on top of an already-large base. That is what sustained adoption looks like. It's quiet. It never makes a "fastest-growing" headline because the percentage isn't flashy, but it moves far more domains.

These are the new gTLD registration trends worth tracking in 2026: not the 4,000% spikes, but the extensions adding tens of thousands of domains a quarter at a steady clip. By Q1 2026 absolute volume, the leaders are .lol (295,727), .asia (194,345), .makeup (114,338), .life (85,719) and .tech (79,160).

Signal vs noise: how to tell a real trend from a registry promotion

Here is the single most useful chart in this post. Plot every TLD with growth rate on one axis and Q1 volume on the other, and the bubbles sort themselves into three groups.

Scatter plot of TLD growth rate versus Q1 2026 registration volume, bubble size is net adds

Huge % from a tiny base (mostly noise): .mobile, .boutique, and the long tail below them (.delivery, .ooo, .immo, .date). Small Q4 bases, modest absolute gains — the percentage is almost pure arithmetic.
Promotion-driven volume (real domains, unproven trend): .makeup, .garden, .beauty — and much of .lol. These genuinely added domains in bulk (.makeup +112,029, the second-biggest gain of any TLD; .garden +26,214), so they are not "small volume." But the driver is pricing, not adoption — so watch renewals before calling any of them a trend.
Genuine sustained growth (signal): .asia, .life, .tech, .one, .link. Moderate double-digit growth on already-large bases — quiet, durable, and nowhere near the top of the percentage leaderboard.

.lol is the one extension that leads on both axes — the biggest absolute gainer (+252,177) and +579% — which would be the dream signal if the volume were clean. As the teardown below shows, it isn't.

The .makeup teardown

.makeup is the clearest case study of why high percentage alone is a trap. It entered the quarter on a Q4 base of just 2,309 registrations — a small TLD (around 166,000 domains in total), operated by XYZ.COM LLC on the CentralNic back-end. That tiny base is the precondition: a large absolute add turns into a stratospheric percentage by arithmetic alone.

Then there's a confirmed catalyst. XYZ Registry raised wholesale prices on .makeup, .beauty, .lol and thirteen other XYZ extensions effective 26 August 2025. Registrars responded exactly as you'd expect — Porkbun and others explicitly told customers to register or renew for up to ten years before the deadline to lock in cheap pricing. When a roughly $1.80 first-year price faces a jump to ~$13, you get a pull-forward: registrations that would have trickled in over years get compressed into a few months. That's a price event, not a demand event.

The same mechanism explains .beauty (+217% off a Q4 base of 9,497, same XYZ registry, same August price hike) and is a major factor in .lol — which carries the additional hallmarks of cheap bulk registration: a ~$0.99–$1.21 first year against a ~$25+ renewal, very high churn, and a documented abuse/spam reputation. So even .lol, the one TLD that's high on both axes, isn't unambiguous organic demand. A large chunk is cheap, speculative, high-churn registration that may not renew. High on both is better than high on percentage alone — but you still have to check whether it sticks.

For the rest — .garden (GoDaddy Registry), .mobile (Dish DBS, a near-dormant ~5K namespace where any bulk add explodes the percentage), .boutique and .fyi (both Identity Digital; .fyi is ~37% concentrated in a single registrar channel, the textbook fingerprint of a reseller or promo wave) — I found no single named promotion. But the pattern is unmistakable: small or dormant base, cheap first-year pricing, single-channel concentration. That combination is the signature of a promotion or speculative bulk registration, not proof of organic end-user demand.

"Registration velocity is a leading indicator — it tells you where capital and attention are moving a quarter or two before the market notices. But velocity has to be read correctly. A 4,000% spike from a registry price event and a steady 60% climb on a base of 80,000 domains are opposite signals wearing the same 'growth' label. The skill is telling them apart, and that's a data problem, not a marketing one." — Alan, CEO, webatla

This is the same lesson from our earlier teardown of the .ai boom: the durable trends are the ones still growing after the promo pricing ends. Velocity is the leading indicator; renewal is the confirmation.

Methodology: how we measure TLD growth

The method is deliberately simple. Take every domain's registration date, bucket it into quarters — Q1 2026 is January to March, Q4 2025 is October to December — group by TLD, and compare the two counts. QoQ growth is just the percentage change between them. The only fields it needs are each domain's TLD and its created registration date, so anything that can read the dataset's JSONL export reproduces it.

The decision that matters most is the minimum-base floor: I only counted TLDs with at least 500 registrations in the Q4 baseline. Without that floor, the leaderboard fills with micro-TLDs where five registrations becoming fifty reads as a "900% surge" that means nothing. Even with the floor, .makeup still posts +4,851% — which tells you how aggressively you have to read the base column. To harden it further, add a net-adds floor and rank by absolute gain, exactly as in the second table above.

A caveat I'd apply to my own numbers: these are creation-date counts from registry data, so they capture registrations, not surviving, renewed, in-use domains. For promo-driven TLDs especially, a chunk of Q1's spike won't be there in a year. That's the difference between velocity and durability — and it's why the net-adds view and the renewal follow-up matter more than the percentage headline.

FAQ

What was the fastest growing TLD in Q1 2026? By QoQ percentage, .makeup at +4,851.84% (2,309 → 114,338). But by net new registrations, .lol led with +252,177 added domains. The two questions have different answers, which is the whole point — percentage and volume are not the same ranking.

Is .makeup growth real? It's a real spike in registrations, but it's almost certainly promotion- and price-driven, not organic end-user demand. .makeup grew from a tiny ~2,300-domain base, and its registry (XYZ.COM LLC) raised wholesale prices in August 2025, which pulled forward cheap registrations and renewals. Treat it as a price event, and watch the renewal rate before calling it a trend.

How do you measure TLD growth and QoQ domain registration growth? Count new registrations by their created date in each quarter, then compare. We bucket Q1 2026 (Jan–Mar) against Q4 2025 (Oct–Dec) and compute the percentage change, with a minimum-base floor so tiny TLDs don't produce meaningless percentages. Always read net adds alongside the percentage — they answer different questions.

Which fastest-growing domain extensions are genuine trends versus promotions? The genuine ones grow at moderate percentages on large bases: .asia, .life, .tech, .one, .link. The promo-pattern ones show huge percentages from tiny bases: .makeup, .garden, .mobile. .lol is the rare extension that's high on both, though much of its volume is cheap, high-churn registration. Browse any extension in the full TLD directory.

Get the data

Everything above came from one pass over one file. The fields it needs — each domain's TLD and its created registration date — live in any webatla dataset that carries registration dates, and the analysis is only as fresh as your data.

Domain Investor dataset → — €299, built around fresh registrations, with tld and created on every domain. The on-theme tool if your job is spotting which TLDs are heating up — pull a fresh export each quarter and you catch the next spike first.
Websites + Ranking → — €99, also carries created and tld (plus a popularity rank), if you want the same time-series at a lower entry price.
All Data → — €599, the full field set (WHOIS/RDAP dates, DNS, tech stack, ranking) if you want to slice growth by registrar, host or technology too.

Browse the full dataset catalogue and pricing, or learn the basics first with our guide on how to download a list of all active domains. Then do exactly what I did: bucket by registration date, group by TLD, and read the base column before you call anything a trend.

How to Download a List of All Active Domains in 2026

2026-03-23T16:28:00.000Z

Looking for a complete list of all active domains — every registered domain name on the internet, in one structured file? Whether you're building a sales pipeline, running security research, training a model, or sizing a market, the hard part is rarely the analysis. It's getting clean, current, machine-readable data in the first place.

This guide walks through the realistic options in 2026, what "active" actually means, and how to download the full set as fresh JSONL.

What counts as an "active" domain?

A domain is active when it's registered in a registry and resolvable — it exists in a TLD's zone and usually has DNS records pointing somewhere. That's different from:

Parked domains — registered but not serving a real site.
Expired or pending-delete domains — no longer registered.
Subdomains — blog.example.com is not a separate registration; example.com is.

When people ask for "all domains," they almost always mean every registered second-level domain across every TLD — example.com, example.org, example.de, and so on. There are hundreds of millions of them spread across thousands of TLDs.

Three ways to get the data

1. TLD zone files

ICANN's Centralized Zone Data Service (CZDS) lets you request zone files for most gTLDs. A zone file lists the domains in a TLD along with their nameservers.

Pros: authoritative and free. Cons: you have to apply per-TLD and get approved, most ccTLDs (.de, .uk, .fr, …) don't publish zones at all, and you only get the domain plus NS records — no technologies, no ranking, no registration data. You're also left merging hundreds of files in different states of freshness.

2. Registrar or registry exports

Some registries sell or publish lists. Coverage is inconsistent, formats vary, ccTLD policies differ wildly, and you rarely get anything beyond the bare domain. Stitching global coverage together this way is a project in itself.

3. A ready-made domain dataset

The pragmatic option is to download a dataset that has already handled the collection, de-duplication, and enrichment. That's exactly what the All Active Domains dataset is: one downloadable file covering every active domain we observe across all TLDs, refreshed daily.

What's inside the All Active Domains dataset

Each line is one domain, with the fields you need to filter and segment:

Field	Example	Use
`domain`	`example.com`	the registration itself
`tld`	`com`	filter by TLD
`created` / `updated`	`2014-03-09`	age, freshness, newly-registered filters
`ns`	`ns1.cloudflare.com`	DNS provider and hosting clusters
`status`	`active`	resolvable vs parked

Need more than the list itself? Layer on the Technologies dataset to see what each site runs, or RDAP & WHOIS for registration details.

Why JSONL?

Every webatla dataset ships as JSONL — one JSON object per line. It's the format that scales:

Streamable — process it line by line without loading the whole file into memory.
Tool-friendly — works out of the box with jq, pandas, DuckDB, BigQuery, and Spark.
Schema-stable — new fields can be added without breaking your parser.

Count domains per TLD with nothing but jq:

cat all-active-domains.jsonl | jq -r .tld | sort | uniq -c | sort -rn | head

Or query it directly in DuckDB:

SELECT tld, count(*) AS domains
FROM 'all-active-domains.jsonl'
GROUP BY tld
ORDER BY domains DESC;

How fresh is the data?

Domains are registered and dropped every minute, so a six-month-old list is mostly noise. Our exports are rebuilt daily and every download is versioned by date, so you always know exactly what you have. Newly registered domains are where most of the value sits — they signal new businesses, product launches, and campaigns before anyone else notices.

Frequently asked questions

How many active domains are there? Hundreds of millions across all TLDs combined, and the number moves every day. The dataset reflects the current resolvable set — not a stale historical dump.

Can I get only new domains? Yes. Filter by created date to isolate newly-registered domains, or start from the Domain Investor dataset, which focuses on fresh registrations.

Isn't scraping WHOIS a faster route? No. WHOIS — now RDAP — returns registration details for domains you already know about. It won't enumerate the full namespace, and rate limits make bulk lookups slow.

What does it cost? One flat price for a month of downloads, with no subscription. See pricing.

Get the full list

Skip the zone-file paperwork and the half-finished scrapers. Download the All Active Domains dataset → and have every active domain as clean JSONL today, or browse all datasets to see what you can layer on top.

webatla Blog

Websites Created Using Wix: 4.9M Live (2026)

What Wix actually is

How many websites are created using Wix?

What the domain endings say

What kinds of sites are built on Wix

Where webatla geolocates Wix sites — read this carefully

Who uses Wix — the builder in context

Trends: the year-over-year number is an index recount

How to see the list of websites using Wix

Get the full list of websites created using Wix

FAQ

Websites Made With Shopify: 2.85M Live Stores (2026)

What Shopify actually is

How many websites are made with Shopify?

What the domain endings say

Where webatla geolocates Shopify sites — read this carefully

Who builds on Shopify

Shopify in the wider commerce picture

Trends: the year-over-year number is an index recount

How to see the list of websites using Shopify

Get the full list of websites made with Shopify

FAQ

Websites That Use Cloudflare: 54.4M Live (2026)

What Cloudflare actually is

Websites that use Cloudflare vs the rest of the CDN market

What the domain endings say

Who puts Cloudflare in front of their site

Where webatla geolocates Cloudflare sites — read this carefully

Cloudflare and the wider delivery layer

Trends: the number that barely moved

How to see the list of websites using Cloudflare

Get the full list of websites that use Cloudflare

FAQ

Websites created using WordPress: 23.6M Live (July 2026)

What WordPress actually is

How many websites are created using WordPress?

Who builds sites with WordPress — the plugin and theme layer

What kinds of sites are built with WordPress

Where websites made by WordPress live

Versions: half the web runs one release

Trends: read the year-over-year number carefully

How to see the list of websites using WordPress

Get the full list of websites created using WordPress

How to Download all DNS Records

What is a DNS record?

The records that do the heavy lifting

Why you cannot pull every DNS record yourself

How webatla collects every record

Every DNS record, in one file

What each line looks like

How to work with the file

What a full DNS dataset unlocks

Always fresh, never a one-time dump

Frequently asked questions

Download every DNS record

How to download list of all registered domains

How big is a list of all registered domains?

The .com question everyone starts with

Why you cannot assemble it yourself

What makes it a complete, usable set

The whole set, in one file

What each line looks like

Working with a file this large

Who relies on a complete domains set

The real cost of an incomplete list

From file to first answer in minutes

Always current, never stale

Frequently asked questions

Download the full list

Who Controls the Internet's Plumbing? DNS and Registrar Market Share in 2026

How concentrated is DNS?

Why DNS concentration is systemic risk

Domain registrar market share 2026: the leaderboard, and what it hides

What the raw leaderboard hides: shell entities

Brand-protection vs mass-market registrars

The oldest domains on the internet

An honesty caveat on the dates

Methodology

FAQ