<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: webatla</title>
    <description>The latest articles on DEV Community by webatla (@webatla).</description>
    <link>https://dev.to/webatla</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3669183%2F63b6b712-10bd-4aad-b932-fd84503b1ca8.png</url>
      <title>DEV Community: webatla</title>
      <link>https://dev.to/webatla</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/webatla"/>
    <language>en</language>
    <item>
      <title>How Many Websites Use React? 11.05M Sites and What a Scanner Can Actually See</title>
      <dc:creator>webatla</dc:creator>
      <pubDate>Thu, 19 Nov 2026 10:51:12 +0000</pubDate>
      <link>https://dev.to/webatla/how-many-websites-use-react-1105m-sites-and-what-a-scanner-can-actually-see-166n</link>
      <guid>https://dev.to/webatla/how-many-websites-use-react-1105m-sites-and-what-a-scanner-can-actually-see-166n</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbay3n8s4x1j27mgh8fwu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbay3n8s4x1j27mgh8fwu.png" alt=" " width="800" height="336"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As of November 16, 2026, webatla counts 11,053,868 websites running React, 3.39% of the 325.8 million websites it tracks. The scan finds a version string on only about 4,500 of them.&lt;/p&gt;

&lt;p&gt;Any answer to how many websites use React depends on what a scanner can observe in a React site, and that is worth understanding if you write or maintain React code. The live number sits on &lt;a href="https://webatla.com/technology/react" rel="noopener noreferrer"&gt;webatla's React technology page&lt;/a&gt;. The history tables and the full framework comparison are in the &lt;a href="https://webatla.com/blog/react-statistics" rel="noopener noreferrer"&gt;React statistics article&lt;/a&gt; on the webatla blog.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a scanner can and cannot see in a React build
&lt;/h2&gt;

&lt;p&gt;React renders in the browser and, in many setups, on the server as well. Either way the browser receives HTML plus JavaScript files, and React's client code takes over the page once they load. A CMS usually leaves fixed paths in the markup, and a web server often names itself in a response header. React leaves neither. Its presence has to be inferred from the JavaScript a site ships.&lt;/p&gt;

&lt;p&gt;webatla's React page is direct about what that means. It finds React where a site exposes it through recognizable build output or development artifacts. A bundle compiled tightly enough leaves no reliable trace, and such sites stay out of the file. Two rules follow for anyone reading the number.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A detection is strong evidence that React is there.&lt;/li&gt;
&lt;li&gt;A missing detection is weak evidence that it is not.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So 11,053,868 is a floor. The page also says the detected population leans toward sites built with default tooling, since aggressive optimization pipelines are exactly what hides the library.&lt;/p&gt;

&lt;p&gt;There is a timing detail too, and it matters when you look at single rows. Each row carries the date its technologies were last checked. On the five preview rows of the React page those dates run from October 17 to November 11, 2026, while the file itself is dated November 16. A row describes what the scan saw on its check date. If a team shipped a rewrite last week, its row can still show the old stack.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdurv5t1zdn4hldy1wfcr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdurv5t1zdn4hldy1wfcr.png" alt="Three numbers in a row: 11,053,868 sites with React detected, about 4,500 showing any version string, 1,503 sites with a string that follows React's numbering" width="800" height="321"&gt;&lt;/a&gt;&lt;/p&gt;
Of 11,053,868 React detections, about 4,500 come with a version string, and 1,503 of those sites show a common value that follows React's own numbering.



&lt;h2&gt;
  
  
  Two checks you can run on any site
&lt;/h2&gt;

&lt;p&gt;If you want to know whether one particular site runs React, you do not need a scanner. Two quick signals are enough to look for yourself.&lt;/p&gt;

&lt;p&gt;The first is a header check, and it mostly teaches you where React is &lt;em&gt;not&lt;/em&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -sIL https://example.com &lt;span class="o"&gt;|&lt;/span&gt; grep -iE &lt;span class="s1"&gt;'^(server|x-powered-by):'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;-L&lt;/code&gt; flag follows redirects and prints the headers of every hop, so read the last block. React sets no response header of its own, even when it renders on the server, so no header names it. You will often see a server name, and sometimes the framework wrapped around React. A Next.js server, for example, sends &lt;code&gt;X-Powered-By: Next.js&lt;/code&gt; unless the team switched that header off. React itself never shows up there.&lt;/p&gt;

&lt;p&gt;The second check runs in the browser. Open the site, open DevTools and paste this into the console.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// React keeps internal references on the DOM elements it manages.&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;managed&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelectorAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'*'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;el&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt;
  &lt;span class="nb"&gt;Object&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;keys&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;el&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;some&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;k&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;k&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;startsWith&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'__reactFiber$'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;k&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;startsWith&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'__reactInternalInstance$'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Elements managed by React:'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;managed&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Global React version:'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;window&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;React&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;version&lt;/span&gt; &lt;span class="o"&gt;??&lt;/span&gt; &lt;span class="s1"&gt;'not exposed'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nb"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'data-reactid elements (React 15 or older):'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelectorAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'[data-reactid]'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;React 17 and later attach a property starting with &lt;code&gt;__reactFiber$&lt;/code&gt; to the DOM elements they render or hydrate. React 15 and 16 used &lt;code&gt;__reactInternalInstance$&lt;/code&gt;. Older versions wrote &lt;code&gt;data-reactid&lt;/code&gt; attributes into the markup. A non-zero count is close to proof. The version line only prints a number when React was loaded as a global script, which modern bundled apps rarely do. The React Developer Tools extension gives the same answer with less typing, because its icon lights up on pages that use React.&lt;/p&gt;

&lt;p&gt;A zero from this snippet has the same weakness as a miss in the scan. A page that mounts React only after a click, or renders it inside an iframe, can come back empty.&lt;/p&gt;

&lt;h2&gt;
  
  
  Version strings: about 4,500 sites out of 11 million
&lt;/h2&gt;

&lt;p&gt;The React page lists the most common version values found next to React. Only about 4,500 React sites come with any version string at all, 0.04% of the count. The version number usually sits as plain text somewhere inside the minified bundle, so the gap says more about what a scan records than about what a site hides.&lt;/p&gt;

&lt;p&gt;The values themselves need a sanity check before anyone counts them. React's version numbers ran from 0.x up to 0.14 and then jumped to 15, followed by 16, 17, 18 and 19. There was never a React 1.x or 6.x. That rules out a large part of the list.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;19627.0 is the most common value of all, on 1,874 sites.&lt;/li&gt;
&lt;li&gt;33058.93, 74932.10647, 1.4.2, 0.0.2, 6.3.8, 6.5.8 and 2.14.9 follow further down.&lt;/li&gt;
&lt;li&gt;18.3.24, on 41 sites, looks like a React 18 release, but the 18.3 line only ever had 18.3.0 and 18.3.1.&lt;/li&gt;
&lt;li&gt;Together these nine strings cover 2,680 sites, more than half of the rows with a version.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The public page does not say where those strings come from. The lesson applies to any scanner output: validate version fields against the real release history before you build a chart on them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37lmuccoz02f6i0j0rul.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37lmuccoz02f6i0j0rul.png" alt="Lollipop chart of React version strings by release line: 19.x 141 sites, 18.x 956, 17.x 53, 15.x 218, 0.12 to 0.14 135, and 2,680 sites with strings outside React numbering" width="800" height="498"&gt;&lt;/a&gt;&lt;/p&gt;
Within the 25 most common version values, 18.x leads with 956 sites, while 2,680 sites carry strings that React never used as release numbers.



&lt;p&gt;Grouped by the major number in the string, the plausible values split like this.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Release line&lt;/th&gt;
&lt;th&gt;Sites&lt;/th&gt;
&lt;th&gt;Share of the 1,503&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;19.x&lt;/td&gt;
&lt;td&gt;141&lt;/td&gt;
&lt;td&gt;9.4%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;18.x&lt;/td&gt;
&lt;td&gt;956&lt;/td&gt;
&lt;td&gt;63.6%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;17.x&lt;/td&gt;
&lt;td&gt;53&lt;/td&gt;
&lt;td&gt;3.5%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;15.x&lt;/td&gt;
&lt;td&gt;218&lt;/td&gt;
&lt;td&gt;14.5%&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;0.12 to 0.14&lt;/td&gt;
&lt;td&gt;135&lt;/td&gt;
&lt;td&gt;9.0%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;No 16.x value made the top 25. For maintainers the interesting rows sit at the bottom of the table. Builds from React 15 and the 0.x line add up to 353 sites, more than twice the 141 sites with 19.x strings. Moving such a site to current React is a long trip. &lt;code&gt;React.createClass&lt;/code&gt; and &lt;code&gt;React.PropTypes&lt;/code&gt; left the core package in React 16, and &lt;code&gt;ReactDOM.render&lt;/code&gt;, the classic way to mount an app, is gone in React 19. For a 0.13.3 or 15.6.1 build that looks more like a rebuild than a version bump.&lt;/p&gt;

&lt;p&gt;Keep the scale in mind. These are a few hundred sites that happen to show a version, out of 11 million. They prove that old builds are still online, but not what share of all React sites runs old code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why sites leave the React count
&lt;/h2&gt;

&lt;p&gt;Over the last 12 months 3.99 million sites came into the React count in webatla's history model and 2.78 million left, which works out to about 7,600 departures a day. The React page splits those departures in two.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Dropped it.&lt;/strong&gt; The site is still online, but the scan no longer finds React there. 1.04 million sites.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shut down.&lt;/strong&gt; The site itself went offline. 1.74 million sites.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The history model gives the same split for every year. The chart divides each kind of exit by the React count at the start of that year.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo698nqgk9pnqpd49q7uc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo698nqgk9pnqpd49q7uc.png" alt="Dumbbell chart by year from 2016 to 2025 comparing the share of React sites that removed React while staying online with the share that shut down, as a percentage of the start-of-year count" width="800" height="599"&gt;&lt;/a&gt;&lt;/p&gt;
Sites removing React stayed between 6.3% and 8.5% of the start-of-year count from 2022 to 2025, while shutdowns rose from 7.8% to 15.6%.



&lt;p&gt;From 2022 to 2025 the share of sites that removed React moved only between 6.3% and 8.5% a year. Shutdowns climbed from 7.8% to 15.6% over the same years. In the first ten months of 2026 shutdowns already reached 14.6% of the count at the start of the year, and removals 9.1%. Over the last 12 months 1.04 million sites removed React out of 9.84 million at the end of October 2025, about 10.6%, which is above every year from 2022 to 2025. The high removal rates of 2018 and 2021 come with single months of very large drops (June and September 2018, July 2021), which may be a measurement effect rather than a wave of rewrites. Early years of the model are approximate.&lt;/p&gt;

&lt;p&gt;So the growing number of exits is mostly sites going offline. When a React site drops out of the count, the usual story is a project that ended. A team pulling React out of a live product is the smaller group. Even that group is not all real migrations. A "dropped it" row can also be a site whose new build no longer exposes React to the scan, and the public pages cannot tell the two apart.&lt;/p&gt;

&lt;h2&gt;
  
  
  Are existing sites moving away from React?
&lt;/h2&gt;

&lt;p&gt;Switching is the better measure of developer preference. A switch is an existing site that adds or removes a technology while it stays online. Over the last 12 months 1.16 million existing sites added React and 1.04 million removed it. Summed from the monthly rows, the balance is about 126,000, or 1.3 for every 100 sites React had at the end of October 2025.&lt;/p&gt;

&lt;p&gt;The same arithmetic works for any framework. The chart applies it to React's three direct rivals (Vue.js, Angular and Svelte) and four older libraries (AngularJS, Backbone.js, Prototype and jQuery). Tools built on React, such as Next.js, are left out, since their own webatla pages tie them to React.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsmek9knov18gl8acyztz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsmek9knov18gl8acyztz.png" alt="Diverging lollipop chart of switching balance per 100 sites over the last 12 months: Svelte plus 21.4, Angular plus 9.2, React plus 1.3, Vue.js plus 0.3, jQuery minus 3.3, Prototype minus 6.9, AngularJS minus 10.5, Backbone.js minus 11.5" width="800" height="573"&gt;&lt;/a&gt;&lt;/p&gt;
Switched to it minus dropped it over the last 12 months, per 100 sites at the end of October 2025. All four older libraries lost existing sites.



&lt;p&gt;The older libraries all lose existing sites on balance: Backbone.js 11.5 per 100, AngularJS 10.5, Prototype 6.9 and jQuery 3.3. React gains a little. Vue.js sits close to zero, with 529,000 sites switching to it and 524,000 dropping it.&lt;/p&gt;

&lt;p&gt;Svelte and Angular post the largest positive rates, but on small bases. Svelte's +21.4 per 100 is about 11,900 sites, roughly a tenth of React's balance in absolute terms. Angular's +9.2 is about 13,000. Today's files count Vue.js on 2,061,594 sites, Angular on 156,514 and Svelte on 84,502. React alone holds 46.3% of the detections in webatla's JavaScript frameworks category (React market share across 54 technologies, where a site with two frameworks counts once for each), so its modest rate still adds more existing sites than any other framework in the chart.&lt;/p&gt;

&lt;p&gt;Both directions are large for every framework in the chart. Some of that back and forth may be measurement, such as a site whose build changed between two checks. The balance is the steadier number to quote.&lt;/p&gt;

&lt;p&gt;Existing React sites are not leaving on net. The libraries losing existing sites are the ones that came before React.&lt;/p&gt;

&lt;h2&gt;
  
  
  Domain extension or server country: two different questions
&lt;/h2&gt;

&lt;p&gt;Every row in the React file has two location fields, and they answer different questions. Country is where the server is, found by IP address. The domain extension is where the owner chose to register. For React sites the two disagree a lot.&lt;/p&gt;

&lt;p&gt;89.1% of React sites with a known server country sit on US servers, 9,671,733 of them. Put each country's domain extension next to the React sites hosted inside that country and the gap becomes visible.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fop5ahqlojznaojv3l3rp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fop5ahqlojznaojv3l3rp.png" alt="Dumbbell chart comparing React sites hosted in a country with React sites on that country's domain extension, for the UK, Australia, Brazil, Canada, France, India, Russia, Germany and the Netherlands" width="800" height="577"&gt;&lt;/a&gt;&lt;/p&gt;
React sites under .uk outnumber React sites on UK servers 431,186 to 18,579. Germany and the Netherlands host more React sites than their own extensions hold.



&lt;p&gt;The .uk extension holds 431,186 React sites, while UK servers host 18,579, about 23 to 1. Australia (.au, 167,920 against 11,876) and Brazil (.br, 237,447 against 19,040) come out at about 14 to 1 and 12 to 1. Germany and the Netherlands run the other way. German servers host 417,973 React sites against 269,953 under .de, and Dutch servers 193,845 against 75,980 under .nl. So German and Dutch servers carry many React sites under .com and other extensions.&lt;/p&gt;

&lt;p&gt;The most likely reason for the pull toward US servers is platform hosting. A site builder or front-end cloud serves its customers from its own infrastructure, wherever the customer lives. &lt;a href="https://webatla.com/technology/wix" rel="noopener noreferrer"&gt;Wix&lt;/a&gt; fits that pattern, with React in all five of its sample rows and 99.4% of its sites on US servers. A sizable share of the 11 million React sites are therefore likely builder pages whose owners never wrote a line of React.&lt;/p&gt;

&lt;p&gt;For your own queries this means picking the field that matches the question. Looking for React sites aimed at British users? Filter by extension. Counting React sites served from EU servers, for latency or data residency? Filter by country. The two filters return very different lists.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the numbers mean if you build or maintain React apps
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The count is bigger than the number of React codebases.&lt;/strong&gt; One team can run React on many domains, and builder pages likely add a share of rows that need no React developer. The public pages give no exact overlap, so how many separate React projects sit behind the 11 million stays unmeasured.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The base keeps growing, with heavy turnover.&lt;/strong&gt; React usage statistics on the technology page show +35% from October 2023 to October 2026 and +12% over the last 12 months. In October 2026 alone the history model has 285,000 sites coming in and 171,000 leaving, so any saved list of React sites ages quickly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exits are mostly shutdowns.&lt;/strong&gt; Removal rates stayed in a narrow band from 2022 to 2025 and rose in 2026, but switch-ins still outweigh removals. Nothing in the data looks like a rush away from React.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Old builds are still online.&lt;/strong&gt; The visible version strings include hundreds of sites on 15.x and 0.x code. If you inherit one of them, plan for a rebuild.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Single-site answers need a direct check.&lt;/strong&gt; A row reflects one check date and one view of the shipped code. When it matters, run the console snippet above.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Quick answers for developers
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Do 11 million React sites mean 11 million React projects?
&lt;/h3&gt;

&lt;p&gt;No. The count is one row per domain where React was detected. Site builders that ship React for their customers likely add many of those rows, and one team can run React on many domains.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I tell which React version a site runs?
&lt;/h3&gt;

&lt;p&gt;Sometimes. &lt;code&gt;window.React.version&lt;/code&gt; works only when React loads as a global script. With the React Developer Tools extension installed, the renderer reports its version to the extension, so the version is often readable on a site you check by hand. In webatla's data about 4,500 React sites expose any version string, and many of those strings are not React release numbers.&lt;/p&gt;

&lt;h3&gt;
  
  
  Are sites leaving React for Vue.js or Svelte?
&lt;/h3&gt;

&lt;p&gt;Not on net. Over the last 12 months 1.16 million existing sites added React and 1.04 million removed it. Svelte and Angular gained existing sites faster in relative terms, but from bases a fraction of React's size.&lt;/p&gt;

&lt;h3&gt;
  
  
  How fresh is the count?
&lt;/h3&gt;

&lt;p&gt;The technology page is rebuilt every day. Individual rows carry their own last-checked date, so a single site's entry can be a few weeks older than the file.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://webatla.com/blog/react-statistics" rel="noopener noreferrer"&gt;React Statistics 2026: How Many Websites Use React?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/blog/jquery-statistics" rel="noopener noreferrer"&gt;jQuery Statistics 2026: How Many Websites Use jQuery?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/blog/websites-created-using-wix" rel="noopener noreferrer"&gt;Wix Statistics 2026: How Many Websites Use Wix?&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>react</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>frontend</category>
    </item>
    <item>
      <title>Domain Database Download: Where to Get a Complete List of Domains (Fast, Reliable, and Ready to Use)</title>
      <dc:creator>webatla</dc:creator>
      <pubDate>Mon, 16 Mar 2026 15:44:35 +0000</pubDate>
      <link>https://dev.to/webatla/domain-database-download-where-to-get-a-complete-list-of-domains-fast-reliable-and-ready-to-use-129a</link>
      <guid>https://dev.to/webatla/domain-database-download-where-to-get-a-complete-list-of-domains-fast-reliable-and-ready-to-use-129a</guid>
      <description>&lt;p&gt;Companies don’t just want a few domains—they want the whole picture.&lt;/p&gt;

&lt;p&gt;Whether you’re hunting for phishing campaigns, building a lead list, or modeling a market, you quickly discover the internet’s biggest truth: the domain namespace is enormous, constantly changing, and split across thousands of registries. That’s why “domain database download” is such a high-intent search query. Teams need a trustworthy, up-to-date dataset they can integrate into their workflows without wasting engineering time.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a Domain Database?
&lt;/h2&gt;

&lt;p&gt;A domain database is a structured dataset that catalogs registered domain names and their metadata across top-level domains (TLDs). Depending on the provider, it may include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Core domain lists&lt;/strong&gt;: domain name, TLD, and sometimes related identifiers like registrar and nameservers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WHOIS records&lt;/strong&gt;: registration details (registrar, status, creation/expiration dates, and sometimes registrant/organization info—where not protected by privacy proxies).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RDAP data&lt;/strong&gt;: standardized registration data including events and relationships, often used as a modern replacement for WHOIS.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DNS context&lt;/strong&gt;: nameserver history and other signals that can support cybersecurity and research use cases.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Because WHOIS and RDAP are not uniform across registries, the value of a domain dataset is heavily influenced by how consistent, clean, and current it is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Companies Download Domain Databases
&lt;/h2&gt;

&lt;p&gt;If you’re searching for a domain database download, you’re likely trying to solve one of these problems with real data:&lt;/p&gt;

&lt;h3&gt;
  
  
  Lead generation (sales)
&lt;/h3&gt;

&lt;p&gt;A complete domain list is a gold mine for prospecting. Sales and growth teams enrich domains with company info, then prioritize outreach by industry or geography.&lt;/p&gt;

&lt;h3&gt;
  
  
  Cybersecurity
&lt;/h3&gt;

&lt;p&gt;Security teams use domain datasets to discover suspicious registrations, monitor emerging infrastructure, and correlate domains across campaigns. Alerts like “new domains containing our brand string” start with a broad domain database download that narrows over time.&lt;/p&gt;

&lt;h3&gt;
  
  
  Brand protection
&lt;/h3&gt;

&lt;p&gt;Legal and brand teams watch for typosquats, impersonation, or fraud. They run discovery across TLDs and analyze patterns in registrant behavior, use of privacy protection, and hosting relationships.&lt;/p&gt;

&lt;h3&gt;
  
  
  Market research
&lt;/h3&gt;

&lt;p&gt;Analysts use domain datasets to understand market penetration (e.g., ecommerce domain volume by country), track trends across TLDs, or study adoption of new technologies by analyzing DNS and registration characteristics.&lt;/p&gt;

&lt;h3&gt;
  
  
  Domain investment
&lt;/h3&gt;

&lt;p&gt;Investors want to identify undervalued names, monitor drops, and track portfolio performance. They often build models that depend on broad historical snapshots plus daily deltas.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where to Download Domain Databases
&lt;/h2&gt;

&lt;p&gt;There’s no single “download domain list” button for the entire internet—but there are a handful of common sources, each with trade-offs.&lt;/p&gt;

&lt;h3&gt;
  
  
  1) Zone files
&lt;/h3&gt;

&lt;p&gt;Some registries provide zone files that list the domains currently delegated for a TLD. Zone files are useful, but they may omit recently registered domains that aren’t delegated yet, and they often lack rich metadata. They also require manual access approvals and ongoing maintenance.&lt;/p&gt;

&lt;h3&gt;
  
  
  2) Registries
&lt;/h3&gt;

&lt;p&gt;Different country-code and generic TLD registries offer different levels of access, licensing, and timeliness. Working directly with multiple registries can become operationally heavy—especially when you want consistent coverage across dozens or hundreds of TLDs.&lt;/p&gt;

&lt;h3&gt;
  
  
  3) Commercial datasets
&lt;/h3&gt;

&lt;p&gt;Commercial providers assemble domain datasets from many sources, add normalization and enrichment, and deliver them as downloadable files. This is often the fastest path to value because it removes the “plumbing” work required to combine WHOIS/RDAP and DNS inputs.&lt;/p&gt;

&lt;h3&gt;
  
  
  4) APIs
&lt;/h3&gt;

&lt;p&gt;APIs can be great for a small subset of domains, but when you need a full domain database download (or daily deltas), rate limits and request overhead can become a bottleneck. The best approach depends on your pipeline: small teams prefer file downloads; platform teams may mix downloads with APIs for on-demand lookups.&lt;/p&gt;

&lt;h2&gt;
  
  
  Challenges of Building Your Own Domain Dataset
&lt;/h2&gt;

&lt;p&gt;It’s tempting to build everything in-house, but a complete domain database download is more than a big file. It’s a distributed data engineering problem.&lt;/p&gt;

&lt;p&gt;Here are the most common pitfalls:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Crawling and coverage&lt;/strong&gt;: RDAP endpoints vary by registry, and some are slow or unreliable. You need retry logic, adaptive scheduling, and careful compliance with robots/rate limits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Normalization&lt;/strong&gt;: Each registry formats data differently. Without consistent normalization, joins become messy and downstream analytics become noisy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Daily updates&lt;/strong&gt;: Domains churn constantly—new registrations, expirations, transfers. If you’re not updating daily, your dataset goes stale and your outputs become inaccurate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Infrastructure cost&lt;/strong&gt;: Maintaining a pipeline that can ingest millions of records reliably (and compactly) is expensive, and easy to underestimate.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Webatla Domain Datasets
&lt;/h2&gt;

&lt;p&gt;Webatla is designed specifically for teams that need domain intelligence with minimal friction. Instead of stitching together multiple sources yourself, Webatla provides downloadable domain datasets with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Global coverage&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Daily updates&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Structured data&lt;/strong&gt; across WHOIS, RDAP, and TLD domain coverage&lt;/li&gt;
&lt;li&gt;Delivery as downloadable files (easy to ingest into data warehouses, SIEM pipelines, CRM enrichment, or research notebooks)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Explore the product pages for specifics:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://webatla.com/" rel="noopener noreferrer"&gt;domain database&lt;/a&gt; (start here if you want a broad “download domain database” option)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/tld/" rel="noopener noreferrer"&gt;TLD domain list&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/countries/" rel="noopener noreferrer"&gt;country breakdowns&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/whois-database/" rel="noopener noreferrer"&gt;WHOIS database download&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://webatla.com/rdap-database/" rel="noopener noreferrer"&gt;RDAP database&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How to Download Domain Data from Webatla
&lt;/h2&gt;

&lt;p&gt;Downloading domain data should be simple—and it is with Webatla. The general workflow looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Choose your dataset&lt;/strong&gt;: global domain lists, WHOIS records, RDAP data, a TLD-specific slice, or a country-specific slice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick your format&lt;/strong&gt;: Webatla datasets are delivered as downloadable files suitable for ingestion.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Integrate&lt;/strong&gt;: load the domain datasets into your analytics stack, enrichment pipeline, or security monitoring tooling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repeat daily&lt;/strong&gt;: because the Webatla dataset is updated daily, you can keep your internal models fresh without rebuilding your pipeline.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;A domain database download isn’t just about convenience—it’s about competitive advantage. The teams who consistently ship the best detection models, build the cleanest enrichment, and prospect efficiently are the teams with the best domain datasets.&lt;/p&gt;

&lt;p&gt;If you need a complete, reliable &lt;strong&gt;domain database download&lt;/strong&gt; with daily updates and structured metadata, start with Webatla’s domain intelligence datasets. Your analysts (and your pipeline) will thank you.&lt;/p&gt;

</description>
      <category>domain</category>
      <category>datasets</category>
      <category>seo</category>
      <category>cybersecurity</category>
    </item>
  </channel>
</rss>
