Editorial Policy

What this blog is for

We write about web data, domain intelligence, technology detection and dataset construction. We also sell those things, so our commercial interest is obvious and we are not going to pretend otherwise. What follows is how we try to keep the writing useful anyway.

How we source claims

Where a factual claim can be traced to a primary source, we use one: IANA's root zone database for TLD counts, registry and registrar documentation, ICANN policy, the RDAP specifications, and published industry briefs for market-level figures. Where practice varies by registry or jurisdiction — and in domain data it varies constantly — we say so instead of generalising.

Numbers

We do not publish coverage figures, client counts or accuracy rates that we cannot substantiate, and where a number is an estimate we label it as one. If we quote a volume, we state the basis on which it is counted — a count of registered domains, of domains ever observed, and of domains currently resolving are three different numbers, and conflating them is how data vendors end up claiming to cover more of the internet than exists.

This is not legal advice

Nothing here is legal advice, and reading it does not create a client relationship. Data protection, database rights and terms-of-service questions turn on specific facts and jurisdiction. Involve qualified counsel before acting on anything you read here.

Corrections

When we get something wrong, we fix it. Material corrections — anything that changes a fact or a recommendation — are made promptly and noted on the page rather than edited away quietly. Minor fixes are made without a note. If you have spotted an error, email [email protected] with the URL and what you believe is correct.

Use of AI

We may use AI tools to help draft, outline or edit. AI is never the final authority: a person is accountable for every published page, checks its claims, and stands behind it. We do not publish unreviewed machine-generated text.

Related: Blog · Methodology · Data Sources