Check MX and authentication-record readiness.
Tool
Mail record check
Review public mail DNS records before adding mail-delivery health checks or alerting.
Checker preview
Safe server-side check
Validate targets before creating recurring watches.
Mail DNS preview
This page is ready for a safe server-side checker integration.
Use monitored records for domains that send customer email.
Keep credentials, mailbox routing, and private provider notes internal.
Watch the signal
Start with a safe one-off preview before enabling recurring checks.
Measure the trend
Keep response, uptime, and incident context close to the decision.
Route the response
Alert the right people and publish customer-safe updates when needed.
What this tool is for
Mail record checks help diagnose whether public DNS is ready for reliable delivery.
When to create a monitor
Add recurring checks when a domain sends invoices, OTPs, alerts, or client-facing transactional mail.
Safe usage
Publish only customer-safe mail-health status, not private routing or admin mailbox details.
Tool workflow
One-off checks first. Continuous monitoring when it matters.
Tools should help people diagnose a specific target. If the target is customer-facing, FTStatus should turn that check into a durable monitor with alert routing and status-page impact.
Mail DNS preview
The page shell is ready. The live checker should be connected through a safe server-side route before accepting public submissions.
Related pages
Continue building the monitoring workflow.
Ready to set up the right monitors?
Start with critical customer-facing services, then add status pages, alert routes, and managed help as reliability becomes more important.