Resource Library

Name Comparisons

Two ways to take the name — weighed properly, decided plainly. 12 guides in the lineup, each one brought up to speed for 2026.

12 Pages

The complete comparisons lineup

The UK's ending against the world's default — Nominet's machinery, the separate .uk question, and how a trading firm should decide.

The short brandable against the default: where mistyped traffic really goes, the ccTLD small print, and the pair registration that settles it.

Two endings from the same 1985 root — which to register when both are free, when .net genuinely fits, and when to take the pair.

The 2014 ending against the 1985 one: what .xyz is genuinely good at, where its reputation costs it, and the renewal question to ask first.

The bundling question argued both ways by a company that sells the bundle: what couples name to host, what never does, and the exits to test first.

What a lookup shows since GDPR, what the proxy layer still covers, who can see through both, and the endings where privacy is not allowed.

The renewal notice as a decision point: what a transfer moves, the year that travels with it, the locks that govern timing, and when staying wins.

The address as the name's most-used form: what a domain mailbox signals, the records that make it deliver, and why the switch gets harder every year.

The ten-year ceiling, the expiry sequence, what a long term insures against and what it cannot lock — the term decision made like a registrar.

.app, .dev and .store against .com, .net and .org — recall, reputation, premium tiers and the HTTPS floor, weighed like a registrar.

Registry tiers against aftermarket resales: what premium actually means, how each kind renews, and the two questions to answer before paying.

A record versus a registration: what a subdomain inherits, what a new name isolates, and the three tests that decide which a project has earned.

Then put it into motion. A certificate and the site move are in every plan, with people on the help desk at any hour.