By Touchbase Technologies · Published

SPF, DKIM and DMARC checklist: check DNS and a real message

A domain checker and a received-message header answer different questions. A DNS lookup can show whether a record is published. A test message can show which sending system and signature were actually used. You need both to understand a particular email path.

Start by listing the services that send for your business, then test one path at a time. Do not treat a green result as proof that an address exists, a recipient wants the email or a message will reach the inbox. Reviewed November 8, 2026.

A business owner and email administrator inspect an envelope, a signature seal and a separate key at a mail workbench

Separate the three checks

SPF concerns the sending infrastructure authorized for a domain used in the SMTP transaction. DKIM concerns a cryptographic signature attached by a sending service. DMARC connects authentication results to the visible From domain through alignment and publishes the domain owner’s policy. A single “email verified” label does not describe these different checks.

CheckWhere to look firstUseful question
SPFRelevant domain’s DNS TXT records and the received headerWas this sending path authorized?
DKIMProvider settings, signature selector and matching DNS recordDid this message carry a valid signature?
DMARCVisible From domain, authentication results and DMARC recordDid an authenticated identity align with the From domain?

The practical sequence below combines provider instructions with an original troubleshooting worksheet. Use the exact values supplied by your own provider. A record that works for a different organization can omit your real senders or authorize infrastructure you do not use.

1. Make a sender inventory

List normal employee mail, newsletters, CRM messages, receipts, support replies and any website service that sends using your domain. Note the provider, purpose, visible From address, administrator and location of the provider’s setup instructions.

Google’s SPF setup guide stresses identifying all of the organization’s senders before determining its SPF record. Use that as an inventory exercise rather than copying a record from the first tutorial you find. A website form, for example, may be handled by a different service from employee email.

For each system, send a clearly labelled test to a mailbox you control. Record which action produced it and when. Do not send a troubleshooting batch to prospects or customers simply to see what happens. If a path cannot produce a controlled test, resolve access to that path before declaring it configured.

2. Read SPF at the correct hostname

On a machine with the `dig` DNS utility, the basic lookup is `dig TXT example.com`. Replace the reserved example domain with the hostname you intend to check. The relevant SPF policy is a TXT value beginning `v=spf1`; unrelated TXT records can legitimately be present too.

SPF evaluates an SMTP identity, which may be different from the visible From address. Read the test message’s authentication results and provider instructions to identify the relevant domain. Querying only the branded homepage domain can miss a provider-managed return-path domain.

RFC 7208 defines SPF’s record-selection and DNS-lookup rules. Multiple applicable SPF records at the same name are an error; publishing a second record is not a reliable way to add a sender. SPF also limits DNS-querying terms, including nested lookups. Counting visible `include` strings alone is not a complete evaluation.

Before editing, save the current values and identify the DNS zone you actually control. Ask the domain or mail administrator to reconcile the full sender inventory into the appropriate policy. After a change, query again and retest the affected sending paths rather than assuming a saved settings screen proves publication.

3. Get the DKIM selector from the sending path

A DKIM public key or provider-directed record belongs at a selector-specific hostname. The selector is not universally `google`, `default` or `selector1`. Follow the service’s instructions and inspect a message that the service actually sent.

For illustration, a signature containing `d=example.com; s=workspace;` points to the DNS name `workspace._domainkey.example.com`. The command `dig TXT workspace._domainkey.example.com` checks that example TXT location. Some providers use CNAME records, as shown in Microsoft 365’s DKIM instructions. Use your provider’s record type and targets rather than converting everything into TXT.

Google’s DKIM instructions describe publishing the provider-generated DNS information and starting authentication in its administration workflow. Publishing a value and enabling signing are separate tasks. Do not paste a private signing key into an online checker or a support message.

A missing signature is different from an invalid signature. First establish whether the expected sending service signed the test. Then investigate selector publication, configuration or changes to signed content. Record the actual result and service before making changes elsewhere.

4. Check DMARC and alignment

The usual lookup is `dig TXT _dmarc.example.com`, using the relevant domain. DMARC policies include monitoring, quarantine and reject dispositions. Choosing an enforcement policy requires understanding legitimate mail paths; this guide does not prescribe switching every domain to rejection immediately.

Google’s DMARC setup guidance explains using SPF and DKIM before applying DMARC and reviewing authentication behavior. Passing DMARC requires a qualifying SPF or DKIM pass with the necessary alignment to the visible From domain. A bare SPF pass for an unrelated provider domain is not by itself proof of DMARC success.

For a fictional example, imagine `From: hello@example.com` while SPF passes for a provider-managed bounce domain. If DKIM also passes with an aligned signing domain, DMARC can pass through that DKIM path. If neither successful identity aligns, the existence of a DMARC TXT record does not solve the mismatch. Provider-managed custom return paths and signing domains must be configured using that provider’s supported process.

5. Read the received test message

In Gmail on the web, open the received message and use the menu beside Reply to choose Show original, as described in Gmail’s header guide. Review the receiver’s authentication results and the domains involved. Other mail clients expose headers through their own menus.

Capture a small worksheet for each path:

EvidenceExample note to record
Sending actionTest receipt generated from the store
Provider and timeNamed service; actual test timestamp
Visible From domainThe domain a recipient sees
SPF result and evaluated domainWhat this receiver reported
DKIM result, signing domain and selectorWhat signed this specific message
DMARC resultThe receiver’s reported result
Next actionOwner, configuration to review and retest date

The entries above are field descriptions, not a fabricated successful test. Keep headers private where they contain personal addresses, internal routing or identifiers. Share only the material needed with the relevant administrator or provider.

A worked troubleshooting sequence

A fictional small shop uses one service for staff mail and another for purchase receipts. Staff tests pass, but the receipt test lacks the expected DKIM signature. The team initially assumes the whole domain is broken because a generic checker shows an authentication warning.

The inventory makes the problem smaller. The employee path is recorded as working for the controlled test. The store operator checks the receipt provider’s signing settings and discovers that its requested selector record was never published. The administrator publishes the exact provider-directed value, completes that provider’s signing step and sends a new test receipt.

The team then records the new header results, including DMARC alignment. It does not conclude that all future receipts will arrive in every inbox. It has established better evidence about one sending path and can repeat the same process for the newsletter service.

Keep sending quality separate from authentication

Authentication does not replace permission, relevant content, functioning unsubscribe handling or sensible sending limits. It also does not validate the recipient’s mailbox. A correctly authenticated message can still bounce because the recipient address is wrong, or be filtered for reasons beyond these DNS checks.

Avoid promising that a warm-up service or a separate domain will guarantee delivery. Review the actual provider requirements and your real sending behavior. For list and message preparation, use the prospect evidence checklist and reviewed cold-email examples.

Touchbase can support contact research, reviewed emails and campaign organization. Connecting a mailbox does not remove the need to configure the actual sending provider and domain correctly. Use your provider’s current instructions for the path you choose.

If you consider Touchbase for the follow-up work, review the current Free and paid plan allowances against the tasks you need.

Questions

Can I check DKIM with only a company domain?

You usually also need the selector or the provider’s configuration information. A guessed selector that returns nothing does not prove the domain never signs email. Use a real signature or the provider’s settings.

Does an SPF or DKIM checker verify my customer list?

No. Sender authentication and recipient-mailbox validation are different checks. Keep their results and any uncertainty separate in your workflow.

What does a successful test establish?

It establishes what the chosen receiver reported for that message and sending path. Keep the test details, investigate failures and repeat after relevant changes. It is not an inbox-placement guarantee.

Prepared with AI assistance and checked against the sources linked in this guide.