Tech Stack Lookup - Company Vendor & SaaS Detection API
Pricing
from $10.00 / 1,000 domain analyzeds
Tech Stack Lookup - Company Vendor & SaaS Detection API
Give it a domain, get the SaaS vendors that company actually uses. Reads DNS verification records - the procurement trail HTML scanners miss - to surface AI tools, security, identity, CRM and collaboration vendors, plus email host and DMARC posture.
Pricing
from $10.00 / 1,000 domain analyzeds
Rating
0.0
(0)
Developer
Amit Mudaliyar
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Tech Stack Lookup — Company Vendor & SaaS Detection API
Give it a domain. Find out which SaaS vendors that company actually uses.
Not "what's on their website" — what's in their company. Their AI tools, identity provider, CRM, security stack, e-signature vendor, email host.
Input: ["figma.com"]Output: 36 vendors detectedAI Anthropic (Claude), Cursor, OpenAI, Decagon, GC AISecurity 1Password, Jamf, WizCollaboration Atlassian, Notion, Dropbox, ZoomDev tools Linear, MongoDB, Postman, GradleEmail Google Workspace DNS AWS Route 53
Why this finds things other tools miss
Most tech-detection tools read the homepage: they see your analytics tag and your CDN, and stop there. Almost nothing a company runs internally appears in HTML.
This Actor reads DNS verification records as well.
When a company adopts a SaaS product, that vendor usually asks them to prove domain ownership by publishing a TXT record. Those records are public, permanent, and they accumulate — every one is a vendor relationship the company confirmed itself. It's the difference between seeing a marketing pixel and seeing the actual procurement trail.
That's why this tool surfaces Cursor, Anthropic, Jamf, 1Password, Wiz, Linear, DocuSign — things no HTML scanner will ever see.
Signals combined:
| Source | What it reveals |
|---|---|
| DNS TXT | Confirmed vendor relationships — AI tools, security, identity, collaboration |
| MX | Email host (Google Workspace, Microsoft 365, Proofpoint, Mimecast) |
| SPF includes | Who sends mail on their behalf — Zendesk, Salesforce, Marketo, SendGrid |
| DMARC | Email-security posture (none / quarantine / reject) |
| NS | DNS and CDN provider |
| HTTP headers | Hosting, CDN, framework |
| Homepage HTML | Analytics, chat widgets, CMS, pixels, payments |
No proxies, no headless browsers, no login. Just public infrastructure records — which is why a domain profiles in about a second.
What you can do with it
Sell to companies that already use a category.
Find every account running Drift, and pitch the replacement. vendorFilter: ["drift"].
Find AI adopters.
categories: ["ai"] tells you who has already put Anthropic, OpenAI or Cursor into production — the single fastest-moving buying signal in B2B right now, and one that barely exists in commercial datasets yet.
Qualify inbound. A signup lands. Before the first call, know their stack, their scale, and their security posture.
Competitive displacement. Track which vendors your target accounts adopt and drop over time by re-running on a schedule.
Security and vendor due diligence. Check DMARC policy and see the third-party surface area of an acquisition target.
Pairs with ATS Jobs Scraper & Hiring Signals — that one tells you who a company is hiring, this one tells you what they buy. Same input, same account list, two halves of the same picture.
Input
{"domains": ["figma.com", "monzo.com", "gitlab.com"],"categories": ["ai", "security"],"includePageSignals": true}
| Option | Default | What it does |
|---|---|---|
domains | required | Bare domains or full URLs. |
categories | [] | Keep only these categories — ai, security, crm-sales, … |
vendorFilter | [] | Keep only vendors matching these strings, e.g. ["openai"]. |
includePageSignals | true | Also fetch the homepage. Turn off for a faster, pure-DNS run. |
outputVendorRows | false | Adds a flat row per vendor — good for CSV and pivot tables. |
includeRawDns | false | Adds MX, nameservers, SPF includes and unrecognised TXT prefixes. |
concurrency | 8 | Domains profiled in parallel. |
Output
One domain-profile per domain:
{"type": "domain-profile","domain": "figma.com","siteTitle": "Figma: The collaborative canvas for design, code, and AI","vendorCount": 36,"aiTools": ["Anthropic (Claude)", "Cursor", "Decagon", "GC AI", "OpenAI"],"securityTools": ["1Password", "Jamf", "Wiz"],"devTools": ["Gradle", "Linear", "MongoDB", "Postman"],"collaborationTools": ["Atlassian", "Dropbox", "Notion", "Zoom"],"emailProvider": "Google Workspace","dnsProvider": "AWS Route 53","hasSpf": true,"hasDmarc": true,"dmarcPolicy": "quarantine","byCategory": { "ai": 5, "collaboration": 4, "devtools": 4, "security": 3 },"vendors": [{"vendor": "Anthropic (Claude)","category": "ai","categoryLabel": "AI & LLM tools","sources": ["dns-txt"],"evidence": "anthropic-domain-verification-4rt01s=L6y4AAr..."}]}
Every detection carries its evidence. You can see exactly which record produced it, so nothing is a black box and you can verify any result yourself with a dig command.
Set outputVendorRows: true to also get one flat row per vendor — the shape you want for a spreadsheet or a CRM import.
Honest limits
Absence is not proof. A vendor missing from the output means no public signal was found — not that the company doesn't use it. Plenty of SaaS products never require a DNS record. Read this as high-confidence positives, not a complete inventory.
Verification records can outlive the contract. Companies rarely clean up DNS after churning a vendor, so a record can linger past cancellation. Treat detections as "has a relationship with", not "is currently paying for".
Coverage is strongest where fingerprints are public. The vendor knowledge base was built from fingerprints sampled across real company domains and grows over time. Anything unrecognised is returned in unmatchedTxtPrefixes (with includeRawDns: true) rather than silently dropped — so you can see what was found but not yet named.
Only public records are read. No logins, no personal data, no private endpoints. Everything here is visible to anyone running dig.
Pricing
Pay per event — one charge per domain successfully profiled, however many vendors come back. Domains with no DNS records at all aren't charged.
Support
Spotted a vendor fingerprint that isn't recognised yet? Open an issue with the TXT prefix and it'll be added — the knowledge base improves with every report.
More from this creator
Three Actors, one account-intelligence picture — all built on official public APIs, no proxies:
| Actor | Answers |
|---|---|
| ATS Jobs Scraper & Hiring Signals | Who is a company hiring? Open roles from nine ATS platforms plus a scored hiring-momentum report. |
| Tech Stack Lookup (this one) | What does a company buy? AI tools, CRM, security and analytics vendors, detected from public DNS records. |
| App Store Intelligence & ASO | How does an app perform? Ratings, rankings and ASO across every country storefront. |