Domains and companies
2.9 million company domains observed and re-observed on a schedule, de-duplicated to companies.
The data
How the intelligence is made
Company-level vendor relationships, verified from public records, graded for confidence, delivered where you work.
Coverage
Coverage
Vendors
1,300+ platforms and services detected across the graph, an average of 5.4 per company. The public directory lists the 500 largest install bases, from Google and Microsoft to Anthropic, Salesforce, DocuSign, HubSpot, Okta and Proofpoint. Custom platforms mapped on request for Enterprise.
Customers by vendor
80,955 accounts with Anthropic (Claude) records. 64,850 with Salesforce. 35,379 with DocuSign. 53,253 with OpenAI. Counted 2026-09-04; every figure links to the directory.
Geography and firmographics
Geography: global. Hosting and mail-server location on every row. Firmographics (HQ country, size band, industry) are added on request under an Enterprise data licence.
Method
How a relationship enters the graph
Vendors require customers to prove they control a domain before a product will send mail, sign documents or authenticate users. That proof is a public DNS record: a vendor-specific TXT token, an SPF include, an MX host or a CNAME to the vendor's infrastructure. IXM observes these records on a schedule, matches them to a catalogue of vendor signatures, and records first-seen and last-seen dates for each company-vendor pair. Records are read from public DNS only. We never log in, crawl behind authentication or collect personal data.
One record, end to end
From a DNS record to a graded row
1The company publishes proof
acme.com TXT "anthropic-domain-verification=3f9…"An administrator adds the record the vendor asked for. It is public by design.
2IXM observes and matches
signature: anthropic-domain-verification → AnthropicScheduled reads across 2.9M domains; 1,300+ vendor signatures; dates recorded.
3A graded row
acme.com · Anthropic · verification TXT · Verified · 2026-09-01Exported as CSV, searched in the app, or pushed to your CRM.
Confidence
Confidence grades
| Grade | Evidence | Typical use |
|---|---|---|
| Verified | Vendor-specific verification token or vendor CNAME on the company's domain | Displacement lists, TAM counts, diligence |
| Strong | SPF include or MX pointing at the vendor's mail infrastructure | Ecosystem targeting, ABM audiences |
| Inferred | Secondary or historical evidence, or a record last seen more than 90 days ago | Enrichment, with a human check |
Every export and API response carries the grade. Filter on it. Download a sample CSV (20 rows of example data in the real layout).
Schema
Data fields
| Field | Description |
|---|---|
| domain | Apex domain where the record was observed (one row per domain) |
| platform | The platform matched, e.g. Anthropic, Salesforce, DocuSign |
| evidence | The DNS record type that matched: verification TXT token · SPF include · MX host · CNAME |
| confidence | Verified (vendor-specific token or CNAME) · Strong (SPF include or MX) · Inferred (secondary evidence) |
| last_seen | Date of the most recent observation (ISO 8601) |
| platforms_all | Every other platform seen on the same domain (semicolon-separated) |
| email_platform | Mail provider inferred from MX, e.g. Google Workspace, Microsoft 365 |
| dmarc_policy · spf | Email-security posture of the domain (present on platform exports) |
| hosting_country · asn | Location and network of the domain's primary web host |
| hq_country · size_band · industry | Enterprise data licence only, on request |
Delivery
Delivery formats
IXM Explorer
Sign in at app.ixm.ai, paste your own accounts or search the whole graph by platform, filter, and export CSV within your plan.
IXM API
REST API and MCP connector on Growth and above. JSON, documented at app.ixm.ai/api-docs/.
Salesforce and HubSpot
Push accounts into Salesforce or HubSpot through the API with the included setup guides, Growth and above.
Data licence
Snowflake share, S3 bucket, AWS Data Exchange; Parquet or CSV.
Refresh
Freshness
The graph is re-observed continuously and every row carries its observation date. A one-off vendor list is cut from the latest observation at order time. Platform plans see updates as they land. Enterprise refresh SLAs are agreed per contract.
Limitations
What the data does not tell you
- A record proves a relationship exists. It does not show seat count, contract value or usage.
- Records can remain after a contract ends. Treat last-seen as an observation date, not a churn date.
- Some vendors verify through HTML files or one-off CNAMEs that we cannot observe, so we under-count them and say so in the vendor catalogue.
- An SPF include shows a vendor may send mail as the domain. For marketing platforms that is strong evidence; for transactional mail relays it is weaker, and we grade accordingly.
- Company resolution is automated and audited on a sample before each release. Report an error and we fix it in the next refresh.
- first_seen is the date we first observed a record. For relationships that existed before our first observation, it is the date of that first crawl, not the date the company adopted the vendor.
- One company may own several domains, and a domain may belong to an individual. We de-duplicate to companies and exclude domains that identify a person, and we publish the residual rate with every pack.