Skip to content

How to look up your own SPF, DKIM and DMARC records

Checked 18 November 2026

Each record sits at its own name in DNS, and you ask for the TXT record at that name. SPF is at your domain itself, DMARC is at _dmarc in front of it, and DKIM is at your selector followed by _domainkey in front of it.123

Which name for which record

Record Name to look up Type
SPF Your domain, such as example.com TXT
DMARC _dmarc.example.com TXT
DKIM selector._domainkey.example.com TXT

For SPF, the standard says each record is placed at the owner name it pertains to, not in a subdomain under it.1 For DMARC, the preferences are stored as TXT records in subdomains named "_dmarc".2 For DKIM, all keys are stored in a subdomain named "_domainkey", and the selector goes in front.3

You need the selector for DKIM. Your mail service shows it in its setup page, and it's also in the s= part of the signature on a sent message. See How DKIM signing works and Reading the authentication results in an email header.

Looking up all three recordsPick a lookup toolAsk for TXT at the domain for SPFAsk for TXT at _dmarc for DMARCAsk for TXT at selector._domainkey
Each record sits at its own name, so you make one lookup per record.

Using a lookup tool

Two kinds of tool do the job. Web-based DNS lookup pages let you type a name and pick TXT as the type. Command-line tools do the same from a terminal. Either way, you get the same answer from DNS.

The DMARC standard shows a command-line example:2

dig +short TXT _dmarc.example.com.

For that example the standard shows this reply:2

"v=DMARC1; p=none; rua=mailto:dmarc-feedback@example.com"2

You'd swap in your own domain. The same pattern works for the other two names.

Reading what comes back

For SPF, the standard's example is a TXT record whose text starts with the version tag, v=spf1.1 The SPF page walks through reading one, part by part. If you see two lines that both start that way, that's a problem to fix, not two valid records.

For DMARC, read the p= tag first. The DMARC page explains the three settings.

For DKIM, a good answer is a long text with a p= tag holding the public key. Empty results usually mean the selector name is wrong, or the record isn't published yet. How the records are added covers the delay.

An answer showing nothing at the DMARC name only means no DMARC record is published there. The standard says that when no record is found, receivers shouldn't apply DMARC to the message.2

A record being there isn't the whole story

A lookup shows what you've published. It doesn't show whether mail actually passes. For that, send a message to a mailbox you control and read the result in its headers. The steps are in Reading the authentication results in an email header.

Where the facts come from

  1. RFC 7208: Sender Policy Framework (SPF), IETF
  2. RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC), IETF
  3. RFC 6376: DomainKeys Identified Mail (DKIM) Signatures, IETF