OPEN SOURCE / PUBLIC DNS
Find the tools behind the domain.
Turn public DNS into reviewable GTM technology signals without requesting company websites.
Get started in one command
No global install. Requires Node.js 20 or newer. See more commands
Run the sample like a real CLI.
Type a domain, press Return, and inspect the evidence printed in the terminal.
vendorprint sample session
vendorprint brightyard.example
evidence:
Evidence first. Inference second.
Every result separates what DNS proves, what the stack suggests, and what remains unknown.
-
URL / HOSTNAME
Normalize the company domain
Resolve messy account URLs to one registrable domain before any lookup begins.
-
MX / TXT / CNAME
Query a bounded record set
Check high-yield public records with hard limits on retries and concurrency.
-
VENDOR TARGET
Attribute the evidence
Match owned infrastructure, tracking targets, and verification proofs.
-
JSON / NDJSON
Return a reviewable profile
Keep the evidence, confidence, relationship, and caveat attached to every finding.
Public signals across the Inc. 5000.
A full scan of 4,981 unique company domains found at least one observable technology signal on 94.7% of them.
71.8% included at least one high-confidence finding.
- Email delivery
- 58.0%
- Marketing automation
- 47.6%
- CRM
- 37.6%
- AI workspaces
- 23.9%
2024 Inc. 5000 cohort, scanned August 3, 2026. Coverage means a public DNS relationship was observed. It does not prove active licensing, seats, or internal usage.
Every conclusion carries its receipt.
Strong matches stay direct. Compatibility stays a candidate. Missing records stay inconclusive.
MX → google.com
Google Workspace
Direct / high
CNAME → outrch.com
Outreach tracking
Direct / high
CNAME → mktoweb.com
Adobe Marketo Engage
CRM candidates
openai-domain-verification
OpenAI domain relationship
Direct / high
Point it at a list. Keep the evidence.
Stream NDJSON, resume interrupted jobs, and review every claim before it enters another system.