URL vs Domain Name: What's the Difference?

A URL dissected — protocol, domain, path, query, fragment

Take https://www.webji.in/blog/hosting/?page=2#pricing apart:

• Protocol — 'https://' — the browser speaks HTTP encrypted with TLS over port 443.

• Subdomain — 'www.' — a branch of the domain, optional and configurable.

• Domain — 'webji.in' — the registered name: label 'WebJi®' plus TLD '.in'.

• Path — '/blog/hosting/' — the resource location on the server.

• Query string — '?page=2' — parameters passed to the application.

• Fragment — '#pricing' — an in-page anchor, scrolled without another server request.

The domain is one component of the URL; the URL is the complete instruction. That nesting is the entire difference.

Where the domain ends and the URL begins

The domain covers only the registered labels — what you buy from a registrar, like webji.in. Everything else in a URL is context bolted on: the protocol is a server configuration; the subdomain is a DNS record you create (www, blog, shop, mail). The path, query and fragment belong to the web application.

When you register a domain you own none of the URLs. You own the name that URLs are built around, and you can mint unlimited URLs under it — every path is a new URL the moment it resolves.

This is why domain registration transfers move DNS, email and site authority together, while URL changes are handled with redirects inside the same domain.

Subdomains, TLDs and root domains

Practical rules follow. www is a subdomain you can use or 301 to the apex — keep one canonical version. Use subdomains for genuinely different properties (shop, support, app), not for content that belongs on paths. Search engines treat subdomains as largely distinct sites, so authority consolidates better within a single host.

How a URL becomes a page — DNS to server to path

1. You type or click the URL; the browser extracts the domain.
2. DNS resolvers translate the domain to an IP address through root, TLD and authoritative nameservers, caching along the way.
3. The browser connects to that IP — TCP plus a TLS handshake for https.
4. It sends an HTTP request carrying the method, path, query and Host header (the domain, so shared servers know which site you mean).
5. The server maps Host plus path to a resource — a file, a WordPress render, or a redirect — and returns the response.
6. The browser parses the HTML, fetches referenced assets and jumps to any fragment.

The domain got you the server; the URL's remaining parts told it exactly what you came for.

URI vs URL vs domain — clean definitions

URI and URL are not the same product. URI is the option with less for you to operate. URL is the option with more control, and more that you have to look after. Choose by what happens when it breaks at night, and by the INR figure on this page. Email support@webji.services if you want that choice made against your actual site.

Ten example URLs labeled part by part

On protocol (https), the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Why the difference matters — canonicals and redirects

Search engines treat every URL variant — http/https, www/apex, trailing slash, query strings — as potentially distinct. Unmanaged, they split your authority across duplicates.

The fix is dull discipline that quietly wins rankings: pick canonical forms (https, one host), 301 the alternates, self-reference canonical tags on pages, and keep internal linking consistent. If a URL change goes wrong mid-migration, the WordPress URL repair guide walks the recovery — and domain-versus-hosting basics cover the other half of the pair.