33
Homepage HTML · Tier A
Marketo form or Munchkin configuration. Includes 18 accounts that also have a landing-page CNAME.
Marketing and CRM · October 2026 research
Looking for a Marketo customers list? These are 99 companies with published Marketo configuration, checked 11 October 2026: 33 in homepage HTML and 66 through landing-page DNS. Published configuration doesn't confirm a current paid subscription.
Package dated 2026-10-11. Original source dates and website scope stay with the records.
99 reviewed company accounts
Package dated
CSV/JSON research package
99 reviewed company accounts with published Marketo configuration: 33 in homepage HTML and 66 through landing-page DNS only. Of the DNS-only accounts, 59 hosts answered HTTPS and 7 gave no response and may be stale. Tracking execution and paid subscriptions are unverified.
Price and delivery by enquiry
Enquire about this packageDownload the 4-row CSV preview33
Marketo form or Munchkin configuration. Includes 18 accounts that also have a landing-page CNAME.
59
Marketo-pointed landing-page host answered HTTPS. Redirects and 404s count as responses.
7
No HTTPS response. These records may be stale.
99 accounts, counted once each. Checks: 2026-10-11, 07:27–11:02 UTC. Published configuration does not verify active tracking or a paid subscription.
Four approved examples in CSV: company name, domain, recorded signal, check date and website scope. Confirm private delivery fields by enquiry.
CSV columns: name · domain · sourceClass · checkedOn · scope
These approved examples illustrate the 2026-10-11 package. They are not a representative sample of all customers.
workday.com
Marketo form/Munchkin configuration on the homepage, plus a company landing-page subdomain pointing to Marketo · Tier A · 2026-10-11
corporate homepage and 1 marketing landing-page subdomain. Published page configuration at the check date; not proof of a paid subscription or organization-wide use.
nokia.com
Marketo form/Munchkin configuration on the homepage, plus a company landing-page subdomain pointing to Marketo · Tier A · 2026-10-11
corporate homepage and 1 marketing landing-page subdomain. Published page configuration at the check date; not proof of a paid subscription or organization-wide use.
crowdstrike.com
Company landing-page subdomain pointing to Marketo (DNS only) · Tier B · 2026-10-11
1 marketing landing-page subdomain. DNS endpoint configuration only; not proof of active tracking or a paid subscription.
macnica.co.jp
Company landing-page subdomain pointing to Marketo (DNS only) · Tier B · 2026-10-11
1 marketing landing-page subdomain. DNS endpoint configuration only; not proof of active tracking or a paid subscription.
The four preview rows come from the package dated 11 October 2026. Each row records how Marketo was found and the check date. The steps below repeat each check on the live website. A check run today is a new observation; it doesn't change what the package recorded on 11 October.
| Company | Where to look | Recorded on 2026-10-11 |
|---|---|---|
| WorkdayTier A · homepage HTML | https://www.workday.com/DNS: info.workday.com | Recorded on 2026-10-11The homepage HTML loaded the Marketo Forms 2.0 script and set a Munchkin ID. Workday's landing-page host also pointed at Marketo in DNS, and the account counts once, in Tier A. |
| NokiaTier A · homepage HTML | https://www.nokia.com/DNS: pages.nokia.com | Recorded on 2026-10-11The homepage HTML loaded the Munchkin script from munchkin.marketo.net and called Munchkin.init with an instance ID. Nokia's landing-page host also pointed at Marketo in DNS, and the account counts once, in Tier A. |
| CrowdStrikeTier B · DNS only | DNS: go.crowdstrike.com | Recorded on 2026-10-11The homepage showed no reviewed Marketo signature. The landing-page host's CNAME pointed at Marketo, and its root redirected to the company website. |
| MacnicaTier B · DNS only | DNS: go.macnica.co.jp | Recorded on 2026-10-11The homepage showed no reviewed Marketo signature. The landing-page host's CNAME pointed at Marketo, and its root redirected to the company website. |
Open the homepage, view the page source and search for: forms2munchkin
A tag manager can add Marketo after the page loads, so no match in the source doesn't prove Marketo is gone.
Look up the landing-page host's CNAME. For CrowdStrike:
dig +short CNAME go.crowdstrike.comA target under mktoweb.com or mktossl.com matches the package rule. The company controls its own DNS zone, so the record ties the landing-page host to that company. A CNAME can outlive a cancelled subscription, which is why DNS-only rows sit in their own tier.
Both Tier B hosts counted as answering HTTPS because their root redirected to the company website. Tier B accepts any HTTP status, including redirects and 404s. A response shows the host was reachable on the check date. It doesn't show that campaigns were running.
The rows don't show paid status, current tracking, company-wide use or plans to migrate. They are approved examples, not a representative sample of the 99 accounts, and the 99 accounts are a selected list rather than Marketo's customer base.
For each of the 99 accounts, the package records which check matched (homepage HTML, landing-page DNS or both), the hosts checked, the tier and the check time. Contacts are separate fields and stay out of the public preview. Price and delivery are by enquiry.
WhosBuilt analysis of the saved October 2026 package. Findings describe this selected cohort, not market share.
84 accounts with a Marketo CNAME
Among 84 accepted accounts with a Marketo CNAME: pages 30, go 27, info 25, lp 2, engage 2 and marketing 0. An account can use more than one prefix.
These counts cover only the six checked prefixes, not every Marketo host a company runs.
Package 2026-10-11 · company accounts with a Marketo CNAME · WhosBuilt saved-record analysis
59 / 84 · 70.2%
59 of 84 DNS accounts point only to Marketo labels containing their own brand. The other 25 use instance IDs, older company names or unrelated labels; attribution rests on who controls the DNS zone.
Brand matching is a substring check against the registrable domain name. Former names count as non-matching; labels do not establish subscription status.
Package 2026-10-11 · company accounts with a Marketo CNAME · WhosBuilt saved-record analysis
Homepage and DNS checks on 2026-10-11, 07:27–11:02 UTC. Each account was checked on its own website or landing-page DNS. The date records the saved observations.
99 reviewed company accounts with published Marketo configuration: 33 in homepage HTML and 66 through landing-page DNS only. Of the DNS-only accounts, 59 hosts answered HTTPS and 7 gave no response and may be stale. Tracking execution and paid subscriptions are unverified.
| Source class | Count | Scope |
|---|---|---|
| Tier A · homepage configuration | 33 | Reviewed Marketo form or Munchkin configuration in homepage HTML. 18 of these accounts also have a landing-page CNAME; they are counted once here. |
| Tier B · DNS-only endpoint, HTTPS response | 59 | Company-controlled landing-page DNS points to Marketo and the host answered HTTPS. Any HTTP status counts, including redirects and 404s; a response does not establish active tracking or a subscription. |
| Tier C · DNS-only endpoint, no HTTPS response | 7 | Company-controlled landing-page DNS points to Marketo, but no HTTPS response was received. These records may be stale and are not confirmed active installations. |
Homepage HTML shows one-third of the accepted accounts: Denominator: all 99 accepted accounts in this list; each account is counted once. One homepage read per organization, with a browser fallback when blocked, plus DNS checks for six landing-page prefixes.
Seven DNS-only endpoints gave no HTTPS response: Denominator: the 66 accepted accounts with a landing-page CNAME and no homepage configuration. One HTTPS GET of the root of up to two Marketo-pointed hosts per account.
pages, go and info are the common landing-page prefixes: Denominator: 84 accepted accounts with at least one Marketo CNAME on the six checked prefixes. Prefix groups can overlap. Count accounts with a matching landing-page CNAME separately for go, info, pages, lp, engage and marketing.
The DNS zone matters when the target label hides the brand: Denominator: the 84 accepted accounts with at least one Marketo CNAME. Classify the first matching CNAME target for each checked host against the account's registrable domain name.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.
33 / 99 · 33.3%
33 of 99 accepted accounts (33.3%) publish Marketo form or Munchkin configuration in homepage HTML. The other 66 were found only through landing-page DNS.
The homepage share is a floor: tag-manager payloads and forms on deeper pages were not checked.
Package 2026-10-11 · accepted company accounts · WhosBuilt saved-record analysis
59 / 66 answered HTTPS · 7 may be stale
59 of the 66 DNS-only accounts had a Marketo-pointed host that answered HTTPS. Seven gave no HTTPS response and are marked as possibly stale.
Any HTTP status counts as a response, including redirects and 404s. An answering endpoint does not prove active tracking or a subscription.
Package 2026-10-11 · DNS-only company accounts · WhosBuilt saved-record analysis
99 reviewed company accounts
Package dated
CSV/JSON research package
99 reviewed company accounts with published Marketo configuration: 33 in homepage HTML and 66 through landing-page DNS only. Of the DNS-only accounts, 59 hosts answered HTTPS and 7 gave no response and may be stale. Tracking execution and paid subscriptions are unverified.
Price and delivery by enquiry
Enquire about this packageDownload the 4-row CSV previewPaid files are licensed for internal use; no resale or redistribution.