In a space where data provenance is rarely disclosed, we think you deserve to know exactly what you're looking at.
Domains observed across 1,300+ TLDs. Continuously processed. No registrant contact data. No identities. No tracking of individuals.
Last updated:
We observe more than we publish. See why ↓
1,300+ TLDs. Every Day.
Each block represents a TLD we track. From legacy giants to the newest gTLD launches.
* Our observation extends to country-code TLDs (ccTLDs). We hold that material rather than publish it. That is a choice we make: a dataset goes public when it clears the standard we hold ourselves to on identifiability and verification, and we have not extended publication to the ccTLD side. The 1,300+ figure reflects what we observe. The 1,000+ gTLD figure reflects what we publish. The difference is held inventory, not a coverage gap.
Observation Across the Entire Domain Lifecycle
Every domain follows a lifecycle defined by ICANN. We observe every stage through multiple independent public data sources. Each data point is cross-referenced and validated before being structured into our data processing pipeline.
What We Track. What We Don't.
Our focus is domain name intelligence based on lifecycle events and infrastructure-level technical changes. We do this work without tracking personal information. Since 2018, ICANN policy has stripped registrant personal fields from public gTLD data by default.
If you believe a published record relates to you, you can raise it with us. Requests for access or erasure are assessed case by case under the applicable data protection rules.
Why we do not collect the personal data behind a domain: We read what public data shows.
1. The registration data we read arrives through RDAP and WHOIS with registrant personal fields already redacted at the registry layer, the default for gTLDs under ICANN policy since 2018.
2. Many registrars add a privacy or proxy layer on top of that, so even the fields that remain typically point at a service, not a person.
3. Our subject is the domain, not the registrant. We read a name for its own intent, what it signals and where it sits in its lifecycle. Who really stands behind it is not our business.
Update Frequency
Different data dimensions operate at different cadences, matched to their nature.
