✓
DNS record history
Compare A, AAAA, CNAME, and nameserver snapshots with the known baseline.
Domain & DNS change monitoring
Know what changed before a DNS problem becomes a prolonged outage.
MetricPoints watches DNS records, nameservers, domain expiration, SSL, and availability. When infrastructure changes, you get a clear history and the surrounding website-health evidence—not another isolated alert with no context.
DNS baseline changes
Domain expiration
SSL certificate health
Availability impact
Included in every unified monitoring plan. No separate DNS subscription.
Change detected
DNS records changed
store.example.com · Infrastructure incident
Nameserver response changed
A and nameserver snapshots differ from the approved baseline.
9:42 AM
Availability check degraded
The same host began returning intermittent resolution failures.
9:45 AM
Resolution recovered
The timeline preserves the change and recovery evidence for follow-up.
10:03 AM
DNS
Changed
SSL
Valid
Uptime
Degraded
Domain
Current
Illustrative incident using signals monitored by MetricPoints.
The infrastructure layer people forget
A website can look healthy right up until its foundation changes.
DNS edits, expiring registrations, certificate problems, and nameserver changes can break access, email, checkout, or third-party services. MetricPoints records the evidence so you can distinguish an intended change from something that needs attention.
✓
Domain expiration
Surface registration-expiry risk early enough to act before a preventable disruption.
✓
SSL certificate health
Track certificate validity and approaching expiration alongside the affected host.
✓
Availability correlation
See whether infrastructure changes coincide with resolution failures or downtime.
One monitoring product
DNS is the starting signal, not the end of the investigation.
A DNS-only tool can tell you a record changed. Unified monitoring helps answer the next question: what did visitors and the website experience at the same time?
Explore complete website monitoring →Availability
Did the host stop resolving or responding?
Browser errors
Did visitors encounter new frontend failures?
Performance
Did the site become slower after the change?
Security protections
Did CSP or security headers weaken?
What happens after you connect a site?
- 1
Establish the baseline
MetricPoints captures the current infrastructure state and begins the configured health checks.
- 2
Detect meaningful drift
New snapshots are compared with the known state so unexpected DNS and domain risks stand out.
- 3
Review the full impact
Open the incident history and related health signals to decide what changed and what to do next.
Frequently asked questions
Domain and DNS monitoring, clearly explained
Which DNS records are monitored?+
MetricPoints currently captures A, AAAA, CNAME, and nameserver records for baseline comparison. Monitoring scope can vary by hostname and configuration.
Does MetricPoints automatically change my DNS?+
No. Monitoring is read-only. MetricPoints detects and records changes; it does not edit DNS records, nameservers, registrations, or certificates.
Is DNS monitoring sold separately?+
No. DNS, domain, SSL, uptime, browser-error, performance, CSP, and security-header signals are included in the unified monitoring plans.
What is the difference between Website Coverage and Full Coverage?+
Both include the core infrastructure signals and incident summaries. Full Coverage adds the deeper raw events, advanced filters, session context, replay, and developer diagnostics used to investigate complex incidents.
Monitor the change—and the website around it.
Start with domain and DNS confidence. Keep the complete view of availability, errors, performance, and protection.
Compare Unified Monitoring PlansWebsite Coverage starts with complete health signals. Full Coverage adds developer-grade evidence.