Vendor footprint

Third-party vendors identified from each company's own published DNS — apex TXT domain-verification tokens and SPF include: mechanisms. Both exist specifically so the vendor (and every receiving mail server) can confirm the relationship; reading them back decodes a public declaration, it doesn't infer one. See the full vendor classification table for exactly which prefixes and SPF hosts map to which vendor.

174 of 177 companies resolved at least one vendor from published DNS alone — 95 distinct vendors identified, 17 of them security-relevant.

Top vendors, by prevalence

Each square is one company; hover it for the name. 83 more vendors beyond the top 12, not charted — see the full table below.

Security vendors

The most differentiated slice of this data — endpoint management, secrets, vulnerability disclosure and posture tooling, each naming exactly which companies run it. 5 more beyond the top 12, not charted.

All 95 vendors

Vendor	Category	Companies
Google (Workspace / Search Console)	productivity	151
Microsoft 365	productivity	139
Atlassian (Jira / Confluence)	collaboration	112
Apple Business Manager	productivity	98
DocuSign	productivity	80
Adobe	productivity	75
Meta Business	marketing	61
OneTrust sec	security	61
Anthropic	productivity	54
Proofpoint sec	security	48
Amazon SES	email	47
GlobalSign sec	security	47
Cisco sec	security	46
Docker	infrastructure	46
Smartsheet	collaboration	45
Jamf sec	security	43
Miro	collaboration	36
OpenAI	productivity	36
MongoDB Atlas	infrastructure	34
Airtable	productivity	32
Canva	productivity	31
Dynatrace	infrastructure	28
Figma	productivity	25
Salesforce	email	25
Wiz sec	security	25
Autodesk	productivity	24
Stripe	payments	24
Palo Alto Networks sec	security	22
Adobe Dynamic Tag Manager	marketing	21
Cisco Webex	collaboration	20
Adobe Sign	productivity	19
Cursor	productivity	19
Mimecast sec	security	19
Twilio	infrastructure	18
TeamViewer	collaboration	16
Box	storage	14
HPE GreenLake	infrastructure	14
Postman	infrastructure	14
Shopify	infrastructure	14
Slack	collaboration	14
Workplace from Meta	collaboration	14
1Password sec	security	13
LiveRamp	marketing	13
Mixpanel	analytics	13
Notion	collaboration	12
Pexip	collaboration	11
SAP SuccessFactors	productivity	11
Yahoo	email	11
HackerOne sec	security	10
LogMeIn	collaboration	10
SendGrid (Twilio)	email	10
HashiCorp Cloud Platform	infrastructure	9
IBM	infrastructure	9
Pendo	analytics	9
Mailchimp	email	8
Perplexity	productivity	8
Cisco Duo sec	security	7
Dell Technologies	infrastructure	7
Google Workspace	email	7
KnowBe4 sec	security	7
LucidLink	storage	7
Uber for Business	productivity	7
Zapier	productivity	7
Dropbox	storage	6
Have I Been Pwned sec	security	6
HubSpot	email	6
Klaviyo	marketing	6
Mailgun	email	6
Wrike	collaboration	6
Censys sec	security	5
Symantec/Broadcom Email Security sec	security	5
monday.com	collaboration	5
Brevo (Sendinblue)	email	4
Loom	collaboration	4
Mandrill (Mailchimp Transactional)	email	4
Sinch	infrastructure	4
Sophos sec	security	4
Yandex	productivity	4
Alibaba Cloud	infrastructure	3
Citrix	collaboration	3
JetBrains	productivity	3
Mailjet	email	3
Marketo (Adobe)	email	3
Parallels	infrastructure	3
Qualtrics	email	3
Snowflake	infrastructure	3
Zoom	collaboration	3
Adobe Experience Manager	productivity	2
Campaign Monitor	email	2
Jumio sec	security	2
Mail.Ru	email	2
Segment	analytics	2
Zoho	productivity	2
Matillion	infrastructure	1
Pinterest	marketing	1

Method & caveats

Built from domain_dns_summary.txt_records and spf_record, aggregated across every domain each company owns, the same "a subsidiary's footprint counts too" scope the infrastructure analysis above uses. A verification token or SPF include only proves the company configured that relationship at some point — not that it's still active today, and not the reverse (a vendor's absence here means no DNS-visible signal was found, not confirmed non-use). One company can run several products in the same category; category totals in the chart above count distinct companies, not tool count.