DNS Tools

DNS Record History — Current Zone Snapshot

Export a timestamped snapshot of all current DNS records with change-tracking guidance

How to Use This Tool

  1. Enter the domain whose DNS you want to snapshot (apex or delegated subdomain).
  2. Click Get Snapshot to invoke lookupAllDnsRecords for that name.
  3. Results spread records by type with values suitable for copying into tickets or baselines.
  4. queriedAt timestamps the capture instant for audit trails.
  5. A note field clarifies that only current data is shown — true history needs repeated snapshots or external monitors.
  6. Store exports securely; TXT records may include verification secrets visible in public DNS anyway.

About This Tool

Tracking DNS drift without a baseline is guesswork. VSPIC captures a point-in-time snapshot of every record type returned by a full zone lookup on your domain, including domain name, records array with type host and value, queriedAt timestamp, and an explicit note that historical diffs require external monitoring over time.

This page is not a commercial passive DNS archive — it documents what authoritative DNS publishes right now so you can save, compare manually later, or feed into your own change management. Run before and after migrations, weekly on critical zones, and during incident response when someone asks what DNS looked like at discovery time.

Common use cases

  • View all DNS records of a domain after migration
  • Confirm DNS records after domain changes
  • Test for DNS leaks when using a VPN
  • Debug email delivery with MX and TXT records

Snapshot versus historical archive

Passive DNS databases accumulate years of observations from crawler networks. This tool delivers one authoritative snapshot on demand without subscription feeds. Build history by scheduling regular snapshots yourself.

The embedded note in API results states clearly that historical changes require external monitoring — set expectations for compliance teams reviewing this feature.

What full lookup includes

lookupAllDnsRecords aggregates common types served for the name — A, AAAA, MX, TXT, NS, CNAME, and others the resolver returns in the collection pass. It mirrors what operators need for general documentation rather than AXFR zone transfer completeness.

Some restricted types or apex-only NS may appear differently than provider export files — treat as operational snapshot, not legal zone file replacement.

Building a change-tracking practice

Export snapshot after every approved DNS change ticket closes. Filename with domain and queriedAt ISO timestamp. Diff tools compare JSON or text exports to highlight drift.

Weekly automated jobs calling the same backend action create lightweight history without passive DNS cost.

Incident response baselines

When hijack suspected, immediate snapshot preserves evidence before attacker edits TTL-down records. Compare against last known good export from change management vault.

Law enforcement and insurance may request timestamps — queriedAt provides machine-readable capture time.

Migration documentation

Pre-migration snapshot plus post-migration snapshot proves parity when paired with DNS compare for critical types. Store both in the ticket forever.

Include snapshots in runbooks for rollback — restore values from export if cutover fails.

TXT and secret hygiene

TXT records expose SPF, DKIM, domain verification tokens, and DMARC. Snapshots copy those into exports — treat files as sensitive if they consolidate reconnaissance data.

Rotate verification tokens if snapshot files leak from shared drives.

queriedAt in audits

SOC2 and ISO auditors ask when configuration was verified. queriedAt answers for that specific run. Repeated scheduled snapshots demonstrate ongoing control.

Align snapshot schedule with maximum TTL so cached stale data never masquerades as fresh longer than policy allows.

Pairing with compare and TTL tools

Compare two live domains when you need instant diff; snapshot when you need archival at rest. TTL checker adds timing context for how long a captured state persists in caches.

Together they form a migration toolkit without passive DNS contracts.

Limitations

No automatic diff UI or email alerts yet — operators diff manually or script against the API. No guarantee of hidden provider-internal records not published publicly.

Single resolver path reflects public view; internal split DNS may differ for intranet clients.

Frequently Asked Questions

Yes. VSPIC offers this DNS record history at no cost with no account required. Results load in real time.

We do not permanently store your queries on our servers. Some tools run entirely in your browser; others fetch public data for the request only.

Yes. Open the page in any modern phone or tablet browser. Results work on Wi‑Fi and mobile data.

No. Only current public records at query time. Build history by saving repeated snapshots yourself or using external monitoring.

ISO timestamp when the snapshot was taken. Use it in change tickets and audit evidence.

No. It queries public resolver data like normal lookups, not AXFR from authoritative servers.

Weekly for critical domains and immediately before and after every DNS change. Increase frequency during migration windows.

Yes via the extended API action for dns-record-history with your domain parameter. Respect rate limits and secure stored exports.

Next step for your check

Continue with dns compare tool on VSPIC.

DNS Compare Tool

Trusted by Users Who Value Privacy

Always Free

No premium plan ever

100% Private

Files processed in browser

Instant Results

Convert in seconds

Works Everywhere

Any device, any OS