Catch a sending domain whose records stopped verifying
Every Monday, WebRun opens Mailgun, checks the verification state of the DNS records on every sending domain, notes any SPF, DKIM or tracking record that stopped verifying, opens a Trello card for each failure, and sends your team the audit on WhatsApp before deliverability suffers.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I check my email sending domain records still verify?
WebRun opens Mailgun every Monday and checks the verification state of the DNS records on every sending domain, looking at the SPF record, the DKIM record and the tracking CNAME separately. It opens a Trello card for each failure and sends the audit to your team on WhatsApp, before a DNS change hurts deliverability.
- A broken SPF or DKIM record is found the week it breaks
- Live sending domains are separated from dormant ones
- Each failing record gets a card with the expected value attached
Built for email engineers · growth teams · SaaS platforms · marketing operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.mailgun.comin a real browser with your saved login - no setup, no API keys. -
1
Mailgun - check every sending domain's records
mailgun.com
WebRun opens Mailgun to check every sending domain's records. - Open Mailgun and list every sending domain on the account
- Read the verification state of each domain's DNS records
- Check the SPF record, the DKIM record, and the tracking CNAME individually rather than the domain as a whole
- Note which domains are actively sending, so a failure on a live domain is separated from a dormant one
Done when Every sending domain has a per-record verification result and a sending status.
-
2
Trello - open a card per failing record
trello.com How to Automate Trello
WebRun opens Trello to open a card per failing record. - Open a card on your engineering board for each record that failed to verify
- Name the domain, the exact record type, and the expected value shown in Mailgun
- Put live sending domains at the top of the list, dormant ones below
- Update the existing card instead of opening a duplicate when a failure carries over from last week
Done when Every failing record has a Trello card with the domain and the record type.
-
3
WhatsApp - send the audit to the team
whatsapp.com How to Automate WhatsApp
WebRun opens WhatsApp to send the audit to the team. - Post the audit to your internal engineering group: domains verified, domains failing, records affected
- Lead with any live sending domain whose authentication broke
- Link the Trello board so the fix has somewhere to be tracked
- Keep it internal. WebRun never contacts a DNS provider or a recipient
Done when The engineering group has this week's sending domain audit.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change any DNS records?
No. WebRun reads the verification state Mailgun reports and writes it up. Editing a DNS record, adding a domain, or changing a sending setting is left entirely to your engineers.
Does it send any test emails?
No. Nothing is sent from your sending domains during the audit. WebRun only reads record verification status, so your reputation and volume are untouched.
Why check each record separately?
Because a domain can look fine overall while one record quietly fails. Checking SPF, DKIM and the tracking CNAME individually catches the failure that starts routing mail to spam.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.