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.
Marketo (Adobe Marketo Engage) source composition | 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.
- One homepage and six landing-page prefixes were checked per organization. Deeper pages, other subdomains and tag-manager payloads were not checked.
- Published configuration can remain after a subscription ends. It does not confirm current tracking, paid status, company-wide use or buying intent.
- The selected accounts lean toward B2B software and enterprise companies. Findings describe this list, not the Marketo market.
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.