Save your DNS records. Compare past versions. Get alerts for the changes that matter.
DNS records connect your domain to your website, email, and other services. dnsstat.us backs up those records so an accidental edit or provider move doesn’t leave you guessing what used to be there.
Your websiteAddresses used to reach your web server
A / AAAA
✉
Your emailServers that receive mail for your domain
MX
✓
Your connected servicesDomain verification and email authentication
TXT
Website DNS record changed1 edit
Before192.0.2.10
→
After198.51.100.20
The previous address is still in your backup history.
Illustrative example · not live domain data
DNS, in plain English
DNS tells browsers and mail servers where to send traffic for your domain. A DNS backup saves those settings, including website addresses, mail destinations, and service verification records. It gives you the old values when you need to repair a mistake.
Why back up DNS?
A deleted DNS record can break a working service.
Your website and email can depend on just a few records. A separate copy helps you find and repair mistakes, even when the provider’s current settings no longer show what was there.
01
Accidental edits
“The new website is up. Why has email stopped?”
A website launch can accidentally remove the records that route email. Compare the DNS backup from before the launch with the current records to see what was removed.
↳ Find the previous value your IT team needs to restore.
02
Provider changes
“What were the settings before we switched?”
Before moving DNS to another provider, keep a copy of the existing records. Compare it with the new provider’s configuration and export saved versions when you need them.
↳ Check the migration against a saved copy.
03
Unexpected changes
“Who changed this record, and what was it before?”
An unexpected change can send visitors or email to the wrong place. Optional alerts flag changes for review, and saved versions show the old and new values. Provider audit logs can help identify who made the edit.
↳ Investigate the change with the previous records available.
Saved DNS versions
See which records changed. Keep the values they replaced.
Open a domain’s timeline, select a saved version, and compare it with another date. Each change shows the records added, removed, or edited, including the previous values.
See the exact difference. Added, removed, and edited records are highlighted.
Keep history without duplicate copies. Unchanged checks don’t create duplicate versions.
Export a saved version. Download records as a zone file or JSON to help restore settings at your DNS provider.
example.com / Change historyExample
Change observed
Mail destination updated
1 modified
MXexample.com Directs incoming email to your mail provider
− Previous value10 mail.old-provider.example.
+ New value10 mail.new-provider.example.
Initial recordsMonday
Mail record changedTuesday
No further changeWednesday
Illustrative history. DNS settings are changed at your provider; dnsstat.us keeps the record.
For domain owners, IT teams & MSPs
Keep a DNS backup. Give the right people access.
For business & domain owners
A copy of the settings your business relies on.
Your web designer, host, and IT team may all manage parts of your domain. Keep a separate DNS history they can use to investigate problems and recover earlier settings.
Review changes and ask your IT team whether they were expected.
Track registration dates and choose renewal reminders where dates are available.
Have the previous settings available when you need help.
The setup may need help from whoever manages your DNS.
For IT admins & managed service providers
DNS history across your customer domains.
Back up supported provider accounts, review changes across domains, and give each customer access to their own records. Follow an alert to the record and its saved history.
Connect Cloudflare or ClouDNS with read-only access.
Monitor public DNS answers when an API connection is unavailable.
Choose alert categories and severity, with email or webhooks.
Role-based access separates customer workspaces and administrator controls.
How it works
Connect your DNS. Save the records. Monitor changes.
1
Add your domain
Connect a supported DNS account, import a zone file, or discover and select public records to monitor.
2
Save a baseline and changes
The first successful capture becomes your baseline. Later checks save a new version when records change, keeping the earlier versions available.
3
Set your alerts
Choose the changes, DNS availability issues, missed captures, and renewal reminders you want to hear about.
Choose the right backup source.
Cloudflare and ClouDNS API connections capture the DNS configuration those providers expose. Imported zone files preserve the records you supply. Public DNS discovery monitors the names and answers it finds; it cannot guarantee a complete zone backup. Checks run on a schedule, so changes between checks may not be captured.
Backup coverage & access
Before you connect a domain.
No need to move your domain or change where your website lives.
My provider stores my DNS. Why keep a separate backup?
Provider history and recovery options vary. A separate DNS backup keeps previous records available outside the provider’s control panel, so you can compare versions and check a migration or accidental edit.
Will this change my DNS or fix problems automatically?
No. Provider integrations are read-only. dnsstat.us records and monitors your settings; you or your IT team make any corrections at your DNS provider. You can export a saved version to help restore the settings yourself.
Does this back up my website or my email?
It backs up DNS records, not website files, mailboxes, or business data. Keep your existing website and email backups. The backup contains the DNS settings used to reach those services.
What if I don’t have a supported DNS provider?
You can import a zone file, enter records, or use public record discovery. Public lookups provide observations rather than a complete copy of the provider’s configuration. Your host or IT team can help decide which records to monitor.
Will I get an email for every rotating server address?
You choose the alert categories and severity. For records monitored through public DNS, learning mode builds a set of accepted answers before monitoring for unfamiliar ones. This helps reduce routine rotation alerts, but no single monitoring location can see every possible answer.
Can it remind me before a domain expires?
Yes, when a renewal or expiration date is available from a supported registry or provider, or has been entered manually, and you enable the relevant alerts. Some registries do not publish that information. Reminders do not renew the domain for you.
How do I get access?
If you already have an account, sign in to the portal. To ask about using dnsstat.us, use the inquiry form below. An administrator or IT provider arranges workspace access and helps connect your domains; submitting the form does not create an account.
We count visits, time spent viewing pages and sections, use of links, and which questions are opened without cookies or personal identifiers. If you submit an inquiry or arrive through a link from adrytech’s sales team, the pages you view may be connected to your inquiry to help the team respond. Inquiries go to adrytech’s sales team, who read and answer them. This tracking applies to the public website, not your DNS records or activity inside the portal.
We also use Cloudflare Web Analytics to measure page loading, responsiveness and layout stability. Cloudflare receives page-load information, including your network address, browser, page address and referrer. This service uses no cookies or fingerprinting. It runs only on this public website; it does not receive customer DNS records or activity inside the portal.