Dynadot Announces KYC Verification for Some TLDs

Know Your Customer is a compliance relay race. A registry — usually a ccTLD bound by local law, or a gTLD under pressure from regulators — sets the identity requirement, and the registrar becomes the clerk who collects the documents. Dynadot is the clerk.

The phrase 'certain domain name extensions' is the tell. A universal KYC policy would be a business decision. A selective one is a contractual obligation. Someone upstream has written this into the registry's terms.

For domain investors, this is friction where friction did not exist. The domain market was built on low-friction ownership: register quietly, hold, sell. Identity verification inserts a document check into that flow, and it makes the quiet resale of names in those extensions materially harder.

The deeper machinery is the slow migration of domains toward financial-services norms. Banks have always verified customers. Registries are adopting the same discipline, and the anonymous middle years of domain ownership are getting shorter.

• A mechanic worth scanning: the list of TLDs Dynadot eventually names. It reveals which registries are demanding identity — and that map shows where regulatory pressure is biting next.