Skip to content

Software • AI • Cloud • Teams

Contact
AnyPlace — Global IT Services Company

HomeFree ToolsEmail Auth Checker

Domain & Infrastructure • Deliverability

Email Authentication SPF · DKIM · DMARC Checker

One pass over your domain's SPF record, _dmarc policy, DKIM selectors and MX servers — graded A to F, with a copy-ready DMARC starter record.

Every query runs from your browser against Google Public DNS. We never receive your domain, and nothing is logged by us — the audit is between you and the resolver.

Live DNS-over-HTTPS

Google Public DNS, in real time.

4 Record Checks

SPF, DMARC, DKIM, MX.

A–F Grade

Clear spoofing-protection score.

Zero Logging

Queries never touch our servers.

Live DNS Authentication Audit

Check Your Domain's Spoofing Protection

We query SPF, DMARC, DKIM selectors and MX records live over DNS-over-HTTPS — nothing is sent to our servers.

Try:

Enter a domain and run the audit to see SPF, DMARC, DKIM and MX results.

Spoofing Protection Grade
—

Run an audit to grade your domain

Score 0 / 8

Starter DMARC record

—

SPF (Sender Policy Framework)Not checked

Lists which servers may send mail for your domain. Lookups are counted against the 10-DNS-lookup limit.

—

DMARC (Anti-Spoofing Policy)Not checked

Instructs receivers what to do when SPF or DKIM alignment fails (none / quarantine / reject).

—

DKIM (Cryptographic Signatures)Not checked

Probes 8 common selectors (default, google, selector1, selector2, k1, s1, s2, mail). Providers using custom selectors need a manual check.

MX (Mail Receiving Servers)Not checked

Confirms the domain actually receives email. No MX means nobody can reply — and SPF/DKIM matter less than fixing that first.

—

What happens next:

Stage DMARC from p=none to p=reject once reports show only legitimate senders — we roll this out for clients without interrupting outbound mail.

Quick Summary / Direct Answer

What Is Email Authentication, and Why Does It Decide Your Inbox Placement?

SPF (RFC 7208) lists which servers may send mail for your domain; DKIM (RFC 6376) cryptographically signs each message so receivers can verify it was not altered; DMARC (RFC 7489) ties them together and tells receivers what to do when authentication fails — accept (p=none), spam (p=quarantine), or reject (p=reject). Together they stop third parties from spoofing your domain and, since February 2024, Google and Yahoo require bulk senders to have aligned SPF/DKIM plus a DMARC policy or face rejection and spam-folder placement.

1. The Four Records This Audit Checks — and Where They Live

Each check is a plain DNS query anyone can replicate with dig. The tool does it over encrypted DNS-over-HTTPS so the audit works from any network:

RecordDNS NameExample ValueFailure Mode If Missing
SPF (TXT)yourdomain.comv=spf1 include:_spf.google.com -allAny server can claim your domain; receivers have no allow-list to check.
DMARC (TXT)_dmarc.yourdomain.comv=DMARC1; p=reject; rua=mailto:dmarc@…Failures are ignored — phishing as your domain reaches inboxes.
DKIM (TXT)selector._domainkey.yourdomain.comv=DKIM1; k=rsa; p=MIIBIjAN…Messages carry no verifiable signature; DKIM alignment in DMARC fails.
MXyourdomain.com10 aspmx.l.google.comThe domain cannot receive mail at all — replies and OTPs bounce.

2. The Safe DMARC Rollout: none → quarantine → reject

Jumping straight to p=reject is how companies block their own mail — CRMs, invoicing tools and newsletters often send outside your SPF. Stage enforcement instead:

  • Stage 1 — Monitor (2 weeks): publish p=none with a rua= aggregate report address. Collect the reports and confirm every legitimate sender passes alignment. The starter record in the tool is exactly this.
  • Stage 2 — Quarantine ramp (2–4 weeks): move to p=quarantine and start at pct=25, raising weekly as reports stay clean. Failing mail lands in spam instead of vanishing, so problems surface without breaking delivery.
  • Stage 3 — Enforce: set p=reject with pct=100. Only once SPF hard-fails (-all) and every sender is aligned should you do this — at that point spoofed mail for your domain stops at the edge.

3. Google & Yahoo's Bulk-Sender Rules (Effective February 2024)

If you send roughly 5,000+ messages a day to Gmail addresses, meeting these is mandatory — failures get mail rejected or routed to spam regardless of your content:

  • Authenticate with SPF or DKIM, aligned with the visible From domain — the signing domain must match what recipients see, or alignment fails even when both records "exist".
  • Publish a DMARC policy at p=none or stronger — even monitor-only satisfies the rule, which is why starting the rollout costs you nothing.
  • One-click unsubscribe on marketing messages, honoured within two days, plus a clearly visible From address and your physical mailing address.
  • Keep spam rates low — Gmail publicly states a spam-rate ceiling (below roughly 0.3%, and never above 0.1% for strong deliverability) measured in Postmaster Tools.
Security Advisory

Need DMARC Enforced Without Breaking Mail?

We audit every legitimate sender, flatten SPF inside the 10-lookup limit, verify DKIM across providers and stage DMARC to p=reject with aggregate reporting — zero outbound interruption.

Companion Tool

WHOIS & DNS Zone Inspector

Inspect the full zone — A, AAAA, NS, TXT and nameserver lifecycle — when a delivery problem goes beyond email records.

Inspect DNS Zone
Knowledge Base

Email Authentication FAQs

SPF mechanics, DMARC enforcement staging, DKIM selectors and the bulk-sender rules that make this mandatory.

What does this email authentication checker actually test?

It performs live DNS-over-HTTPS queries against Google Public DNS straight from your browser: the TXT records on your domain (SPF), TXT records on _dmarc.yourdomain (DMARC), TXT records across eight common DKIM selectors, and your MX records. Nothing is sent to our servers and no queries are logged by us — the results you see are resolved in real time by public DNS resolvers.

What is SPF, and what does -all versus ~all mean?

SPF (Sender Policy Framework, RFC 7208) publishes a TXT record listing which servers may send email for your domain. The ending mechanism is the enforcement flag: -all (hard fail) tells receivers to reject mail from unlisted sources, ~all (soft fail) marks it suspicious but deliverable, and ?all (neutral) provides no protection at all. A missing SPF record or a second SPF record on the same domain breaks authentication entirely — most receivers then treat the mail as unauthenticated.

Why do Google and Yahoo require DMARC for bulk senders?

Since February 2024, Google and Yahoo require bulk senders (roughly 5,000 messages per day) to authenticate mail with SPF and DKIM aligned with the visible From domain, publish a DMARC policy, and support one-click unsubscribe. Mail that fails these checks is more likely to be rejected or routed to spam. Even below that volume, a DMARC policy is the only reliable way to stop third parties from spoofing your domain.

My domain has no DMARC record — how bad is it?

Anyone can send email appearing to come from your domain today: no receiver is instructed to do anything about failures. That is the single most common spoofing exposure we find. The fix takes minutes: publish a monitoring record (p=none) first so you can see who legitimately sends mail on your behalf, then move to enforcement once your report shows no unintended senders.

What is the safest way to roll out DMARC enforcement?

Stage it: start with p=none and a rua aggregate report address for two weeks, then move to p=quarantine with pct=25 and increase weekly as reports stay clean, and finally p=reject once every legitimate sender (your CRM, invoicing tool, support desk, newsletter platform) passes alignment. Jumping straight to p=reject without checking reports is how companies break their own outbound mail.

You only found DKIM on one selector — is that wrong?

No. Each mail provider chooses its own selector name (Google commonly uses google, Microsoft 365 uses selector1 and selector2, many others use default or k1). A domain signing with one provider will only expose that provider's selector. We probe eight of the most common names; if your provider uses a custom selector it will not be in our list even though DKIM is correctly configured — check your mail provider's DNS instructions to confirm.

What is the 10-lookup limit in SPF, and why does this tool count includes?

RFC 7208 caps an SPF evaluation at 10 DNS lookups across include, a, mx, ptr and redirect mechanisms. Every include: you add consumes one (plus lookups inside it), and exceeding 10 causes an SPF permerror — receivers then treat SPF as failed, hurting deliverability. Our checker counts the includes in your record and warns you before you cross the limit, which commonly happens when teams keep stacking marketing tools without flattening the record.

Can AnyPlace set up SPF, DKIM and DMARC for our domain?

Yes. Our infrastructure and security engineers audit every legitimate sender, flatten SPF within the 10-lookup limit, verify DKIM across your mail providers, and stage DMARC enforcement to p=reject with aggregate reporting — without interrupting your outbound mail. Send us your domain through the contact form and we will return a rollout plan.

Content last reviewed October 2026.

TELL US ABOUT YOUR PROJECT

Tell Us What to Build, Fix or Modernize

Send a short brief. We reply within 12 hours with clarifying questions and a discovery quote — no retainers, no spam.

What Happens Next

1. We review and ask questions2. Discovery scope and price3. Build or squad starts
Reply in 12 hours NDA available on request contact@anyplacehub.com

Request a Discovery Quote

Share your goals and timeline. NDA signed first if needed.

12-hour response

Your details stay with us — never shared, never spammed. Reply within 12 hours. Prefer writing directly? Email contact@anyplacehub.com