Spoof Checker (DMARC/SPF) — Free Scan

Find domains that imitate your brand — before attackers use them.
Enter your brand or domain, and we’ll generate high-risk typo and homoglyph variants, then check which ones are active (MX/A/NS). Prioritize takedowns and defensive registrations.

Domain Spoofability Check

Instant domain-only check via DMARC/SPF. No email content required.

What this scanner does

  • Checks DMARC, SPF, MX, MTA-STS, and TLS-RPT records.

  • Flags weak or missing policies that make your domain easy to spoof.

  • Explains results in plain English with clear next steps.

  • Optional: email the report and book a free fix session with our team.

Privacy note: We never read your emails. This scan queries public DNS only.

Why domain spoofing matters

  • Executive fraud & invoice scams: Attackers impersonate your domain to trick staff or customers.

  • Brand damage & deliverability: Spoofed mail hurts trust and can land your real emails in spam.

  • Compliance & cyber insurance: Many standards expect DMARC enforcement or roadmap to it.

What we check

  • Enter your domain (e.g., example.com).

  • We query public DNS and run checks for DMARC/SPF/MX/MTA-STS/TLS-RPT.

  • You get a verdict with colour-coded risk and actions to remediate.

Frequently Asked Questions (FAQ) - Spoof Checker

  • Domain spoofing is when a threat actor forges the “From:” address to use your domain name, tricking recipients into trusting a malicious email.
  • Email spoofing is the broader tactic of falsifying sender identity. Domain spoofing is one form; others use lookalike domains or display-name tricks.

  • DMARC tells receiving mail servers to reject or quarantine messages that fail SPF/DKIM and don’t align with your domain. With p=reject and strict alignment, most forged mail using your domain is blocked.
  • No. The scanner only queries public DNS records.
  • Keep it simple, include all senders, and end with -all. Example:
    v=spf1 include:_spf.google.com include:sendgrid.net -all
  • Some providers block unauthenticated mail anyway. Your domain posture still needs improving to protect broadly, not just at Gmail.
  • Yes—enable DKIM for Google/Microsoft and any ESP/marketing tool so messages can pass DMARC via DKIM alignment.
  • Yes—publish separate DMARC for subdomains or enforce parent sp= policy. We’ll advise the cleanest layout.
  • Often 2–4 weeks with proper monitoring and sender inventory. We can accelerate if your sender set is simple.