Subscribe
Free tool

Email Sending Domain Checker

Enter a domain to see its SPF, DKIM and DMARC records, what each one means in plain words, and what to fix if you send through a HighLevel dedicated sending domain. The lookup runs in your browser. No email needed.

By Hamid Mazumder Checked against HighLevel docs on 8 sources

Selectors tried: google, selector1, selector2, k1, s1, s2, default, mail, dkim, mandrill, smtp, pic, krs, mx, mailo, email. HighLevel shows your exact DKIM host in Settings, Email Services, Dedicated Domain and IP; the selector is the part before ._domainkey.

What each record does

  • SPF lists the servers allowed to send email for the domain. HighLevel's SPF value typically includes its LC Email and Mailgun servers, and only one SPF record is allowed per domain, with at most 10 DNS lookups (Authentication Errors).
  • DKIM adds a signature to each email so receivers can check it came from you and was not changed. The public key sits at a selector under _domainkey. HighLevel says multiple DKIM records for the same domain are not supported on a dedicated sending domain (Dedicated Sending Domain).
  • DMARC tells receivers what to do when SPF and DKIM fail: p=none monitors, p=quarantine sends to spam, p=reject blocks. HighLevel suggests starting at v=DMARC1; p=none; and tightening once SPF and DKIM pass (DMARC).

Fixing it in HighLevel

  1. Go to Settings, Email Services, Dedicated Domain and IP and add a subdomain you use for nothing else, such as mg.yourbrand.com (Dedicated Sending Domain).
  2. Add the records HighLevel shows (SPF, DKIM, MX, CNAME and DMARC), or let it auto-configure supported DNS providers. For a subdomain, the host is only the subdomain part. On Cloudflare, set the records to DNS only (Add and Verify DNS).
  3. Remove any old SPF or MX records on that subdomain first. HighLevel's "Domain already pointing to email server" error means they are still there.
  4. Verify the domain, then set it as the default under Domain Configuration so no email falls back to shared sending (Assigning Domains).
  5. Send from an address on that domain. If emails still go out from someone's login email, read why HighLevel emails send from your login address.

Estimates, not guarantees. This is a snapshot of public DNS at the moment you check, read through a public resolver that may cache records for a while after you change them. Passing here does not guarantee inbox placement, and a DKIM key on a selector this tool did not try may still exist. HighLevel's own Verify domain check is the one that counts for your sending domain.

FAQ

What does this checker look up?

Three public DNS records: SPF (a TXT record starting v=spf1 on the domain), DKIM (TXT records at selector._domainkey on the domain, for a list of common selectors plus any you add) and DMARC (the TXT record at _dmarc on the domain). It explains what each one means and what HighLevel's articles say to fix.

Should I check my root domain or my sending subdomain?

Both, if you send through a HighLevel dedicated sending domain. HighLevel recommends a subdomain such as mg.yourbrand.com for sending, and the SPF and DKIM records it gives you live on that subdomain. DMARC can be set on the root domain and covers subdomains unless they have their own.

Why does it say no DKIM was found when I set it up?

DKIM keys sit under a selector name that only the sending service knows, and this tool can only try common ones. HighLevel shows the exact DKIM host in Settings, Email Services, Dedicated Domain and IP. Enter the selector part (the text before ._domainkey) in the extra selector box and check again.

How many SPF lookups are allowed?

10. HighLevel's authentication article says going over the limit causes a permanent error that can make SPF fail entirely. The checker counts include, a, mx, ptr, exists and redirect terms, and follows includes to estimate the total.

Can I have two SPF or two DMARC records?

No. HighLevel says only one SPF record and one DMARC record should exist per domain, and that a second one breaks authentication. Merge them into one record.

Is my domain sent anywhere?

Your browser sends the DNS questions to Cloudflare's public DNS resolver, or to Google Public DNS if Cloudflare does not answer. These records are public. Nothing goes to GHL Weekly and nothing is stored.

Related: HighLevel emails sending from your login email, and the usage cost calculator for what LC Email costs per thousand emails.

Sources

Checked against HighLevel docs on 30 Oct 2026. The Cloudflare and Google pages document the public resolvers this tool queries. How I check facts is on the editorial standards page.

  1. HighLevel Help Center: How to Set Up a Dedicated Sending Domain (LC Email) help.gohighlevel.com
  2. HighLevel Help Center: Add and Verify Domain DNS Records in HighLevel help.gohighlevel.com
  3. HighLevel Help Center: Email Authentication Errors - Fix SPF, DKIM, and DMARC Issues help.gohighlevel.com
  4. HighLevel Help Center: Email Authentication - DMARC help.gohighlevel.com
  5. HighLevel Help Center: Assigning Dedicated Sending Domains to Different Email Types help.gohighlevel.com
  6. HighLevel Help Center: Sending Priority - From Name & Address help.gohighlevel.com
  7. Cloudflare: DNS over HTTPS, JSON format developers.cloudflare.com
  8. Google Public DNS: JSON API for DNS over HTTPS developers.google.com