A real report, start to finish.

OUTBOUND DOMAIN HEALTH & DELIVERABILITY AUDIT
Domain: example.com
Overall grade: B

=== MX (mail routing) ===
  0 .

=== SPF ===
  "v=spf1 -all"

=== DKIM (common selectors checked) ===
  selectors with a validated key: none found

=== DMARC ===
  "v=DMARC1;p=reject;sp=reject;adkim=s;aspf=s"

=== ISSUES FOUND ===
  1. No DKIM record with a non-empty key found under common selectors (checked: default, selector1, selector2, google, k1, k2, s1, s2, mail, smtp, mandrill, zoho, zmail, dkim, mx, email, key1, key2, fm1, fm2, fm3, protonmail, protonmail2, mailjet, sendgrid, sib, mc1, amazonses, postmark, pm, hs1, hs2, 20230601, 20240101). Either DKIM is not configured, the key has been revoked (a record with an empty p= value, which this scan correctly does NOT count as configured), or it uses a non-standard selector this scan didn't check.
  2. No rua= aggregate-report address in the DMARC record — there is no visibility into who is failing SPF/DKIM checks for this domain.

=== NOTES (not scored as issues, worth reading) ===
  1. MX is explicitly null (RFC 7505: '0 .') — this domain is configured to send only and receive no mail. Common and correct for a dedicated sending domain; confirm it is intentional and not a receiving domain someone forgot to configure.

Known limitation: SPF nested-include lookups are not recursively counted (see module docstring). This report is generated by real-time DNS lookups against public records only. No email was sent, no account was accessed, and no third party was contacted to produce this report.

First 10 customers: FOUNDING10 takes EUR 50 off. Full refund if the audit finds nothing actionable. See all options.