vendorprint Install CLI

PUBLIC DNS. REAL EVIDENCE.

Every domain
leaves a fingerprint.

Find the tools behind the domain.
Scan a website. Explore the signals.
See exactly what the records say.

No sign-up. Public DNS only. No website crawling.

Powered by vendorprint

SAVED EXAMPLE · SYNTHETIC

truststack.example

Explore a saved example, or enter your own domain above.
truststack.exampleDNS-visible stack

Choose a bubble to inspect its evidence

Saved examples (synthetic)

A DNS record is a clue, not a customer list. Findings can show configuration or a domain relationship; they do not prove active subscriptions or reveal an entire stack.

Use vendorprint in your terminal.

Run it once with npx, no install needed. Replace example.com with the domain you want to scan.

Get started in one command

Need more scans? Run the free CLI locally. Node.js 20 or newer.npm packageDocumentation

FOR AI AGENTS

Give your agent
evidence to work with.

Add company technographics to your research workflow. The VendorPrint skill teaches your agent to scan public DNS, explain vendor signals, and keep uncertainty visible.

For Codex, Claude Code, Cursor, and other compatible coding agents with shell access.

Read the agent setup guide

01 / INSTALL THE SKILL

Choose your agent in the installer. Node.js 22.20+ for installation; 20+ for scans. No VendorPrint API key.

02 / ASK ABOUT A COMPANY

Use vendorprint to research example.com's software stack. Show the evidence, confidence, and what remains unknown.

Replace example.com with the domain you want to research.

Inspect the skill on GitHub
80 bounded DNS attempts per domain
4 logical queries in flight per domain
0 company website requests

Evidence first. Inference second.

Every result separates what DNS proves, what the stack suggests, and what remains unknown.

  1. URL / HOSTNAME

    Normalize the company domain

    Group account URLs by company while retaining exact hostnames for DNS checks.

  2. MX / TXT / CNAME

    Query a bounded record set

    Check high-yield public records with hard limits on retries and concurrency.

  3. VENDOR TARGET

    Attribute the evidence

    Match owned infrastructure, tracking targets, and verification proofs.

  4. JSON / NDJSON

    Return a reviewable profile

    Keep evidence and confidence attached to each finding, with observation time and scan completeness.

Product signals across two company cohorts.

A dated full-mode DNS baseline, with software vendors and large enterprises measured separately.

82.1%software-cohort domains with direct product configuration

821 of 1,000 sourced domains. 98.9% had any vendor finding.

Fortune cohort: product configuration
39.8%
Software: trust-center hosting
18.7%
Software: identity relationships
16.1%
Software: business software
97.5%

Scans started October 15, 2026 UTC. Benchmark package 0.4.0 / catalog 2026.10.14. Current catalog: 0.5.0 / 2026.10.15; these percentages have not been remeasured for this release. Direct configuration excludes generic hosting and email infrastructure. It does not prove active licensing, seats, or internal usage. New cohorts replace the old Inc. headline; percentages are not comparable across cohorts.

Browse signatures and full methodologyDownload benchmark summaries

Every conclusion carries its receipt.

Strong matches stay direct. Compatibility stays a candidate. Missing records stay inconclusive.

Public observation Supported finding Relationship
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 Relationship / medium

Point it at a list. Keep the evidence.

Stream NDJSON, resume interrupted jobs, and review every claim before it enters another system.

View the source Read the docs