Guard: know when your email configuration changes
A daily automated scan of one domain, with every change recorded. £7 a month.
Cancel any time through Stripe. No contract, no minimum term.
Why configuration drifts
Email authentication is not a thing you finish. A provider adds an include to their own SPF record and your lookup count crosses ten. Someone sets up a new marketing platform and authorises it in a way that breaks alignment. A DNS change during an unrelated migration drops a record. A DKIM key gets rotated on one side only.
None of these announce themselves. You find out weeks later, from a customer who says they never got the invoice.
What Guard watches
- SPF record changed, become invalid, or crossed the ten-lookup ceiling
- DMARC record changed, removed, or its policy weakened
- DKIM selector evidence changed, for selectors that can be monitored
- MX records or inbound provider changed
- MTA-STS and TLS-RPT changed
- Configuration health moved materially in either direction
Every run is recorded as an immutable event with the records as they were, so the history answers "when did this change, and what was it before" rather than just "something is wrong now".
Notifications
Outbound email is not yet configured on this deployment. Guard records every change on your dashboard, and does not email you. This is stated here rather than promised and quietly not delivered; when a transport is configured this page will say so.
What Guard is not
It is not DMARC aggregate report processing. Your reports go to whatever address you put in your own
rua tag, and this product does not collect them. It is not inbox placement testing, and it does not
monitor blocklists.