Check whether public DNS answers match expectations.
Tool
DNS health check
Run a quick DNS-oriented check before turning critical records into continuous monitoring.
Checker preview
Safe server-side check
Validate targets before creating recurring watches.
DNS health preview
This page is ready for a safe server-side checker integration.
Use ongoing monitors for records that affect live services.
Keep provider and internal resolver details out of public pages.
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
DNS health checks help confirm whether public records appear healthy from outside your own network.
When to create a monitor
Create recurring DNS monitors for customer-facing domains, mail records, and platform endpoints.
Safe usage
Do not expose internal resolver names, origin IP details, or firewall allowlists in public output.
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.
DNS health 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.