Engineering Glossary · Domains
TLD — The Ending Changes Your Resolution Path, Not Your Page Speed
Someone has told you a particular ending is faster, and you would like to know whether that claim survives a measurement.
The short answer
A TLD is the rightmost label of a domain — .com, .org, .co.uk, .dev — and it decides which registry's nameservers answer the second step of a resolution, which policies and prices apply, and in a couple of cases whether browsers will accept plaintext HTTP at all.
What it does not decide is how fast your pages render. The ending affects a cold lookup by a handful of milliseconds at most and affects nothing once an answer is cached. If a benchmark says otherwise, the benchmark is measuring caching rather than the extension.
By the HostingFast team · Reviewed 24 August 2026
0
Entries with no jargon left over
100+
Terms, all cross-linked
Real
Worked examples, not diagrams
Free
To read, permanently
Endings fall into three practical groups. Generic ones — .com, .net, .org — put no restriction on use. Country codes attach a jurisdiction and sometimes an eligibility rule. The newer extensions exist mainly because the obvious .com went two decades ago, and they range from genuinely useful to purely decorative.
Behind each ending is a registry that sets wholesale pricing, decides whether DNSSEC is supported, publishes the parent zone your delegation lives in, and enforces its own transfer and renewal rules. Calling it a suffix undersells all of that.
The second hop, and what it costs
Run a traced resolution — dig +trace against your domain — and watch the query walk down: a root server points at the servers for the ending, those point at your domain's nameservers, and only then does an answer come back. The middle step belongs to the registry, and it is the only part of resolution your choice of ending touches.
Every mainstream registry runs anycast nameservers with a global footprint, and parent-zone answers carry long TTLs, so that hop is nearly always served from cache. The difference between two endings there is noise next to the difference between a well-placed authoritative nameserver and a badly placed one.
The one ending that genuinely changes browser behaviour
The .dev and .app namespaces are on the HSTS preload list as whole TLDs, which means mainstream browsers refuse plaintext HTTP to any hostname beneath them before a request is ever sent. That removes an HTTP-to-HTTPS 301 on first contact — a real round trip saved, and the only case where the ending is a measurable performance decision.
The flip side is that there is no plaintext fallback for local development or for a service that cannot present a valid certificate. On .dev, HTTPS is not a target you migrate towards; it is a precondition you build against from the first commit.
Where the ending does show up in your work
DNSSEC support is set per registry, so whether you can publish a DS record at all depends on the ending you picked. So does the minimum TTL the registry will accept on delegation records, and the length of the lock that follows a transfer.
Renewal economics differ wildly as well. Some newer endings sell a first year for pocket change and renew at a figure that assumes you have already built a brand on it. The renewal price, not the launch price, is the number that belongs in a budget.
Running any ending on this platform
The panel does not care which extension you use: zone editing, certificate issuance and mail routing behave identically on a .com and on a .agency. Free SSL is issued for every hostname you attach and renews itself before expiry.
Daily backups run on every plan and restoring a file or a database is one click in the panel rather than a ticket — which will do more for your availability than any decision about the ending ever will.
Definitions with the measurement attached
Most hosting glossaries stop at what a thing is. These entries carry the tool that measures it and the figure worth aiming for, because that is the part that changes a decision.
Per-site PHP version switching lives in the control panel, so a legacy application and a current one can run side by side on one account without anyone opening a support ticket.
- 100+ entries, cross-referenced end to end
- Every claim testable with a command
- Written against real panels and real tooling
- Free to read, with no email wall
Why HostingFast
Standard on every plan
Myths tested, not repeated
Where a popular claim about endings does not survive a traced lookup, this entry says so and shows the command.
TLD, in the resolution chain
Exactly which hop the extension owns, and why that hop is almost always served from cache.
The HSTS preload case
The one situation where your ending changes a browser's behaviour before your server is contacted at all.
Registry rules that reach your runbook
DNSSEC support, TTL floors and transfer locks vary by ending, and this page names which.
Renewal economics stated plainly
The figure to plan against is year two, and nothing here pretends otherwise.
Neighbours wired in
ccTLD, Domain Name and Domain Registrar carry the same thread forward.
Quick Start
From order to online
- 1
Trace a resolution once, properly
Run a traced query against your domain and read the three stages. Watching the parent zone answer removes most of the mystery about what an ending actually does.
- 2
Check the parent delegation TTL
Query the NS records for the ending itself and look at the TTL on the answer. Long values are precisely why nobody's page load is meaningfully affected by an extension.
- 3
Decide HTTPS policy before the ending
On .dev or .app, plan for HTTPS-only from the start, because there is no plaintext path to fall back on while you get a certificate sorted.
- 4
Price year two before you commit
Look up the renewal figure for the ending before a brand depends on it, and put that number in the budget instead of the promotional one.
Built In
Loaded onto every plan
- Any extension supported, with identical panel tooling behind it
- Free SSL issued and renewed for every hostname you attach
- Daily backups with self-service restores from the panel
- Per-site PHP version and extension control
- LiteSpeed caching at server level on every plan
- Money-back cover: 30 days on hosting plans, 7 on reseller
- No setup fee on any plan, ever
- 24/7 human support rather than a bot queue
Frequently Asked
What people ask us most often
Is a .dev domain actually faster than a .com?
Only on the very first request, and only because .dev is HSTS-preloaded: the browser goes straight to HTTPS instead of issuing a plaintext request that gets redirected. That is one round trip saved on first contact and nothing thereafter. Resolution speed itself is dominated by your authoritative nameservers, not by the extension above them.
Does the extension change my Core Web Vitals?
No. LCP, INP and CLS are measured from the moment a navigation starts, on a page that has already resolved, so nothing in those metrics can see your extension. If field data moved after a domain change, look for a redirect chain or a cold cache rather than the ending.
Can I publish DNSSEC on any ending?
No — support is set by the registry, and a few smaller extensions still will not accept a DS record. Check before you design a deployment around signed zones, because discovering the gap after you have signed makes for an awkward afternoon.
Will my hosting renewal cost more than my first term?
No. The rate you order at is the rate you renew at, every year. There is no introductory teaser pricing here, so there is no year-two step change waiting in an invoice — the hosting line stays a fixed number you can plan around.
Keep reading
Domain Name
The hostname itself, and the lookup every cold visitor pays for it.
Domain Registrar
Who holds the delegation, and which limits they impose on your zone.
Best Hosting With a Free Domain
Where a free domain sits in a plan, and what to check before it tempts you.
Web Hosting
cPanel hosting on NVMe with LiteSpeed, free SSL and a migration included.
Agency Hosting
Client accounts, staging and care-plan infrastructure built for agencies.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Ship it on hosting that measures up.
NVMe, LiteSpeed and free SSL on every plan, engineers who answer at any hour, and a renewal price that matches the day you signed up.
View Web Hosting plans