How to Find What Email Marketing Platform a Website Uses
Mailchimp, Klaviyo, HubSpot, ConvertKit — email platforms leave form actions and scripts behind. Here is how to detect a site's ESP from its signup form.
To find what email marketing platform a website uses, inspect its newsletter signup form: right-click the form, choose Inspect, and read the action URL — it almost always points straight at the provider. A form posting to a list-manage.com address is Mailchimp; one tied to Klaviyo or HubSpot carries their identifiers. Back this up by watching the DevTools Network tab for the platform's loaded script, such as static.klaviyo.com or js.hs-scripts.com. Together, the form action and the loaded script identify most email service providers (ESPs) in under a minute. This guide covers the fingerprints for the major platforms and where to look when there is no obvious form.
It is a natural companion to how to find out what analytics a website uses and feeds directly into how to build a B2B lead list from a website's tech stack.
Why the email platform is worth detecting
A company's email service provider is one of the most useful technographic signals you can read. For sales — especially if you sell a martech product or a competing email tool — it tells you both the incumbent provider and whether there is a switching opportunity. For competitive research, the ESP reveals how a rival runs newsletters, lifecycle and automation, and roughly how sophisticated their marketing stack is. For partnership and integration scoping, knowing the platform tells you what a prospect already connects to. And combined with other detected tools, the ESP helps build a full picture of a company's marketing maturity. Because email platforms inject forms and scripts into the page, much of this is visible from the outside.
Method 1: inspect the signup form (the best signal)
The single most reliable method is to inspect the newsletter signup form. Scroll to the footer (where signup boxes usually live), right-click the email field or the form, and choose Inspect to open DevTools on that element. Read the enclosing <form> tag's action attribute — the URL the form submits to. This is where the platform reveals itself, because the form has to post the subscriber's email to the provider's servers. A list-manage.com action is Mailchimp; a Klaviyo or HubSpot endpoint names those. The form action is the cleanest signal because it is structurally required — the form cannot work without pointing somewhere, and that somewhere is usually the ESP.
Method 2: watch the Network tab
Some platforms reveal themselves through loaded scripts and through the request that fires on submit. Open DevTools (F12), go to the Network tab, and reload — many ESPs load a tracking or form-rendering script site-wide from a recognisable domain. Then submit the form (a test address is fine on most sites) and watch the request that fires: it goes to the provider's endpoint, naming it even if the form action was obscured. This live view catches popup builders and platforms that inject their forms dynamically, which a static source view can miss. It is also how you catch an ESP that is loaded for tracking even when the visible form is minimal.
Method 3: View Source and hidden fields
A source check is fast for the major tools. View the page source (Ctrl/Cmd + U) and search for the provider domains: list-manage.com, chimpstatic.com, klaviyo.com, hs-scripts.com, convertkit, activehosted.com and so on. While you are there, look at the form's hidden fields, which are often provider-specific. Mailchimp embeds, for example, include a distinctive hidden honeypot field (an anti-bot trap) and u= and id= parameters that identify the account and audience. Klaviyo and HubSpot tag their forms with their own identifiers and data attributes. These structural details corroborate the platform even when the script is loaded indirectly.
The fingerprint table
| Platform | Tell-tale fingerprint |
|---|---|
| Mailchimp | Form action on list-manage.com (u=, id= params), honeypot field, chimpstatic.com script |
| Klaviyo | static.klaviyo.com / klaviyo.js, klaviyo object, Klaviyo form identifiers |
| HubSpot | js.hs-scripts.com, forms.hsforms.com, hs-form markup, HubSpot tracking code |
| ConvertKit | convertkit.com / ck.js, ConvertKit form data attributes |
| ActiveCampaign | activehosted.com form action and tracking script |
| Braze | Braze SDK script and API calls (often app-side messaging) |
| Drip / Omnisend / others | Provider-specific script domain and form endpoint |
A single matching fingerprint is usually enough; the form action plus the loaded script together make it conclusive.
Confirming via the subscribe request and behaviour
If the form action and scripts leave any doubt, the subscribe request itself removes it. With the Network tab open, submit the signup form (a disposable address is fine on most public newsletters) and watch the request that fires: it posts to the provider's endpoint, naming the platform even when the visible markup was generic or proxied through the site's own server. The response and follow-up behaviour corroborate too — a Mailchimp double opt-in shows a "check your inbox to confirm" message and sends a branded confirmation email, while many ecommerce ESPs drop you straight into a welcome flow. You do not need to complete the confirmation to read the request; the outbound POST is enough to identify the endpoint. This live method is the tie-breaker for the awkward cases where a site routes the form through its own /subscribe URL before relaying to the ESP, because the relay or the loaded tracking script still gives the provider away. It is the same Network-tab discipline used across detection: watch what actually fires, not only what the static markup declares.
When there is no obvious newsletter form
Not every site has a visible footer signup. Some collect email only at checkout, behind a gated content download, or during account signup. When there is no newsletter box, inspect whichever form does exist and watch the Network tab as you interact with it — the submit request still reveals the endpoint. You may also find the ESP's tracking script loaded site-wide (for example Klaviyo's onsite tracking on an ecommerce store) even without an obvious form, which identifies the platform on its own. If neither a form nor a provider script is present, the site may handle email entirely server-side or through an integration you cannot see from the front end — in which case detection legitimately comes up empty, and you should say so rather than guess.
A worked example
You want to know how a competitor runs email. You scroll to their footer, right-click the newsletter field and choose Inspect. The enclosing form's action posts to a list-manage.com URL with u= and id= parameters — Mailchimp, confirmed. To double-check, you spot the tell-tale hidden honeypot field in the form markup, and the Network tab shows a chimpstatic.com script powering a popup. But you do not stop there: you also notice a js.hs-scripts.com request loading site-wide, which is HubSpot's tracking code, suggesting they use HubSpot as a CRM alongside Mailchimp for newsletters. So the read is: Mailchimp for marketing email, HubSpot for CRM and tracking — a two-tool setup that tells you more about their go-to-market than any single fingerprint would. Checking every form, not just the obvious one, paid off.
What the email stack tells you about a company
The ESP and its companions are a clear read on marketing maturity. A site on a simple, free-tier email tool with a basic footer form is usually a smaller or earlier-stage operation. A site running a sophisticated ecommerce ESP like Klaviyo, with onsite tracking, popups and segmentation, signals a serious lifecycle-marketing effort. A HubSpot footprint points to an inbound, CRM-driven approach, often B2B. And a combination — say, an ESP plus a CRM plus the analytics and pixels from a separate detection pass — paints a full picture of how data-driven and growth-focused the company is. This is exactly the kind of signal that feeds technographic lead qualification: the tools a company chooses reveal how it operates.
Using this for outreach, responsibly
If you are building a prospect list, the email platform is a powerful filter — but use it responsibly. Detecting an ESP from public form actions and scripts is ordinary technographic research; the line to respect is what you do next. Target outreach on the relevance the signal provides (you genuinely help companies on a given platform), keep messaging honest about how you identified the fit, and follow anti-spam and data-protection rules for any contact you make. The detection itself is neutral; the responsibility is in the outreach. For the full method of turning detected tools into a qualified list, see how to build a B2B lead list from a website's tech stack.
How accurate is email-platform detection?
Accurate for platforms that expose a form or load a script, which is most of them. The form action is a structural signal that is hard to obscure while keeping the form working, and the loaded scripts have stable, recognisable domains, so the major ESPs are reliably detected. The accuracy gap is sites with no visible form and no onsite script — where email is handled server-side or via a back-end integration — and cases where a generic form posts to the site's own server, which then relays to an ESP you cannot see. So "which ESP does this signup form use?" is usually answerable with confidence, while "does this company use any email tool at all?" occasionally is not. Report the fingerprints you find, and be honest when the front end reveals nothing.
The workflow
- Find and inspect the signup form — read the
<form>action URL. - Watch the Network tab on load and on submit for the provider endpoint and scripts.
- View Source for provider domains and tell-tale hidden fields.
- Check every form, not just the footer, and note multiple tools.
- Report the fingerprints you find; say so honestly if the front end reveals nothing.
Go deeper
- The measurement stack: how to find out what analytics a website uses.
- Turn detection into prospects: how to build a B2B lead list from a website's tech stack.
- The whole stack: how to find out what technology a website uses.
- The theory behind it: what is technographics?
Want the email platform, analytics and full marketing stack in one report? Analyse any site with StackOptic — free, no sign-up.
Frequently asked questions
How do I find what email marketing platform a website uses?
Find the newsletter signup form and inspect it. Right-click the form, choose Inspect, and read the form's action URL — it usually points at the provider, such as list-manage.com for Mailchimp. Also check the DevTools Network tab for loaded scripts like static.klaviyo.com or js.hs-scripts.com, and view the page source for those domains. The form action plus the loaded script together identify most email platforms quickly and reliably.
Which signals identify Mailchimp specifically?
Mailchimp embedded forms post to a URL on a list-manage.com domain, with u= and id= parameters identifying the account and audience. The embed also includes a distinctive hidden honeypot field used to catch bots. On the loaded-script side, Mailchimp's popup and tracking code comes from chimpstatic.com. Seeing a list-manage.com form action, the honeypot field, or a chimpstatic.com script is a strong Mailchimp indicator; together they are conclusive.
What if the site has no visible signup form?
Some sites collect email only at checkout, in a gated content form, or via an account signup rather than a visible newsletter box. In those cases, inspect whichever form does exist and watch the Network tab as you interact with it. You may also find the ESP's tracking script loaded site-wide even without an obvious form. If no form and no provider script are present, the site may handle email entirely server-side, which detection cannot see.
Can a site use more than one email tool?
Yes. A company might use one platform for marketing newsletters and another, or a CRM, for transactional or sales email. It is common to see, for instance, Klaviyo for ecommerce marketing alongside HubSpot for CRM and forms. So check all the forms on the site, not just the footer newsletter, and report the full set of providers you find rather than assuming a single tool handles every type of email.
Why would I want to know a site's email platform?
The email service provider is a high-value technographic signal. For sales, especially for martech and competing email tools, it identifies both the incumbent and a potential switching opportunity. For competitive research, the ESP indicates how a rival runs lifecycle and marketing email and how sophisticated their stack is. Combined with other detected tools, it helps build a picture of a company's marketing maturity and feeds directly into lead qualification and outreach targeting.
Analyse any website with StackOptic
Get the full technology stack, performance, security and SEO report in seconds — free.
Analyse a websiteRelated articles
How to Tell if a Website Uses Progressive Web App (PWA) Features
A web app manifest, a registered service worker, installability and a theme-color tag are the PWA signals. Here is how to detect them in Chrome DevTools.
How to Tell if a Website Uses Akamai, Fastly, or CloudFront
Each major CDN leaves distinct header fingerprints — Fastly's x-served-by, Akamai's ghost markers, CloudFront's x-amz-cf-pop. Here is how to tell them apart.
How to Tell if a Website Uses Google reCAPTCHA
Google reCAPTCHA leaves signals: a recaptcha/api.js script, a grecaptcha global and a g-recaptcha data-sitekey. Here is how to detect it and tell v2 from v3.