Privacy policy
TLD Stats has no accounts, no passwords, and no payment details, so there is no profile here to lose. This page says what is measured anyway, what your browser keeps, and who else sees a domain you look up.
Effective 3 September 2026
1.What this site does not collect
There is nothing to sign up for. TLD Stats holds no account, no password, no payment detail, and no mailing list. Nothing you do here is tied to a name, because there is no name to tie it to.
Your information is never sold, rented, or traded.
2.Analytics
Two analytics services run on this site.
- Fathom Analytics counts page views in aggregate. It sets no cookies and builds no cross-site profile.
- Google Analytics 4 measures the same traffic in more detail. It does set cookies, and it processes your IP address and approximate location under Google's own terms.
Neither one runs in local development, and neither receives anything you type into a lookup or into the feedback form.
A browser-level ad or tracker blocker stops both. The site works exactly the same without them, so blocking them costs you nothing.
3.What your browser stores
Two values are kept in your browser's own storage. Neither is a cookie, and neither is ever sent to a server.
tldstats-theme— whether you chose the light or the dark theme.tld-stats:starred— the extensions you starred for comparison.
Clearing your browser's site data removes both. The site keeps working; it simply forgets the preference.
4.The lookup tools send your query to a third party
This is the part worth reading carefully. The WHOIS lookup and the DNS lookup cannot answer on their own. The domain you enter is forwarded, from this server, to:
- IANA, for the list of which registry serves that extension.
- The registry's own RDAP server — Verisign for
.com, and a different operator for every other extension. - Cloudflare's public DNS-over-HTTPS resolver, for a DNS lookup.
Those operators see the domain and this server's request. They do not see you: the request is made by the site, so your IP address is not passed on. Each operator has its own privacy terms, over which this site has no control.
A lookup is not stored here. The result is cached briefly at the network edge so a repeated lookup is fast, and no record of who asked is kept.
5.The feedback form
The feedback control in the footer is the only place this site accepts anything you write. Sending a message submits:
- What you wrote, and the category you picked.
- Your email address, only if you fill it in. It is optional, and it is used to reply to you and for nothing else.
- Technical context that makes a bug report actionable: the page you were on, your browser's language, time zone and local time, its user-agent string, and your screen size.
Messages reach a private team channel and are read by a person. They are not added to a mailing list.
6.Hosting and server logs
The site runs on Cloudflare's network. Cloudflare processes each request in order to serve it and to defend against attacks, which involves standard request data such as your IP address. That processing is Cloudflare's, under its own terms.
7.Your rights
Under the GDPR, the UK GDPR, and laws such as the CCPA you may ask what personal data is held about you, ask for a copy, ask for it to be corrected or deleted, and object to its processing.
In practice there is very little to ask for. Unless you sent a feedback message with an email address, this site holds no personal data about you at all. If you did, ask and it will be deleted.
8.Children
This site is a reference tool for domain prices. It is not directed at children, and it knowingly collects nothing from them.
9.Changes
When this policy changes, the effective date at the top changes with it. There is no mailing list to notify, so the date is the record.
10.Contact
Use the Send feedback control in the footer of any page. It reaches a person, and it is the fastest route for a privacy request as much as for a bug.