URL vs Domain Name: What's the Difference?

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

A URL has six parts: protocol, subdomain, domain, path, query string and 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.

Domain name vs URL — side-by-side comparison

A domain name identifies the site; a URL identifies one resource on that site. The domain is a component of the URL, not a synonym for it.

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. The lookup itself is covered in DNS records explained.

URI vs URL vs domain — clean definitions

A URI identifies a resource, a URL is a URI that also says where to fetch it, and a domain is the registered name inside that address. Every URL is a URI, but not every URI is a URL.

• URI — any identifier, such as mailto:support@webji.services. It names a resource without promising a web location.
• URL — a URI with a scheme and a location, such as https://webji.in/pricing/. It tells the browser where to fetch.
• Domain — the registered label plus the TLD, webji.in. It is the part you renew at a registrar, and it appears inside the URL's host.

Ten example URLs labeled part by part

Each row below is a real address with the parts labelled, including subdomains, a port, query strings, fragments, a country-code domain and one URI that is not a web URL.

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.

Is an IP address the same as a domain or a URL?

No. An IP address is the numeric location of a server, a domain is a human-readable name that DNS maps to that IP, and a URL adds the protocol and path that select one resource on it.

• IP address — 192.0.2.10 or 2001:db8::1. Computers route to this; people do not remember it.
• Domain name — webji.in. A DNS A record (IPv4) or AAAA record (IPv6) points it at the IP.
• URL — https://webji.in/pricing/. It carries the domain plus the protocol and path for one page.