Keep every Resend sending domain verified and signed
Every Monday, WebRun opens Resend, checks whether each sending domain is still verified, reads the SPF and DKIM records the platform expects, records the status of every domain in Airtable, and writes a fix list in Notion naming any record that is missing or wrong.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I check my Resend sending domains are still verified?
Every Monday WebRun opens Resend and checks each sending domain: whether it is still verified, and whether the SPF and DKIM records the platform expects are actually in place. WebRun records the status in Airtable and writes the fix list in Notion, so a DNS change never quietly kills a domain.
- A broken record is found before a campaign fails to send
- Every domain's state is dated and logged week after week
- The fix list names the record and where it belongs, not just the error
Built for engineering teams · growth engineers · SaaS founders · email 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
resend.comin a real browser with your saved login - no setup, no API keys. -
1
Resend - check domain verification
WebRun opens Resend to check domain verification. - Sign in to Resend and open the domains list for your account
- Read each domain's verification status and the DNS records it expects, including SPF and DKIM
- Note any record shown as missing, pending, or failing, and how long it has been that way
- Note which API keys exist and when each was last used, without ever reading or copying a key value
- Change nothing. WebRun reports the status and never edits DNS or re-verifies a domain
Done when Every sending domain has a verification status and a list of any broken records.
-
2
Airtable - log the weekly status
WebRun opens Airtable to log the weekly status. - Append this week's row per domain to the sending infrastructure base
- Record verified or not verified, the state of the SPF and DKIM records, and the date checked
- Keep the history so a domain that has been failing for weeks is obvious at a glance
Done when This week's status for every domain is logged in Airtable.
-
3
Notion - write the fix list
WebRun opens Notion to write the fix list. - Update the sending domains page with a short fix list for the week
- For each broken domain, name the record type, the expected value shown by Resend, and where it must be added
- Mark healthy domains as verified so the page reads as a full picture, not just problems
Done when The Notion page shows every domain's state and exactly what needs fixing.
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 edit our DNS records?
No. WebRun reads what Resend expects and reports what is missing. Adding or changing a record at your registrar is done by an engineer who can see the wider zone.
Does it read our API keys?
No. It notes which keys exist and when they were last used. It never opens, copies, reveals, or writes down a key value anywhere.
Will it tell me before a send actually fails?
Yes. It checks verification and record state weekly, so a domain broken by a registrar change is flagged on the next run rather than at the next campaign.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.