DNS Verification
Understand how DNS verification supports domain readiness for SendFlow Email delivery.
On this page
Overview
DNS verification helps SendFlow teams keep domain readiness and confidence before Email campaigns go live organized inside one workspace instead of scattering setup and campaign work across disconnected tools.
Use this guide as a practical operating reference for admins, staff, and campaign managers who need repeatable workflows.
What to manage
The goal is to keep the workspace readable for the whole team while making sure the data, setup, and delivery flow stay accurate.
When ownership is clear, SendFlow becomes easier to scale across audiences, templates, campaigns, and sending infrastructure.
- Track which domains are verified and which are pending.
- Coordinate DNS changes with whoever owns the domain.
- Avoid using unverified setup for live traffic.
- Keep verification history visible to the team.
Recommended workflow
Use a simple operating flow whenever your team is working on dns verification.
This keeps planning, review, and execution aligned before anything goes live.
- 1Open the sending domain and verification view.
- 2Review the records required for the domain.
- 3Coordinate updates with the domain owner if needed.
- 4Check the verification status again in SendFlow.
- 5Only move campaigns onto the domain when verification is complete.
Review checklist
A short review step usually prevents configuration drift, wrong audience targeting, or noisy campaign logs later.
Ask a second team member to confirm changes when the guide affects live delivery, routing, or workspace-wide assets.
- The correct domain is being verified.
- The expected DNS records have been added.
- Verification status is confirmed in the workspace.
- Launch plans do not depend on pending configuration.
Do not treat pending verification as good enough
A domain that is not fully verified should not be treated as production-ready for campaign routing.