Download websites that use EmailJS

About EmailJS

Sending an email normally requires a server. EmailJS exists to remove that requirement, and the way it does so is what makes its presence on a site informative. Published by EmailJS as a Proprietary service since 2016, the library is JavaScript running in the visitor's own browser, handing a message to the vendor's API, which relays it through whichever mail provider the site owner has connected. No backend belonging to the site is involved at any point.

A site using it is therefore, in most cases, a site with no backend at all. Static sites, single page applications, documentation portals, agency landing pages and portfolios all reach the moment where a contact form has to go somewhere, and standing up a server to deliver one message is out of proportion to the need. We file the service under Email, though everyday use is far more mundane than campaign sending: contact forms, notification hooks and feedback widgets.

As of October 2026 we detect EmailJS on 10,626 sites, 5,491 of which resolve to United States, with the domains concentrated under .com. A distribution like that follows the tooling rather than any market. The static site generators, hosting platforms and starter templates that make a backendless build easy are documented in English and default to generic domains, and the library travels inside those templates.

Version data is unusually meaningful for a client-side script. We record 23 distinct versions in the field, and the release we encounter most often is 4. A script reference is pinned in the page source, sometimes copied from a tutorial written years earlier, so old versions persist until somebody edits the markup by hand. The spread across those versions is a fairly direct measurement of how rarely small static sites are revisited after launch.

There is a security dimension too, and it affects who wants this list. Sending from the browser means the account identifier the library uses is visible in the page to anyone who looks. The vendor mitigates that with domain restrictions and rate limits, but the exposure is structural rather than a misconfiguration, so a population of sites using the service is a population sharing a particular class of surface. Researchers studying credential exposure or the abuse of relay services want the full set for that reason.

A per-domain lookup answers whether one site uses the service. A full list answers who has built without a backend, at what scale, in which countries and on which versions, which is the question that matters to competing form and mail services, to hosting platforms sizing the static site market, and to anyone measuring how the removal of servers reshaped small websites. Detection reads the script or module reference in the served page, so a site that compiles the library into a bundle under another filename can be missed, and the count should be read as a floor.