Your Domain Extension Predicts Your Tech Stack — And .ai Is the Extreme Case

A rank-based cut of a tech-stack census tells you who can afford what. A TLD-based cut tells you something different: what a domain extension actually signals about the site behind it — and for one extension in particular, the signal is almost absolute. Split our 1,000,000-domain census by TLD instead of by Tranco rank, and .ai domains stand alone.

The AI land rush has a tech-stack signature

.ai33.1%

.io17.4%

.app16.8%

.dev16.6%

.com5.3%

Almost one in three reachable .ai domains runs Next.js — more than 6x .com's rate, and nearly double .io's. That gap is the headline, but the shape underneath it is the more interesting finding: .io, .app, and .dev — the three extensions with the strongest existing reputation as "the startup/developer TLDs" — land within a single point of each other, all close to 17%. If general startup culture were driving the Next.js number, you'd expect all four non-.com extensions to cluster together. They don't. .ai is out on its own, which points to something narrower than "startups prefer modern TLDs" — the 2024-2026 AI-product land rush specifically, where a wave of freshly built product sites all reached for the same default modern stack at the same time.

Ruling out the obvious objection

A fair challenge to the number above: is .ai just full of low-traffic vanity domains that happen to squeak into a top-1,000,000 census, inflating a percentage that doesn't mean much? The data says no, on three separate counts.

.ai domains average more traffic than .com domains do, not less — and they run the heaviest detected tech stack of any TLD in this comparison, not the lightest. Neither is what a "pile of parked vanity domains" would look like.

.dev58.2%

.ai49.2%

.io42.4%

.app38.5%

.com26.4%

The third count: .ai sites running Next.js are nearly twice as likely to actually be deployed on Vercel — Next.js's own creator and most natural hosting home — as .com sites are (49.2% vs. 26.4%). That's the signature of "spin up a product, hit deploy," not a framework name mentioned somewhere deep in a legacy site's bundle. And it isn't a hidden ecommerce story either: .com runs Shopify or WooCommerce on 9.3% of its reachable sites, while every TLD in this piece sits at 1.4-2.5% — .ai, .io, .app, and .dev are SaaS/product-skewed namespaces, not commerce ones, full stop.

.ai domains are also just... more alive

.ai93.4%

.com87.0%

.app82.2%

.io78.1%

.dev70.9%

A second, smaller signal sits right next to the first: .ai doesn't just skew toward the newest frameworks, it skews toward actually being alive. 93.4% of registered .ai domains resolve a working homepage — the highest reachable rate of any TLD in this comparison, ahead even of .com's 87.0%. The likely mechanism is age, not quality: .ai is a namespace that's almost entirely been registered in the last few years, so it hasn't yet accumulated the decades of expired, parked, and squatted domains that quietly drag down an older extension's reachable rate. .dev, by contrast, is the least reachable of the five at 70.9% — read that as a genuine open question rather than a settled explanation; it may reflect more personal/experimental registrations that get abandoned, Google's stricter HTTPS requirements for the .dev namespace interacting with how this census probes a site, or something else entirely. Stated plainly because it's the honest answer, not because it fits the story.

WordPress isn't gone, even here

.com21.2%

.io16.2%

.ai13.9%

.app9.7%

.dev4.4%

It would be a cleaner story if the newest TLDs had abandoned WordPress entirely. They haven't. 13.9% of reachable .ai domains still run WordPress — lower than .com's 21.2%, but far from zero, and actually closer to .io's 16.2% than the Next.js numbers would suggest. Marketing pages, blogs, and docs sites bolted onto an otherwise modern product are common enough that even the most AI-native domain extension isn't a clean sweep for the newest stack. Keep both numbers in view: .ai is the strongest Next.js signal in this census by a wide margin, and it still isn't a WordPress-free zone.

Limits, stated plainly

This is a TLD-level cut, not a claim about any individual site — a domain extension is a weak, aggregate signal, not a guarantee. Sample sizes vary a great deal: .dev has only 954 reachable domains in this census against .com's 369,002, so its percentages should be read as directional rather than decimal-precise, the same caution the parent census applies to its own smallest rank band. And as with the rest of this census, this is a homepage-only fingerprint — it reflects what a plain request to / reveals, not what a domain's checkout flow, app backend, or logged-in product actually runs.

Query the full Tech Stack dataset

1,000,000 fingerprinted domains — CDN, CMS, ecommerce, analytics, web server and more — over one REST API, filterable by TLD.

Explore the datasetPricing