Free tool
See the software a company’s DNS gives away
Enter a domain to see the tools its public DNS records name, who handles its email, whether SPF, DKIM and DMARC are set up, and which automations fit what it already runs.
Check a domainFree, no sign-up Updated Method and sources Markdown version
| TXT | Verification tokensAccounts the domain was verified with, such as Microsoft 365, Stripe or Atlassian |
|---|---|
| SPF | Who may send as youEmail services, CRMs and helpdesks that send mail from the domain |
| MX | Who receives your mailThe mail provider, or a filtering gateway in front of it |
| DMARC | Spoofing policyWhether failing mail is monitored, quarantined or rejected |
| NS | Who hosts DNSCloudflare, Route 53, GoDaddy and others |
Summary and how to use it
A company’s public DNS names some of the software it uses. Services ask for a TXT record to prove you own the domain, the SPF record lists who may send email as you, MX shows who receives your mail and NS shows who hosts your DNS. Reading those records shows part of the stack and whether email authentication (SPF, DKIM and DMARC) is set up. Apps that never ask for a DNS record stay invisible.
What a typical result shows
A 40-person company’s domain might show Google Workspace from its MX and SPF records, HubSpot and Mailchimp from SPF includes, a Stripe and a DocuSign verification token in TXT, and Cloudflare as the DNS host. SPF ends in ~all with five lookups, there is a Google DKIM key, and DMARC is missing. The checker would say to add DMARC at p=none with a report address, and suggest lead routing between the inbox and HubSpot and quotes sent for signature from the CRM.
How to use it
- 1Enter a domain
Type a company domain such as example.com. A full web address or an email address works too.
- 2Read the tools found
Each tool is grouped by category, with the DNS record that shows it.
- 3Check email authentication
Read the SPF, DKIM and DMARC verdicts and what to fix for each.
- 4Look at the automations
See which automations fit the tools found, with a page on each.
- 5Book the audit if it helps
The $500 audit maps every tool and handoff, including the ones DNS cannot see.
Check a domain
We read the public records any mail server reads and match them against 94 products. The domain is not stored.
Email authentication
Tools in public DNS
Automations that fit this stack
Map the rest of the stack in an audit
DNS shows the tools that left a record. The $500 Automation Audit maps every tool and handoff your team uses, ranks what to fix with a fixed price for each, and the fee is credited to the build.
How the check works
It reads the same public records every mail server and browser reads. Nothing is scanned, logged in to or probed.
The TXT, MX and NS records at the domain, the DMARC record at _dmarc, and DKIM keys at 9 common selectors (google, selector1, selector2, k1, s1, s2, resend, zoho, mail). Lookups go through Cloudflare’s public DNS over HTTPS, with Google’s as a fallback, all at once with a short timeout.
Each record is compared with a list of patterns we have seen in live records or in the vendor’s own setup instructions, such as stripe-verification= in TXT or include:_spf.google.com in SPF. We leave out patterns we are unsure of, so a miss is more likely than a wrong match.
Software that never asked for a DNS record: most apps signed in to with Google or Microsoft, tools used by one team, and services that send mail from their own domain. Old verification tokens can also outlive the tool.
The domain you enter goes to our server, which asks the public resolvers and returns the answer. We do not save it, and the analytics event for a check records only that a check ran and how many tools it found. Answers are cached for an hour.
Use it from your AI assistant
Run the same method in ChatGPT, Claude or Perplexity, or connect your assistant or coding agent to the tool directly. Agents get the same numbers as this page.
Any chatbot
Copy the prompt, or open it in one click. The assistant reads the published method and interviews you for the inputs.
Help me use the SBD Stack checker. Read the method at https://smallbaydigital.com/tools/stack-checker.md and follow it exactly. Ask me for the inputs that matter most, a few at a time. If I don't know one, use the documented default and tell me you did. Then give the conclusion first, the numbers behind it, the assumptions you made, and a link to https://smallbaydigital.com/tools/stack-checker/ so I can check it. Steps from the method: 1. Enter a domain: Type a company domain such as example.com. A full web address or an email address works too. 2. Read the tools found: Each tool is grouped by category, with the DNS record that shows it. 3. Check email authentication: Read the SPF, DKIM and DMARC verdicts and what to fix for each. 4. Look at the automations: See which automations fit the tools found, with a page on each. 5. Book the audit if it helps: The $500 audit maps every tool and handoff, including the ones DNS cannot see. If you can call MCP tools, connect to https://smallbaydigital.com/api/mcp and use the stack_check tool, which runs the same calculation as the web page.
Claude Code, Codex, Cursor and other agents
Add the SBD tools as an MCP server. No login or key, read-only, and nothing you enter is stored.
claude mcp add --transport http sbd-tools https://smallbaydigital.com/api/mcp
Server URL https://smallbaydigital.com/api/mcp. Tool name stack_check.
Where the numbers come from
Each default and rule is traced to a published source, or labelled as practitioner guidance where no audited benchmark exists.
- IETF RFC 7208: Sender Policy Framework (SPF)Used forSPF checks, the 10 lookup limit and the all qualifiers
Defines the SPF record, its mechanisms and qualifiers, and limits evaluation to 10 DNS-querying terms (section 4.6.4). Two SPF records for one domain is an error.
- IETF RFC 7489: DMARCUsed forDMARC policy, rua and pct checks
Defines the record at _dmarc, the p= policy (none, quarantine or reject), aggregate report addresses (rua) and the pct tag.
- IETF RFC 6376: DKIM SignaturesUsed forWhere DKIM keys are looked up
Public keys are published at <selector>._domainkey.<domain>. Selector names are chosen by the sender, so they cannot all be listed.
- Google Email sender guidelinesUsed forWhy DMARC matters for delivery
Senders to Gmail need SPF or DKIM, and bulk senders (around 5,000 messages a day or more) need SPF, DKIM and a DMARC record.
- Cloudflare 1.1.1.1 DNS over HTTPS, JSON formatUsed forThe primary resolver
Public resolver answering DNS queries over HTTPS in JSON.
- Google Public DNS JSON APIUsed forThe fallback resolver
Google’s public resolver, used when Cloudflare does not answer in time.
What the terms mean
- DNS
- The public directory that turns a domain name into the servers for its website, email and other services.
- TXT record
- A free-text DNS record. Many services ask you to add one with a token to prove you control the domain.
- MX record
- Names the servers that receive email for the domain, which usually shows the mail provider or a filtering gateway in front of it.
- SPF
- Sender Policy Framework. A TXT record listing the servers and services allowed to send email as the domain. RFC 7208.
- DKIM
- DomainKeys Identified Mail. A public key in DNS, published under a selector name, that receivers use to check a message’s signature. RFC 6376.
- DMARC
- A TXT record at _dmarc that tells receivers what to do with mail failing SPF and DKIM (none, quarantine or reject) and where to send reports. RFC 7489.
- NS record
- Names the nameservers for the domain, which shows who hosts its DNS.
- DNS over HTTPS
- A way to query public DNS over an ordinary web request. The checker uses Cloudflare’s resolver, with Google’s as a fallback.
Questions about DNS and email records
What does DNS reveal about a company’s software?
The services that needed a DNS record to work. Verification tokens in TXT records show accounts such as Microsoft 365, Stripe, DocuSign, Atlassian or OpenAI, the SPF record lists services that send email as the company, MX shows the mail provider and NS shows the DNS host. It cannot show apps that never asked for a record.
What is DMARC and do I need it?
DMARC is a DNS record that tells receiving mail servers what to do with messages that fail SPF and DKIM checks, and where to send reports. Google and Yahoo require it for bulk senders, and without it anyone can send mail that appears to come from your domain. Start at p=none with a report address, then move to quarantine and reject once the reports show your real senders pass.
Is it legal to look up DNS records?
DNS records are published so that any mail server or browser on the internet can read them. Looking them up is what every email you send already does. The checker reads only those public records and does not scan, log in to or probe any server.
Why doesn’t it find all our tools?
Most software never asks for a DNS record. Tools you sign in to with Google or Microsoft, apps used by one team, and services that send from their own domain leave nothing to read. Verification records are also often removed once a domain is verified, and DKIM keys can sit under selector names we do not check.
Do you store the domains people check?
No. The domain is sent to our server, which asks two public DNS resolvers and returns the answer. Nothing is saved, and the result is cached for an hour so the same check is not repeated.
What does a good SPF record look like?
One TXT record starting v=spf1 that includes each service that sends as you and ends in ~all or -all. It must stay within 10 DNS lookups once includes are expanded, so remove services you no longer use.
Why does it say DKIM was not found when we have it?
DKIM keys are published under a selector name the sender chooses. We check nine common ones (google, selector1, selector2, k1, s1, s2, resend, zoho and mail). If yours uses another name, the key is there but we cannot see it. Your mail provider’s admin page shows the selector.
Can a verification token mean a tool is no longer used?
Yes. Tokens often stay after a trial ends or a tool is replaced, so a token shows the domain was verified with that service at some point. Removing old tokens is good housekeeping.
Can I use this from ChatGPT or Claude?
Yes. Connect your assistant to the SBD MCP server at smallbaydigital.com/api/mcp and ask it to run stack_check on a domain. It returns the same result as this page.
More free tools
- Automation and AI ROI calculatorFree, vendor-neutral automation and AI ROI calculator: loaded labour cost, risk adjustment, NPV, IRR, discounted payback and scenarios, with the method shown.Open the tool
- Automation opportunity mapperFree, vendor-neutral automation opportunity mapper. Score each process on impact and ease, plot a 2×2 and get a ranked roadmap, with method and sources shown.Open the tool
- Build vs buy decision toolFree, vendor-neutral build vs buy tool. Compare buying, low-code and custom builds on a weighted scorecard and three-year cost of ownership, with sources shown.Open the tool
- AI readiness assessmentFree AI readiness self-assessment across the six pillars of the Cisco AI Readiness Index: 24 questions, a radar chart, a readiness stage and next steps.Open the tool
- AI agent risk and controls plannerFree AI agent planner. Describe what the agent reads and does, and get its risk profile, the OWASP LLM risks that apply, a starting autonomy level and controls.Open the tool
- All free toolsEvery calculator and planner, with its method and sources.See all















