Editorial Policy

What we publish and why

We publish practical guidance on domain registration, transfers, DNS configuration, DNSSEC and WHOIS privacy. Because we also sell those services, you are right to ask how independent the writing is — this page sets out where our commercial interest sits.

How we research

Domains and DNS are unusually well specified, so we base factual claims on primary sources: ICANN policy and consensus documents, registry and registrar documentation, the relevant RFCs, and official guidance from data-protection authorities. Where registry rules differ by TLD — and they often do — we say so rather than generalising.

Honesty about limits

Caching and resolver behaviour mean DNS changes are rarely as instant as marketing implies, transfer windows are set by registries rather than by us, and not every TLD supports every feature. We would rather state a limitation than oversell a capability.

No invented numbers

We do not publish statistics, uptime figures, customer counts or certifications we cannot substantiate. Where we cite third-party research, we say whose it is.

Accuracy and corrections

If we publish something inaccurate, we fix it. Material corrections — anything that changes the meaning or the advice — are made promptly and noted on the article rather than quietly edited. Minor fixes are made without a note. Spotted an error? Email [email protected] with the URL and what you believe is wrong.

Use of AI

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

Commercial interest

Many articles relate to services we sell and link to our own pages. What we commit to is that the technical claims are meant to be correct whether or not they favour us, including cases where another provider or approach may suit you better. Nothing here is sponsored content.

Related: About · Blog · Accessibility