Domain Analyzer screenshot

Domain Analyzer

Combine a domain's RDAP registration record with its live A, AAAA, MX, NS and TXT records, plus a delegation note.

Privacy First
0 Runs
Updated 2026-11-07
Runs on the tool server
No account needed
Reads RDAP and public DNS
Reports an unavailable half

What the report combines

Two facts about one domain, from the two lookups this site already runs. The registration half is the RDAP record: registrar, status, registration and expiry dates, nameservers and DNSSEC signing. The DNS half is live: A, AAAA, MX, NS and TXT answers, with the TTL the resolver returned for each.

Then one comparison that neither half can make alone: whether the nameservers the registry records match the NS records the delegation actually returns. A mismatch usually means a nameserver change is propagating, and seeing the two sets side by side is the fastest way to tell.

How to use it

Enter a domain such as example.com and press Run. The report has three blocks — registration, DNS, notes — and a one-line summary.

If the registration half is unavailable

RDAP answers by redirecting to whichever registry runs the domain's TLD, and this deployment's outbound policy does not permit that redirect. When that happens the report says the registration record is unavailable, with the reason, and still returns the DNS half, which uses a resolver whose address is a fixed constant. Nothing is widened to make the other half work: the block is reported, not bypassed.

Honesty

A TTL is the resolver's answer and may be a cached copy. A missing record is reported as NODATA with that meaning, never as an empty list. Registration dates are the registry's, and a domain with privacy protection shows the registrar's redacted record, not the owner's details.

Enter a domain and this page returns one report built from two existing lookups: the registry record from RDAP and the live DNS answers for A, AAAA, MX, NS and TXT.

It adds one thing the two lookups do not: a delegation note comparing the nameservers the registry lists with the NS records the resolver returns, because a domain whose two lists differ is mid-change.

The two halves can succeed independently. If the registry half cannot be reached from this deployment, the DNS half is still returned and the registration block says it was unavailable, with the reason.

What the report contains

The registration block carries the registrar, the domain status flags, the registration and expiry dates, the nameservers and whether the registry marks the delegation as signed.

The DNS block carries the answers for each of the five types, and a per-type failure is listed separately rather than reported as an empty answer. A type that answered nothing is distinguishable from a type that failed.

The summary sentence names the registration dates or says they were unavailable, then names which record types answered.

  • Registration: registrar, status, dates, nameservers, DNSSEC flag
  • DNS: A, AAAA, MX, NS and TXT
  • One note comparing registry nameservers with delegated NS

Reading the delegation note

The note compares the two nameserver sets exactly. When they match it says so; when they differ it lists the names that appear only in the registry and only in DNS, which is the pair that tells you which side is stale.

It says the sets could not be compared, rather than guessing, when either half failed or either side published no nameserver. That is a limitation of reading two systems, not a finding about the domain.

How to use the domain field

Enter the domain and run the tool. The registry half reads RDAP and the DNS half asks for A, AAAA, MX, NS and TXT; either half can succeed while the other reports unavailable with its reason.

Read the registration block of registrar, status flags, dates, nameservers and delegation-signed flag, the per-type DNS answers, and the delegation note flagging registry-versus-resolver nameserver drift.

What to Expect

Best for

  • One view of a domain's registration dates and its live DNS
  • Spotting a nameserver change that has not finished propagating
  • Checking whether a domain is signed before a migration

Not ideal for

  • A domain not covered by RDAP, where the registration side will be missing
  • A deployment that blocks outbound redirects, where the registry half is unavailable
  • Any record type outside the five the report asks for

What this tool keeps

  • The registry's dates and status flags as published
  • Per-type DNS answers with the resolver's TTL
  • A named reason when either half is unavailable

What may need cleanup

  • The DNSSEC flag, which is the registry's claim rather than a validation
  • A delegation difference that may simply be propagation in progress
  • A registration block marked unavailable, which is an environment limit

Common errors

  • Reading an unavailable registration block as a finding about the domain
  • Treating a nameserver difference as an error rather than a change in flight
  • Expecting CAA or SRV records in the report

Example use cases

  • A pre-migration check on a domain's registrar and nameservers
  • Confirming a nameserver change reached the registry
  • Recording a domain's expiry date alongside its live DNS

Sample input

Analyse example.com and read its registration dates next to the A and MX answers.

Sample output

A report naming the registrar and both dates, the A and MX answers, and a note that the registry and delegated nameserver sets match.

Who this is for

  • System administrators preparing a domain migration
  • Developers diagnosing a nameserver change
  • Anyone who needs registration dates and live DNS in one place

Frequently asked questions

What does the domain report combine?

The registry record from RDAP and the live DNS answers for A, AAAA, MX, NS and TXT, in one report.

Does it validate DNSSEC?

No. The DNSSEC flag is the registry's own claim rather than a validation performed here.

Why is the registration half missing?

A domain not covered by RDAP, or an environment that blocks outbound redirects, leaves the registration half unavailable with a named reason.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.