MyIPScan

Email Security Tool

SPF Checker

Find the SPF TXT record for a domain and review common policy signals. This does not replace a full mail-flow or deliverability diagnosis.

Check SPF

Enter a domain to check SPF.
Technical response details (optional)
Direct answer

SPF Checker: the short answer

An SPF record is a TXT record starting v=spf1 that lists the servers allowed to send mail for a domain and ends with a rule for everyone else (~all soft fail, -all fail). This checker reads the record and flags a missing or duplicated record and overly broad rules. A domain may publish only one SPF record, and more than 10 DNS lookups makes it fail.

What the results mean

A normal SPF policy starts with v=spf1. Broad mechanisms such as +all can be risky, while too many includes can hit SPF lookup limits.

How to use this tool

  1. Enter the organizational domain.
  2. Review whether exactly one SPF record exists.
  3. Check DMARC after SPF so receiver policy is also visible.

FAQ

Does SPF stop spoofing by itself?

No. SPF is one signal. DMARC alignment and DKIM also matter.

Is ~all bad?

Not automatically. It is a soft-fail policy and may be intentional during rollout.

Can this validate every include?

No. This first pass highlights the root SPF record and obvious structure signals.

How the report is built

Email domain diagnostics

Email checks connect MX, SPF, DMARC, optional DKIM selector records, PTR/rDNS, sender-IP context, blacklist context, and email-header evidence.

How these reports are structured, and how to share them safely
SummaryStart with a plain-language status for the public target.
Top issuesPrioritize the few findings that need attention first.
What passedShow expected public signals without turning them into a certification.
What needs reviewSeparate limited, unavailable, and review-worthy signals.
Why it mattersExplain the business, delivery, crawl, or implementation impact.
Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.
What this tool cannot checkThis does not send mail, inspect private mailboxes, guarantee inbox placement, or certify sender reputation everywhere.
Client-safe copyClient-safe copy should keep authentication findings and fixes while removing email local-parts, raw TXT payloads, raw sender IP details, and private mailbox context.
Monitoring beta (optional)Optional monitoring beta can compare MX, SPF, DKIM selector checks, DMARC policy, PTR/rDNS, and selected blacklist signals for approved domains.

Client-safe report

Share findings without leaking raw technical material

Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

About this checkWhat it checks, what it cannot, and how to read it

Check my email domain

What this checks

Public mail-domain records and pasted email-header signals such as MX, SPF, DMARC, DKIM selector context, and sender-route clues.

Limits

What this cannot check

It cannot guarantee inbox placement, inspect private mailboxes, or certify sender reputation everywhere.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.

Quick reference

SPF Checker: what this tool does

Finds SPF TXT records and highlights missing, duplicate, or broad SPF policy signals.

How to use

  1. Enter the sending domain.
  2. Check first that exactly one SPF TXT record exists: two is a hard failure at the receiver.
  3. Count the DNS lookups your includes will generate before you add another one.

What the result means

The result is the SPF TXT record published for that domain, read through /api/dns-lookup, with missing, duplicated and unusually broad policies flagged. SPF is a list of who may send for the domain; whether one message passes depends on the sending IP and the receiver's evaluation.

Limitations

  • Pass or fail is not decided here. SPF is evaluated per message against a real sending IP and envelope-from domain.
  • The record is read as published. Nested include and redirect chains are not expanded, so the ten-lookup limit is not counted for you.
  • SPF is one sender-authentication signal and is normally read alongside DKIM and DMARC rather than on its own.

More questions

Does SPF alone protect email?

No. SPF is one sender-authentication signal and should usually be paired with DKIM and DMARC.

What does SPF Checker do?

SPF Checker Finds SPF TXT records and highlights missing, duplicate, or broad SPF policy signals. Results are review signals with stated limits.

How should I use SPF Checker results?

Use the result to decide what to review next, make one change at a time, and retest in the same browser, network, domain, or provider context when possible.

What does SPF Checker not prove?

It does not prove that your mail passes SPF or reaches the inbox, and it does not expand nested include and redirect chains, so the ten-lookup limit is not counted for you.