DNS & email monitoring
Know when a client's email DNS changes — before their invoices bounce
Each check takes a real DNS-over-HTTPS snapshot of SPF, DMARC, MX and NS records, compares it with the previous one and records what changed. Missing SPF, an SPF record over the 10-lookup limit, missing DMARC and missing MX open issues automatically; DMARC p=none is treated as a valid monitoring policy and logged as information.
What it does today
SPF parse + RFC 7208 lookup count
Include and redirect chains are followed to a safe bound to count DNS-querying terms.
Available nowDMARC policy, pct and reporting addresses
p=none is reported as monitoring mode, not as an error.
Available nowMX and NS snapshots with change detection
A dns_changed information issue lists the exact before/after values.
Available nowDKIM
Checked only for a selector you provide — we never guess selectors and call the result a failure.
Available now
What changes we catch
Typical incidents are a new email platform replacing MX records, a marketing tool adding a second SPF record, or someone removing _dmarc while cleaning up DNS. Each snapshot is stored with the raw record text, so you can show the client the exact value before and after.
DNS checks confirm that authentication records exist and are well-formed. They cannot guarantee inbox placement, which also depends on sender reputation and content, and we say so in every report.
Frequently asked questions
Try it on a real domain — free, no account needed.