Three different layers of email authentication
SPF, DKIM and DMARC are often mentioned together, but each solves a different part of the problem. SPF identifies sending infrastructure allowed by a domain. DKIM provides cryptographic message signing. DMARC ties these signals to the domain visible in the From header and tells receivers how to handle failures.
SPF: authorized senders
An SPF policy is typically published as a TXT record that begins with v=spf1. It may include IP addresses, third-party includes and mechanisms such as mx. A missing record is not itself proof of email spoofing; it means no SPF policy was found at that name. More than one SPF policy at the same name is generally problematic.
DKIM: signed messages
DKIM signing uses a private key held by the sending system and a matching public key published in DNS, often at selector._domainkey.example.com. The selector is supplied by your mail provider; it is not necessarily default. Our DKIM Checker discovers records for a selector but does not authenticate an actual email message.
DMARC: alignment and policy
A DMARC record is published at _dmarc.example.com, usually beginning with v=DMARC1 and containing a policy such as p=none, p=quarantine or p=reject. Enforcement choices should be made after reviewing legitimate sending sources and authentication alignment.
A safe rollout
- List every platform that sends email on your behalf.
- Configure SPF and DKIM at each sending service.
- Monitor DMARC reports before moving to stricter enforcement.
- Review forwarding paths, subdomains and third-party marketing systems.
Checking for a DNS record is a starting point. Full deliverability depends on actual message headers, policy syntax, alignment, reputation and receiver decisions.
Standards: RFC 7208 (SPF), RFC 6376 (DKIM), RFC 7489 (DMARC).
Editorial note: This is general educational information, not a live audit. DNS behavior and provider policies can change, and results should be verified against authoritative sources.