Loading...

DNS History

Review previously observed DNS values and when they were first and last seen.

Enter an exact name without https://, a path or a port. Use ASCII or Punycode; subdomains are searched separately.
Looking up DNS observations…
Enter a domain to explore the DNS records observed by mnemonic PassiveDNS.

Only the first 1,000 provider matches were examined. Some history may be missing, including when no rows are shown. Select a specific record type to narrow the search.

Ordered by last seen, newest first. All dates are in UTC.
Record type Value First seen (UTC) Last seen (UTC) Observations
Passive DNS observations can be incomplete. First and last seen dates are not exact change times and do not confirm that a record is currently active. Check current DNS records

Follow VuiZ.Net on Google Search

Add VuiZ.Net as a preferred source on Google to find your favorite tools more easily.

  • Find your tools again
  • Discover new utilities
  • Support VuiZ.Net
Follow

Explore a domain’s observed DNS history

DNS History retrieves public observations from mnemonic PassiveDNS for an exact domain or hostname. It helps you investigate previously observed IP addresses, mail servers, nameservers and other DNS values.

Each row contains a record type, value, first seen and last seen dates, and an observation count when available. These are observations from the provider’s sensors, not a complete change log or a live DNS lookup.

Key features

  • Record type selection Search all available types or request A, AAAA, CNAME, MX, NS, TXT, SOA or CAA records. Only records belonging to the exact submitted name are displayed.
  • Observation dates in UTC Results are ordered by the most recent last-seen date. First seen and last seen describe the provider’s observation window, not the exact time a DNS change occurred.
  • Filter and export Filter the returned rows by record type or value, then copy those rows or download them as CSV. Exported dates use ISO 8601 UTC.
  • Cached public data Successful lookups are cached for six hours. Up to 1,000 provider matches are examined per query; a warning appears if more matches exist.

How to look up DNS history

Find historical observations for an exact DNS name and export the relevant records.

  1. Enter the DNS name Enter a domain such as example.com or a hostname such as www.example.com without a scheme, path or port. Use Punycode for internationalized names.
  2. Choose a record type Select All types for an overview, A or AAAA for IP addresses, MX for mail routing, or another listed type. Click Look up history.
  3. Read the observation window Review each value and its first and last seen dates in UTC. Check the retrieval time and any result-limit notice before drawing conclusions.
  4. Filter and save Type part of a value or record type into Filter results. Use Copy rows or Download CSV to save the rows currently shown.

Usage tips

  • Look up example.com and www.example.com separately; this tool does not expand a domain into its subdomains.
  • Use DNS Lookup to check current records. A recent last-seen timestamp alone does not prove a record is still active.
  • If a limit warning appears, repeat the search with a specific record type to narrow the provider query.
  • The submitted domain is sent through the VuiZ server to mnemonic. Query only names you intend to share with that service.

Frequently asked questions

No. Passive DNS coverage depends on what the provider’s sensors observed. Missing periods and values are possible, and multiple values may overlap in time.
They are the earliest and latest observations reported for a record by mnemonic. They do not identify the exact creation, modification or deletion time of that DNS record. Dates are displayed in UTC.
The public dataset may contain no observations for that exact name or selected type. Empty results do not prove that the domain never existed or that it had no DNS records.
Only records whose owner name matches your input are displayed. Subdomains must be queried separately. Provider matches that merely contain your domain as an answer are excluded; they can still consume part of the 1,000-match limit.
VuiZ caches successful results for six hours and limits requests to the shared public provider. A rate-limit or service error asks you to retry later; it is not reported as an empty history.