Know what each record describes
A and AAAA describe IP addressing, MX points to mail handling, and NS identifies name servers. These observations help you review the DNS information associated with a monitored website.
Keep important DNS signals visible alongside uptime.
Review A, AAAA, MX and NS observations in the same workspace as your website checks. Keep DNS context close when something changes.
A
192.0.2.10 → 192.0.2.24AAAA
2001:db8::10MX
mail.exampleNS
ns1.example- 01Records observed
- 02A record change observed
- 03Review DNS context
Fictional sequence. Animation timing is not check cadence or a performance promise.
Use change as an investigation clue
DNS observations can add context after a hosting move, mail-provider change or nameserver update. Compare what is visible with the configuration you intended to publish.
An observation, not a global propagation verdict
DNS results reflect observations made by the service. They do not prove worldwide propagation, authoritative consistency across all resolvers, or the root cause of downtime.
In practice
Where this signal earns its place.
- Reviewing a move to a new hosting address.
- Keeping mail and nameserver context near website health.
- Investigating availability changes after DNS edits.
A closer look
Which DNS record types are shown?
The public website-health signals include A, AAAA, MX and NS records.
Is this a worldwide propagation checker?
No. These are DNS observations and health signals alongside uptime monitoring, not a globally distributed propagation test.
Connect the context
Related signals
01
All features Website Monitoring
Monitor availability, response time and downtime.
02SSL Monitoring
Track certificate health and expiry.
Start monitoring
Know about downtime before your customers do.
Add your first monitor and keep website availability, performance and incident history in one clear place.
7-day Starter trial · No credit card required · Starts with your first monitor