How this site is written and corrected

Who writes

Guides and articles are written by people who do this work: detection, review and takedown operations. The roster is small and it is published. Every author has a profile listing what they have written here and what they have published elsewhere, so the claim of expertise is checkable rather than asserted.

Where a piece is written by the research team rather than an individual, it says so.

Who is accountable

The author named at the top of a guide is accountable for every sentence in it. They check technical claims against primary sources before publication, and two things in particular: the list of sources at the foot of the page, and the paragraph saying what the evidence cannot establish.

There is no separate reviewer, and this page does not claim one. A page carries one name, and that name is the one to hold to it.

Which sources count

Technical claims rest on primary sources: ICANN policy, IETF standards, Unicode technical reports, registry and provider documentation, and the published guidance of national security bodies. Those are cited at the foot of each page with links.

• A secondary source is not used to support a technical claim about how a protocol behaves.
• A vendor's marketing page is not a source for what a protocol does, including ours.
• Where a claim rests on this product's own behaviour, the methodology page is cited, because that page publishes the rule.

Dates

Published is the date a page first appeared. Updated changes only for a material change to the substance, never to make a page look fresh. A page whose wording was tidied does not get a new date.

The same rule governs the sitemap: a last-modified date there matches the page's real update date. Bumping it to court a crawler would be a lie told to a machine, which is still a lie.

Worked examples

Where a guide shows a check, that check was run on the date the page says, and the values shown are the values the public sources returned. Nothing is edited to look tidier, and an unavailable lookup is shown as unavailable.

Examples that do not come from a real run use example.com and the documentation address ranges reserved for the purpose, so that no illustration ever points at a real registration.

How software is used in drafting

Drafting assistance from language models is used on this site. It is used for structure, for first drafts and for consistency of voice. It is not used to originate technical claims, and no page is published on a model's assertion that something is true.

What does not change is accountability. A named person checks every published sentence against primary sources and is answerable for it. If a claim on this site is wrong, a person got it wrong, and the correction process below applies exactly as it would to anything else.

Corrections

Report an error through the contact page, with the page address and what you believe is wrong. Factual errors are corrected on the page, and a material correction carries a dated note saying what changed and when.

Corrections are not made silently. A page that said something wrong and now says something right shows that it changed.

Advertising, affiliates and sponsorship

There are none. This site carries no advertising, no affiliate links and no sponsored placements, and no third party pays for a mention. Nothing on a page is there because someone bought it.

The site is funded by paid plans, which is stated on the about page. That is the only commercial relationship between what you read here and what anyone pays.

What this site will not claim

Some claims would be easy to make and are not defensible, so they are not made.

• No detection-accuracy percentage, because no evaluation has been run that would survive scrutiny.
• No description of a domain as malicious on the strength of similarity alone.
• No certification the operator does not hold.
• No customer name, count or testimonial that has not been agreed in writing.
• No legal advice. Pages that touch disputes say so on the page.