The path

From blind spot to enforced policy

There's no shortcut around reading your own mail traffic, but the path itself is straightforward. Five steps, in order — skipping ahead is the most common way domains break their own legitimate mail.

  1. 01Check your domain

    Run the free lookup to see what SPF and DMARC records are actually published right now. Most domains turn up with neither — that gap is invisible until you look for it.

    Check a domain →
  2. 02Understand what’s missing

    SPF, DKIM, and DMARC each verify something different about a message, and DMARC is what ties them together into a policy. The guide covers what each one actually does, in plain language.

    Read the guide →
  3. 03Publish a monitoring policy

    Add a DMARC record with p=none and an rua= address. This enforces nothing — it just tells mailbox providers where to send aggregate reports, so every source sending mail as your domain starts showing up.

  4. 04Read the reports, fix what’s failing

    Aggregate reports arrive as XML, not a dashboard. Until the monitoring tool here can parse them for you, reading them directly (or with another report analyzer) works in the meantime — the goal is a complete list of legitimate senders, all passing.

    How to read a report →
  5. 05Move to enforcement

    Once reports are clean, move from p=none to p=quarantine and eventually p=reject — in stages, watching reports at each step so legitimate mail never gets silently blocked.

    See the enforcement ladder →

Start with step one

It takes a few seconds and tells you exactly where your domain stands today.

Check your domain