Skip to content

What a result looks like

Findings are sorted by severity. Where a check can suggest a fix, a warning comes with the record or header line to paste and a Re-check button, so fixing it takes one round trip.

Domain and network checks run on our server; formatters and decoders run in your browser and work offline.

DMARC check for example.com

Needs attention

Findings

  1. Warning: Policy is p=none (monitoring only)

    Receivers deliver mail that fails DMARC as usual. This is the right first step while you read aggregate reports, but it does not stop spoofing. Once legitimate senders pass SPF or DKIM alignment, move to quarantine, then reject.

    Next step: quarantine
    _dmarc.example.com. IN TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"
    Read the DMARC guide
  2. Passed: Aggregate reports go to dmarc@example.com

    Receivers send daily XML summaries of mail using your domain.

Sample result for the record v=DMARC1; p=none; rua=mailto:dmarc@example.com. Check your own domain.

Why people use XGM

  • Nothing is gated. Every tool and full report runs without an account, and so do exports, share links and history.
  • Warnings come with the fix. DMARC, SPF and header checks give the record or header line to paste, with a Copy button.
  • Results are portable. JSON, CSV, Markdown, print to PDF, a permanent link and a snapshot you can compare later.
  • 15 tools run in your browser. Formatters, decoders and generators never upload what you paste, and work offline.
  • It works from scripts and AI agents. A free API returns JSON or plain text for curl, and an MCP server lets Claude Code run checks.

From the guides