Skip to content

Check a domain's SPF, DKIM and DMARC in one call

Send a sending domain and get its MX, SPF, DKIM and DMARC records read from DNS, graded from 0 to 100, with a list of issues and how to fix each one. 2 credits per lookup.

2 creditsValidateCSV bulkMCP
POST/v1/email-authentication-check
{
  "success": true,
  "data": {
    "domain": "example.com",
    "score": 62,
    "mx": {
      "found": true,
      "records": [
        {
          "host": "mx1.example.com",
          "priority": 10
        },
        {
          "host": "mx2.example.com",
          "priority": 20
        }
      ]
    },
    "spf": {
      "found": true,
      "record": "v=spf1 include:_spf.example.com include:mail.example.com ~all",
      "dns_lookups": 11,
      "valid": false
    },
    "dkim": {
      "found": true,
      "selectors": [
        "s1",
        "default"
      ]
    },
    "dmarc": {
      "found": true,
      "record": "v=DMARC1; p=none; rua=mailto:dmarc@example.com",
      "policy": "none"
    },
    "issues": [
      {
        "code": "spf_too_many_lookups",
        "severity": "high",
        "message": "SPF needs 11 DNS lookups. The limit is 10.",
        "fix": "Remove unused include mechanisms or replace them with ip4 and ip6 entries."
      },
      {
        "code": "dmarc_policy_none",
        "severity": "medium",
        "message": "DMARC is published with p=none, so mail that fails authentication is still delivered.",
        "fix": "Review your aggregate reports, then move to p=quarantine."
      }
    ]
  },
  "meta": {
    "credits_used": 2,
    "credits_remaining": 999,
    "cached": false,
    "request_id": "req_8f3a2c1e9b7d"
  }
}
[01/Response]

What you get back

The fields most teams branch on. The full response is in the sample on this page and in the API reference.

scoreScoreA grade from 0 to 100 for the domain's overall authentication setup.
mx.foundMXWhether the domain publishes MX records, with the hosts listed next to it.
spf.recordSPF recordThe SPF TXT record exactly as published.
spf.dns_lookupsSPF lookupsHow many DNS lookups the record triggers. More than 10 breaks SPF.
dkim.selectorsDKIM selectorsThe common selectors that returned a public key for this domain.
dmarc.policyDMARC policynone, quarantine or reject, taken from the published DMARC record.
issuesIssuesEach problem found, with a severity, a description and the fix.
[02/Capabilities]

What Email Authentication Check does

01

Read from public DNS

Everything in the result comes from DNS queries against the domain. Nothing is installed, no email is sent, and you can check domains you do not control, such as a client's or a vendor's.

02

SPF parsed, not only found

The lookup follows include and redirect mechanisms and counts the DNS lookups they trigger. Records that go over the limit of 10 are flagged, because receivers treat them as a permanent error.

03

DKIM across common selectors

DKIM keys live under selector names that DNS does not list. The check probes the selectors mail platforms commonly use and reports the ones that publish a key.

04

Issues with a fix attached

Each problem comes with a severity, a plain description and the change that resolves it. A DMARC policy of none, for example, is reported with the step toward quarantine or reject.

[03/Try it]

See the response before you sign up

Fill in the request and run it. The dashboard has the same form, plus history, bulk upload and live data.

POST /v1/email-authentication-check2 credits

The sending domain, without a protocol.

Preview mode: this page returns a sample response so you can see the shape of the data. Create a key to run it on live data.

Response

Fill in the field and run the lookup to see what comes back.

[04/Integrate]

One POST request

Send JSON with a Bearer key. The same key works for all 79 products.

curl -X POST https://api.1lookup.dev/v1/email-authentication-check \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"example.com"}'
Endpoint
POST /v1/email-authentication-check
Base URL
https://api.1lookup.dev
Request
domain
Price
2 credits
Coverage
Global
Bulk
CSV upload and bulk API
Cache
Repeats within 7 days are free
Also via
Dashboard and MCP server (run_lookup)
[05/Use cases]

What teams use it for

Check your domain before a campaign

Run your sending domain and every subdomain you mail from. Fix the high-severity issues before volume goes out, not after messages start landing in spam.

Audit client domains at onboarding

Agencies and email platforms can grade a new customer's domain on day one and hand over a list of DNS changes to make.

Watch for record drift

DNS records get edited, and each new sending tool tends to add another SPF include. Check on a schedule and alert when the score drops.

Review vendor and partner domains

A domain with no DMARC record is easier to spoof. Check the domains that send you invoices and add the score to your vendor review.

DKIM is checked on common selectors only. A domain that signs with a custom selector can show DKIM as not found even when it is configured correctly.

[06/Cost]

2 credits

Credits come with your plan and work on every product. Requests that fail on our side are never charged. Beyond your plan, extra credits are pay as you go.

See pricing
PlanPer 1,000 creditsPer 1,000 lookups
Starter $29/mo$4.83$9.67
Growth $99/mo$3.96$7.92
Pro $299/mo$3.32$6.64
Scale $799/mo$2.66$5.33
[07/FAQ]

Email Authentication Check questions

What does the check look at?

MX records, the SPF record and its lookup count, DKIM keys on common selectors, and the DMARC record and policy. Each part feeds a score from 0 to 100.

Why is DKIM reported as not found when I have it set up?

DKIM selectors cannot be listed from DNS, so the check tries common selector names. If your provider uses a custom selector, the key exists but this lookup will not find it.

How many credits does a check use?

Two credits per domain. Results are cached for 7 days, so pass "fresh": true after you change a DNS record and want to confirm the fix.

Does a score of 100 guarantee inbox placement?

No. Authentication shows that mail is allowed to come from your domain. Placement also depends on sender reputation, content and how recipients engage, none of which DNS can show.

Do I need access to the domain?

No. The records are public, so any domain can be checked without verification or a DNS change. Fixing the issues does require access to the domain's DNS.

[ Validate ][ Enrich ]
[Get started]

Run Email Authentication Check on your own data

Starter is $29 a month for 6,000 credits, enough for 3,000 lookups a month.

[ Screen ][ Scrape ]