RDAP
Registration
Registrar, lifecycle events, public statuses, nameservers, and DNSSEC delegation indicators. Registration contacts are commonly redacted; DomainSense does not reconstruct private identity.
Open methods · version 1.2
Show the source.
Name the limit.
Domain intelligence is useful only when readers can see how it was produced, what it means, and where it stops.
Public DNS
Resolution
A, AAAA, MX, TXT, and CAA answers are requested through standards-based DNS-over-HTTPS. Records can vary by location and change after collection.
HTTPS probe
Endpoint
A bounded public HEAD request checks whether an HTTPS endpoint responds. This is not a content audit, uptime guarantee, or security scan.
IANA + DNIB
Root & market
Delegated TLDs and RDAP routing come from IANA. Quarterly totals come from linked industry reports. Counts describe labels and registrations—not people, active sites, eligibility, or economic value.
THE OBSERVATION COUNT
A disclosed checklist, not a ranking.
DomainSense reports how many of eight equally weighted checks were observed: a registration record, a registrar field, two or more nameservers, an address record, an HTTPS response, DNSSEC delegation signing, mail routing, and a CAA policy.
The count does not estimate sale price, traffic, reputation, legitimacy, brand quality, legal rights, or owner intent. An unavailable registration lookup is labeled unavailable rather than silently converted into a negative fact.
REFRESH & HISTORY
Observation starts here—not in the past.
Domain reports are cached for up to 24 hours. When a refreshed report changes, DomainSense retains a bounded public snapshot and identifies which observable fields moved. The ledger begins with the first DomainSense observation; it is not reconstructed historical ownership, passive DNS, or proof of when a real-world change occurred. The TLD Atlas refreshes from IANA on a six-hour cycle. If a normalized result conflicts with its source, the source is authoritative.
Inspect every source and refresh boundary →