What is a domain name in a URL? Domain vs URL vs web address, explained
The domain name is one part of a URL: the piece between the https:// and the first slash. Every component named, plus which single part you actually pay for.
| Subject | Buying |
| Published | August 2026 |
| Length | 7 min read |
| Written by | The NameBest team |
While you read this, the console on the homepage is checking names against the registry in real time.
No card needed. Or run the console without an account at all.
The domain name is one component of a URL: the part sitting between the https:// and the first single slash. In https://namebest.com/buy-a-url the domain name is namebest.com, while the full URL also carries the https:// scheme and the /buy-a-url path. Every domain name lives inside a URL, but a URL contains several parts that are not the domain name, and only the domain is something you buy.
This confusion costs people money, which is the only reason it is worth writing about. Somebody sets out to buy a web address, gets told they need a domain, assumes that is a different product, and ends up paying two companies for two things when they needed one. Or they buy a name and expect a website to appear, because the words URL and website got used interchangeably by whoever sold it to them. The parts are easy once somebody names them properly.
What is a domain name in a URL?
It is the address of the server, and it is the only part of a URL that is registered to a person or a company. The formal structure comes from the URL specification, and MDN documents it in the same terms: a URL is made of a scheme, an authority, a path, optional parameters, and an optional fragment. The authority is where the domain lives, alongside a port number that is almost always omitted because browsers assume 443 for HTTPS.
Take a longer address than the usual example, so every part is visible at once:
https://shop.namebest.com/domains/premium?ref=email#pricing
| Part | In this example | What it is | Do you buy it? |
|---|---|---|---|
| Scheme | https:// | The protocol the browser uses to request the page | No. It is shared by the whole internet |
| Subdomain | shop. | An optional prefix that splits a site into sections | No. It comes free with the domain |
| Second level domain | namebest | The name itself, the part people remember | Yes, together with the extension |
| Top level domain | .com | The extension, run by a registry | Yes, as an inseparable pair with the name |
| Domain name | namebest.com | The two above, joined. This is the registrable unit | Yes. This is the whole purchase |
| Path | /domains/premium | Which page on that server you want | No. You create paths for free |
| Query string | ?ref=email | Parameters passed to the server, often tracking | No. Software generates it |
| Fragment | #pricing | A jump to a section of the page already loaded | No. It is never sent to the server at all |
Read down the fourth column and the whole thing resolves. One row is a purchase. Everything else either comes with it or belongs to nobody.
Is a URL the same as a domain name?
No. A domain name is a component of a URL, not a synonym for it. The domain name identifies the server; the URL identifies one specific resource on that server. namebest.com is a domain name. https://namebest.com/buy-a-url is a URL. One domain name supports an unlimited number of URLs beneath it, which is why a shop with four thousand product pages still pays for exactly one registration.
The practical version: if it has a slash in the middle or a protocol on the front, you are looking at a URL. If it is just a name and a dot and a suffix, that is the domain.
What is the difference between a URL and a web address?
Nothing. Web address is the plain English name for a URL, and the two are used interchangeably by everyone including the people who write the standards. URL stands for Uniform Resource Locator, which explains why the plain phrase won. Nobody has ever said uniform resource locator out loud in a meeting on purpose.
The word that does mean something different is URI. A URI is the broader category of identifiers, and a URL is the subset of URIs that tells you where to find the thing rather than only naming it. Outside of specification documents the distinction rarely matters, and if you are here to buy a URL for a business it does not matter at all.
Where does the domain name end and the path begin?
At the first single slash after the scheme. That is the rule, and it holds for every URL. The two slashes in https:// are part of the scheme separator and do not count. So in https://namebest.com/domains/premium, everything before the third slash is the domain and everything from it onward is the path.
This matters more than it sounds, because attackers exploit the fact that people read left to right and stop early. An address like https://namebest.com.verify-login.example/ has nothing to do with namebest.com: the real domain is verify-login.example, and the recognisable brand has been parked in a subdomain to look reassuring. The trustworthy part of any URL is the last two labels before the first single slash, and reading them is the single most useful habit in this entire article.
Is www part of the domain name?
Technically it is a subdomain rather than part of the registrable domain, and it is optional. You register namebest.com, and www.namebest.com is something you switch on afterward at no extra cost, along with any other prefix you fancy. Most sites configure both and redirect one to the other so a single version is canonical, which keeps search engines from treating them as two separate sites.
You never buy a subdomain, and no registrar will sell you one. If somebody is offering to, they are selling you space on a domain they control, which is a different arrangement entirely and one where you do not own the address.
Which part of a URL do you actually pay for?
The domain name, as a single unit of name plus extension, charged yearly. In the United States in August 2026 an ordinary unclaimed .com runs roughly $11 to $23 a year, and that spread is mostly registrar margin: Verisign charges every registrar a wholesale fee of $10.26, rising 7 percent to $10.97 on November 1, 2026, with a $0.20 ICANN transaction fee on top. Other extensions are priced by their own registries and vary a lot, from about $12 for .net up to $83 for .ai.
Nothing else on the list carries a price. Paths, subdomains, query strings and fragments are all yours to create in unlimited quantities once the registration exists. What does cost extra is hosting, which is a separate product from a separate company: the domain is the address, hosting is the machine that stores the files, and a working site needs both. If the address you want is already registered, you can still often buy it from the person holding it rather than settling for a worse name.
Does URL structure affect SEO?
The extension does not. Google has said repeatedly that the top level domain is not a ranking factor, and it treats a published list of country extensions used generically, including .co, .io and .ai, as generic rather than geographic. Picking .io over .com is a branding decision and a budget decision, not a search penalty.
The path is a different matter, though the effect is modest and mostly about humans. Short, readable paths made of real words are easier to scan in a result, easier to paste into an email without breaking, and easier for a person to guess. Long strings of numbers and session parameters do the opposite. Keep the structure shallow, use hyphens between words, and stop worrying about it, because content quality outweighs URL cosmetics by an enormous margin.
Why any of this matters when you are buying
Because it changes what you go shopping for. Once you know the purchase is one domain and not a bundle of addresses, you stop over-buying: you do not need a separate registration for a blog, a shop and a support site, because subdomains and paths cover all three for free. And you stop under-buying, which is the more expensive mistake, by grabbing a cheap awkward name on the assumption that the address barely matters when it is the one part of the whole setup you cannot cheaply change later.
The order that works is unglamorous. Decide the name, check whether it is available across the extensions you would accept, look at the renewal price rather than the first year offer, and register it in your own name or the company's rather than in an account belonging to whoever built the site. That last point catches people out constantly. If you are going to hire someone to build the site for you, buy the address yourself first and give them access to point it, because a domain sitting in a contractor's account is a negotiation waiting to happen.
Then treat the address as permanent, because in practice it is. Registrations are licensed for a term rather than sold outright, but renewal is unconditional, so the name stays yours indefinitely as long as you keep paying. Changing it later means redirects, reprinted material, and a search reset nobody enjoys. It is worth ten extra minutes now. When you are ready, the full walkthrough of buying a domain name covers all three routes with prices and timings attached.