# Email setup map

> Draws a domain's email setup as one diagram: MX, the SPF include tree, DKIM and DMARC. Free, no signup. We look this up and don't keep it.

**Email setup map. A domain's whole email setup in one diagram, no signup.** Use it at https://tools.joinvalley.co/email-setup-map

## What is an SPF include tree? And what each part of the map shows.

An SPF record can include other domains' SPF records, which can include more: that's the include tree. Each include costs a DNS lookup, and SPF allows at most 10, so a tree that grows past 10 breaks SPF. The map draws the tree with its count, next to where the domain's mail goes, its DKIM keys and its DMARC policy.

| Part | What it shows | DNS record | The rule |
| --- | --- | --- | --- |
| Receiving | The servers that take the domain's email, and the provider when it's Google Workspace or Microsoft 365 | MX | Lowest priority number first; no MX means the domain itself |
| SPF include tree | Every domain the SPF record includes, and the ones those include | TXT at the domain | At most 10 DNS lookups, nested includes counted |
| DKIM | Keys found at common selectors, with their size | TXT at {selector}._domainkey | Selectors aren't listed anywhere, so we try common ones |
| DMARC | The policy for mail that fails: none, quarantine or reject | TXT at _dmarc | A subdomain without one inherits its parent's |

Provider names come only from the MX and SPF values Google and Microsoft publish. Everything else shows as the host or domain it is.

Sources: [RFC 7208: Sender Policy Framework (SPF)](https://www.rfc-editor.org/rfc/rfc7208) (read 2026-10-15), [RFC 6376: DomainKeys Identified Mail (DKIM) Signatures](https://www.rfc-editor.org/rfc/rfc6376) (read 2026-10-15), [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-10-15), [RFC 5321: Simple Mail Transfer Protocol, section 5.1](https://www.rfc-editor.org/rfc/rfc5321#section-5.1) (read 2026-11-02)

## How it works

Type a domain, a website or an email address. We look up its MX, SPF, DKIM and DMARC records through Cloudflare's public DNS resolver, the same lookups as our SPF, DKIM and DMARC checker, and don't keep them.

The map follows every include in the SPF record and every include inside those, and draws them as a tree, counting the DNS lookups against SPF's limit of 10. An include that doesn't lead to an SPF record is marked.

Next to it: where the domain's mail goes, the DKIM keys found at the common selectors we try, and the DMARC policy, including one inherited from a parent domain. Each part gets a one-line verdict.

It only reads DNS, so it can't see a DKIM selector it didn't think to try, or how a receiving server actually treated a message; paste a message's headers into our email header analyzer for that.

## What an email setup map shows you. And the problems a table hides.

Four things that are easy to see in a diagram and hard to see in a list.

### Why SPF stops at 10 lookups

Every include, a, mx, ptr and exists in an SPF record costs a DNS lookup, and so does everything inside each include. SPF allows at most 10. Past that, the check returns an error, and receivers can treat the record as broken.

The tree shows where the lookups go, so you can see which include to drop or replace.

Sources: [RFC 7208: Sender Policy Framework (SPF)](https://www.rfc-editor.org/rfc/rfc7208) (read 2026-10-15)

### Receiving and sending are separate

MX records say where a domain's email arrives; SPF says which servers may send as it. They're often different companies: a team on Google Workspace that also sends newsletters through another service. The map puts both side by side.

Sources: [RFC 5321: Simple Mail Transfer Protocol, section 5.1](https://www.rfc-editor.org/rfc/rfc5321#section-5.1) (read 2026-11-02), [RFC 7208: Sender Policy Framework (SPF)](https://www.rfc-editor.org/rfc/rfc7208) (read 2026-10-15)

### DKIM selectors are a guess

A DKIM key sits at a name made from a selector, like google._domainkey.acme.com, and nothing lists a domain's selectors. We try the common ones; if your sending service uses another, check it by name in our SPF, DKIM and DMARC checker.

Sources: [RFC 6376: DomainKeys Identified Mail (DKIM) Signatures](https://www.rfc-editor.org/rfc/rfc6376) (read 2026-10-15)

### Google Workspace and Microsoft 365 on the map

Google Workspace's MX is smtp.google.com or starts with aspmx, and its SPF include is _spf.google.com. Microsoft 365's MX ends in mail.protection.outlook.com and its SPF include is spf.protection.outlook.com. The map labels them when it sees them.

A clean setup gets your email delivered. What you say decides whether anyone replies. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Sources: [Google Workspace Help: Set up MX records for Google Workspace](https://knowledge.workspace.google.com/admin/domains/set-up-mx-records-for-google-workspace) (read 2026-10-30), [Microsoft Learn: Create DNS records for Microsoft 365](https://learn.microsoft.com/en-us/microsoft-365/admin/dns/create-dns-records-using-windows-based-dns?view=o365-worldwide) (read 2026-10-30), [Google Workspace Help: Set up SPF](https://knowledge.workspace.google.com/admin/security/set-up-spf) (read 2026-10-15), [Microsoft Learn: Set up SPF for your Microsoft 365 domain](https://learn.microsoft.com/en-us/defender-office-365/email-authentication-spf-configure) (read 2026-10-15)

## Sources

- [RFC 7208: Sender Policy Framework (SPF)](https://www.rfc-editor.org/rfc/rfc7208) (read 2026-10-15)
- [RFC 6376: DomainKeys Identified Mail (DKIM) Signatures](https://www.rfc-editor.org/rfc/rfc6376) (read 2026-10-15)
- [RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc9989) (read 2026-10-15)
- [RFC 5321: Simple Mail Transfer Protocol, section 5.1](https://www.rfc-editor.org/rfc/rfc5321#section-5.1) (read 2026-11-02)
- [Google Workspace Help: Set up MX records for Google Workspace](https://knowledge.workspace.google.com/admin/domains/set-up-mx-records-for-google-workspace) (read 2026-10-30)
- [Microsoft Learn: Create DNS records for Microsoft 365](https://learn.microsoft.com/en-us/microsoft-365/admin/dns/create-dns-records-using-windows-based-dns?view=o365-worldwide) (read 2026-10-30)
- [Google Workspace Help: Set up SPF](https://knowledge.workspace.google.com/admin/security/set-up-spf) (read 2026-10-15)
- [Microsoft Learn: Set up SPF for your Microsoft 365 domain](https://learn.microsoft.com/en-us/defender-office-365/email-authentication-spf-configure) (read 2026-10-15)

## Questions people ask

### What is an SPF include tree?

The chain of SPF records a domain's record pulls in: each include points at another domain's SPF record, which can include more. Together they decide which servers may send as the domain.

### How many DNS lookups can an SPF record use?

At most 10, counting every include, a, mx, ptr and exists, and everything nested inside includes. Past 10, SPF returns an error.

### How do I see all the SPF includes for a domain?

Type the domain above. The map follows every include and every include inside it, and draws them as a tree with the lookup count.

### Why does my SPF record go over 10 lookups?

Usually because each service you added brings its own includes, and nested ones count too. The tree shows which include uses the most, so you know what to drop or replace.

### How do I find a domain's DKIM selector?

There's no public list. Look in a received message's DKIM-Signature header for s=, or check the sending service's setup page; the map tries the common selectors for you.

### Can a domain use different companies to send and receive email?

Yes. MX records decide where mail arrives and SPF decides who may send, and they're often different services. The map shows both.

### Does the email setup map change my DNS?

No. It only reads public DNS records. We look them up and don't keep them.

### Is this email setup map free?

Yes, free with no signup. Map as many domains as you like.

## Related tools

- [SPF, DKIM and DMARC checker](https://tools.joinvalley.co/spf-dkim-dmarc-checker): Checks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.
- [MX lookup](https://tools.joinvalley.co/mx-lookup): Shows a domain's MX records and who handles its email, for one domain or 500 at once.
- [Email header analyzer](https://tools.joinvalley.co/email-header-analyzer): Reads an email's headers: whether SPF, DKIM and DMARC passed, its route and each delay.
- [Email spam checker](https://tools.joinvalley.co/email-spam-checker): Scores a cold email out of 100 and flags links, money signs, em dashes and merge tags.
- [Cold email domain finder](https://tools.joinvalley.co/cold-email-domain-finder): Sending domain ideas close to your brand, each checked against its registry.

## Next step

Want replies, not just clean copy? Valley finds buyers showing real buying signals and messages them across email and LinkedIn. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Shelf: [04 Email outreach](https://tools.joinvalley.co/email-outreach)

---

Tools by Valley, made by [Valley](https://www.joinvalley.co/?utm_source=tools_suite). HTML version: https://tools.joinvalley.co/email-setup-map
