Free email tool

SPF, DKIM and DMARC checker

Check the DNS records mailbox providers look at before they deliver your mail. Gmail and Yahoo require bulk senders to have SPF and DKIM, a DMARC record and one-click unsubscribe on marketing mail. Outlook.com requires SPF, DKIM and DMARC from domains sending more than 5,000 emails a day, and recommends an easy unsubscribe link.

What each result means

We read the public DNS records of the domain you enter. We store nothing, and we can't see whether a given message passed. Pass means we found no problem. Each Warn and Fail comes with a fix; here is what they mean. SPF, DKIM and DMARC Explained covers how the three fit together.

SPF

We read the TXT record that starts with v=spf1 and count its DNS lookups, nested includes too.

  • Fail

    No SPF record found

    Add one TXT record. HighLevel's is v=spf1 include:mailgun.org ~all, on the sending subdomain.

  • Fail

    More than one SPF record

    SPF then returns a permanent error and can't pass. Merge every sender into one v=spf1 record.

  • Fail

    More than 10 DNS lookups

    Each include, a, mx, ptr, exists and redirect counts, nested ones too, and past 10, SPF can't pass. Drop senders you no longer use, or move one to its own subdomain, which gets its own 10.

  • Fail

    Allows any server (+all)

    End the record with ~all, which Google recommends, or -all.

  • Warn

    Ends with ?all, or has no all

    Servers you didn't list get a neutral result, which protects nothing. End with ~all or -all.

DKIM

We look for a key at selector._domainkey.yourdomain.com, for the selector you type or a list of common ones. We don't check the key's length; Gmail and Yahoo require at least 1024 bits.

  • Warn

    No key for common selectors

    Type your provider's selector and check again.

  • Fail

    No key for the selector you gave

    Check the spelling, and that the host name wasn't doubled (step 4 below).

DMARC

We read the TXT record at _dmarc on the domain you enter.

  • Fail

    No DMARC record found

    Gmail and Yahoo require one from bulk senders. Google's starting record is v=DMARC1; p=none; rua=mailto:[email protected], with your own report address. On a subdomain, check the root domain too: receivers fall back to its record.

  • Fail

    More than one DMARC record

    Receivers then apply no DMARC policy at all. Keep one, and put several report addresses in its rua= tag, separated by commas.

  • Fail

    No valid p= policy

    p= is required, right after v=DMARC1: none, quarantine or reject.

  • Warn

    Policy p=none

    Meets the Gmail and Yahoo minimum, but blocks nothing. Google suggests a week of reading reports, then p=quarantine for a small share of mail, raised to 100%.

  • Warn

    No rua= address

    You get no reports. Google recommends always including rua=.

Each DMARC result also names the alignment mode. Relaxed, the default, lets replies.yourdomain.com align with a From address at yourdomain.com. Strict (adkim=s, aspf=s) needs an exact match, and Google warns it can get subdomain mail rejected or sent to spam. Google's example record is strict, so drop those tags if you send from a HighLevel subdomain with a From address on your root domain.

MX

We look up the domain's MX records.

  • Warn

    No MX record

    Replies and bounces to the domain may fail. HighLevel's setup adds two MX records.

Sending from HighLevel

By default, HighLevel (GoHighLevel, or GHL) sends email from shared domains, and recipients can see HighLevel's servers in a "sent via" line. A dedicated sending domain on LC Email sends as your own domain. The steps, from HighLevel's setup guide:

  1. 1

    In the sub-account, open Settings > Email Services > Dedicated Domain and IP, and click Add Domain.

  2. 2

    Enter a subdomain such as replies.yourdomain.com. HighLevel recommends one, and requires one if your root domain gets mail through Google Workspace or another provider.

  3. 3

    Click Add & Verify to see the five DNS records.

  4. 4

    Add them at your DNS host, copying each value from HighLevel. In the host field, enter only the prefix, such as replies: a full name gets doubled and fails verification.

  5. 5

    Click Verify Domain. Changes can take up to 24 hours, or 48 at some DNS hosts.

  6. 6

    If your root domain has no DMARC record, add one at _dmarc. The five records don't include it. HighLevel's Google and Yahoo article starts with v=DMARC1; p=none;.

  7. 7

    Check the subdomain above with its DKIM selector, then your root domain.

For replies.yourdomain.com, HighLevel's setup guides list these records:

TypeHostValue
TXTSPFrepliesv=spf1 include:mailgun.org ~all
TXTDKIMCopy the host and value from HighLevel
MXrepliesmxa.mailgun.org, priority 10
MXrepliesmxb.mailgun.org, priority 10
CNAMEemail.repliesmailgun.org

The DKIM host and value are unique to each domain. In HighLevel's example for helpdesk.companyname.com, the host is mx._domainkey.helpdesk, and the part before ._domainkey, mx, is the selector to type above. We don't look up the CNAME.

Keep your From address on the same root domain: HighLevel's sending guide accepts [email protected] or [email protected] for replies.company.com. If a sub-account sends through its own SMTP provider instead of LC Email, use that provider's records.

What Gmail, Yahoo and Outlook require

  • Gmail: every sender needs SPF or DKIM. Bulk senders, at about 5,000 messages a day to personal Gmail accounts, need both, plus DMARC (p=none is enough), a From domain aligned with one of them, one-click unsubscribe on marketing mail and a spam rate below 0.3%.
  • Yahoo: the same for bulk senders, and DMARC must pass. Yahoo publishes no volume threshold.
  • Outlook.com: domains sending more than 5,000 emails a day must pass SPF and DKIM and publish DMARC of at least p=none, aligned with one of them. Failing mail can be junked or rejected with 550 5.7.515.

HighLevel says it adds a one-click unsubscribe header to every email except 1:1 emails. We read DNS, not headers: to see whether a message passed, send yourself a test at a Gmail address and choose Show original, as HighLevel suggests. More in our guides to Gmail and Yahoo, Outlook.com and one-click unsubscribe.

Questions

What DNS records does HighLevel (GoHighLevel) need for a dedicated sending domain?

Five, in HighLevel's setup guides: an SPF TXT record (v=spf1 include:mailgun.org ~all), a DKIM TXT record unique to your domain, MX records for mxa.mailgun.org and mxb.mailgun.org, and a CNAME to mailgun.org. Copy the exact values from HighLevel's DNS records screen.

Does HighLevel need a DMARC record?

The five setup records don't include one, but HighLevel's guides tell you to add a TXT record at _dmarc, starting with v=DMARC1; p=none;. Gmail and Yahoo require DMARC from bulk senders. A record on your root domain also covers subdomains that have none.

Should I use my root domain or a subdomain in HighLevel?

A subdomain, such as replies.yourdomain.com. HighLevel recommends one, and requires one if your root domain already gets mail through Google Workspace or another provider, since the MX records would conflict. Your From address can stay on the root domain.

Which domain should I enter in the checker?

Your HighLevel sending subdomain with its DKIM selector, for SPF, DKIM and MX. Then your root domain, for DMARC: we read DMARC only on the domain you enter, while receivers fall back to the root domain's record.

Where do I find my DKIM selector in HighLevel?

On HighLevel's DNS records screen, at the start of the DKIM record's host name, before ._domainkey. In HighLevel's example, mx._domainkey.helpdesk, the selector is mx. Leave the field blank and we try common selectors.

Why won't HighLevel verify my sending domain?

HighLevel's guides name three common causes: a host name typed in full, which doubles the domain; old MX or SPF records, which trigger the error "Domain already pointing to email server"; and a wildcard DNS record, which you can remove until the domain verifies, then add back. Changes can also take up to 48 hours to show.

Why does HighLevel warn about my p=reject DMARC policy?

Without a dedicated sending domain, HighLevel sends through a shared domain, and it warns that most inbox providers will then reject mail from a From domain with a strict DMARC policy such as p=reject. The fix is a dedicated sending domain. HighLevel offers p=none only as a stopgap, since it weakens protection against spoofing.

Sources

HighLevel, Google, Yahoo and Microsoft update these pages, so check them before you rely on them. Not legal advice.