Ending vs Ending
.com vs .net — the call to make while both are still free to register
Two endings from the same January 1985 root file, both open to anyone, and only one of them the answer people type when they guess your address.
The short answer
If both are free, register the .com and make it the name you print; it is the ending browsers autocomplete, customers guess, and the aftermarket values. Register the .net alongside it only when the name matters enough to defend, and point it at the same site.
.net earns first place in one honest case: a business that is genuinely network-shaped — infrastructure, connectivity, platforms — where the ending describes the work. Everything below is the working, from what each registry actually runs to what a WHOIS lookup will show for either.
By the Hosting & Domains team · Reviewed 25 August 2026
1985
Both endings in the root since
Open
No residency rules on either
60 days
Registry lock after registration
Free
WHOIS privacy on both
The two endings entered the root in the same month of 1985 and have been administered side by side ever since. Technically they behave identically: same delegation rules, same sixty-day transfer lock after registration, same grace and redemption sequence if a renewal is missed. Nothing in DNS treats one better than the other.
The difference is entirely human, which is why it matters more, not less. This page argues the choice from the registrar's side of the counter: what each ending signals, what happens to type-in traffic when you pick the less-guessed one, and the narrow cases where .net is not a fallback but the right first answer.
Identical machinery, unequal habit
In the zone file, .com and .net are the same kind of thing: generic endings with no eligibility test, delegated to whichever nameservers you set at your registrar, renewable on the same registry calendar.
Outside the zone file, decades of habit have made .com the address people assume. Someone who half-remembers your name will try it with .com first, and if a competitor holds that guess, the traffic lands with them.
That asymmetry is the whole comparison. You are not choosing between two technologies; you are choosing whether the commonest guess about your name resolves to you.
When .net genuinely fits
.net began as the ending for network operators, and for anything infrastructure-shaped — connectivity, hosting platforms, monitoring, an ISP — it still reads as description rather than compromise.
It also ages well. Unlike a novelty ending, nobody asks what .net means, and it carries none of the reputational baggage that some newer, cheaply registered endings have collected with spam filters.
What it does not do is catch the guessers. A .net address on the side of a van sends some fraction of its readers to the .com, so the ending suits businesses found by referral and search more than by memory.
The case for taking the pair
If the name is one you intend to build a brand on, registering both endings on day one is the cheapest defensive act you will ever take. The .net that costs a routine registration today is a negotiation with a stranger tomorrow.
Delegate the second name to the same nameservers and redirect it permanently to the first. A 301 from the spare to the main consolidates search signals rather than splitting them.
Registering the pair also closes the commonest impersonation route: a lookalike address one ending away from yours, used to phish your own customers.
What a registrar checks before recommending either
First, the registrant record: whichever ending you take, it should be registered in your details, not an agency's, because the registrant is who the registry listens to.
Second, the renewal, shown before money moves rather than discovered at year two. Both endings renew on published registry-anchored rates, and a registrar unwilling to show them is telling you something.
Third, the exit. Both endings transfer on an auth code once the sixty-day lock lifts; confirm the registrar will release on request before you bring a name you care about.
The guess test, run before you register
Say the name aloud to somebody who has never seen it written, then ask them to type the address. Nearly everyone appends .com. That one experiment settles most .com vs .net debates faster than any article, because it shows you where your misremembered traffic will go.
If the .com of your name is taken and the .net is free, run the test again with the person told the ending. If they retain it, the .net can work — with the caveat that you are renting recall the .com owner gets free.
- Both endings registered in your details, not held for you
- Delegation to any nameservers, changeable at will
- WHOIS privacy included on both, at no charge
- Transfers released on request once the registry lock lifts
Why Hosting & Domains
Standard on every plan
Search once, see both
One availability search covers .com, .net and the endings adjacent to them, so the pair decision is made with the facts on one screen.
The renewal in view first
Registration and renewal are shown together before checkout, because a name is a recurring commitment and should be priced as one.
Redirects done properly
Point the defensive name at the main one from the same panel — permanent redirect, certificate issued, no search signal split.
Quick Start
Order placed to site online
- 1
Run the guess test
Have someone who has never seen the name type the address. Where they land is where your brand's stray traffic will land.
- 2
Register the winner in your own details
The registrant record is the title deed. Your name, your mailbox, your registrar login — never a third party's.
- 3
Take the pair if the brand warrants it
Register the other ending, delegate it to the same zone, and 301 it to the main site so the two never compete.
Built In
Fitted to every plan
- The .com checked first, whatever you end up registering
- Registrant record in your details from day one
- WHOIS privacy applied at registration, not bolted on later
- Renewal date diarised, auto-renew on, card in date
- The spare ending redirected permanently, not parked blank
- Auth-code transfer confirmed as available once the lock lifts
Frequently Asked
The questions that come up most
Is .net worse for search rankings than .com?
No. Search engines treat the classic generic endings identically; ranking follows content and links, not the ending. What .com changes is human behaviour — the guessed visit, the remembered address — which affects traffic before search is involved at all.
The .com of my name is taken but not in use. What are my options?
Check WHOIS for the expiry and the registrant. If it lapses, it passes through grace and redemption before any drop, and names with any value are usually caught at auction. A polite approach to the owner sometimes works; otherwise take the .net or adjust the name — building on a name you hope falls vacant is not a plan.
Can I register the .net now and move to the .com later?
Yes, and the move is routine: register the .com when it becomes available, serve the site there, and 301 the .net across. Expect a period of updating printed material and directory listings — which is the argument for settling the ending before the brand goes on vehicles and cards.
Do .com and .net renew on the same terms?
The machinery is the same — annual terms, extendable up to the registry's ten-year ceiling, same grace and redemption sequence. The rates differ by registry and are shown against each ending before you pay, so compare them on the page rather than assuming.
Does it matter that both are run by the same registry operator?
Operationally, no — your relationship is with your registrar, and both endings transfer, delegate and renew under the same ICANN policies. It mainly explains why the two behave identically in every technical respect: they are siblings from the same 1985 root, managed side by side.
Keep reading
.com vs .co
The other ending that trades on being nearly .com — what the missing letter buys and risks.
Domain Names
Search the name across every ending we carry, with renewal shown beside registration.
Domain Prices
Every ending's registration, renewal and transfer rates on one page, no footnotes.
Web Hosting
cPanel hosting on NVMe drives for whichever ending wins — delegation set at registration.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Settle the ending, then take the name.
Search once across .com, .net and their neighbours, register in your own details, and see the renewal before you pay.
View Domain Names plans