The domain registrar vs hosting question comes up when a bill arrives from a company you do not recognise, or when you want to move a site and cannot work out where to log in. The two are often sold together, but they do different jobs, and confusing them is how people lose control of their own domain.
The short version: a registrar sells you the right to use a name; a web host rents you space on a server. DNS, and specifically the nameservers set at your registrar, tells the internet which server answers for that name.
What a domain registrar does
Cloudflare’s explainer on domain name registrars puts it in one line: “A domain name registrar functions as a retailer for web addresses, while a domain name registry maintains the master database and sets wholesale prices for domains.” It adds that “registrars do not actually manage and maintain domain names; that part is done by a domain name registry.”
When a registrar sells a .com, Cloudflare explains, it “must notify VeriSign — the registry for ‘.com’ domains” and pay VeriSign a fee, which is “factored into the price that the registrar charges the end user.” Its analogy: “A registrar is like a dealership for domain names, and the registry is like the manufacturer.”
You do not buy the name outright either. In Cloudflare’s words, “the user never truly owns the domain; they just lease it.” For generic TLDs such as .com, ICANN says any entity selling registrations “with a direct access to the gTLD registries is required to obtain an accreditation from ICANN”. That accreditation “only applies for gTLDs”; country-code extensions are run by their own registry operators.
There is often a fourth party. Resellers “sell domain names on behalf of a registrar in return for a finder’s fee”, and their sites “rarely explicitly state that they are resellers”. ICANN publishes a list of accredited registrars if you need to know who actually holds your registration.
Accreditation brings obligations that hosts do not carry. Under ICANN’s agreement, registrars “must adhere to ICANN’s consensus policies”, including the transfer policy and the UDRP, “must timely submit updated registration information to registries” and “must investigate reported inaccurate contact information”. That is why transfers, disputes and contact changes run through the registrar, never the host.
What web hosting does
Namecheap’s own definition of hosting: “Web hosting is a service that allows you to rent a space on a server to store your website, so it’s available to the world.” When a visitor types your domain, “the hosting server delivers the requested files.” Shared hosting puts “multiple websites” on “the same server and its resources”; dedicated hosting gives you “an entire physical server exclusively for your website”; VPS and cloud sit in between.
Hosting has nothing to do with who holds the name. You can cancel a hosting plan and still own the domain, and you can let a domain lapse while the hosting account stays paid.
Nameservers: how the two connect
The link is DNS. Cloudflare’s documentation on NS records says the nameserver record “indicates which DNS server is authoritative for that domain”, and that “NS records tell the Internet where to go to find out a domain’s IP address.” The nameserver stores the A, MX and CNAME records, so the IP address your domain points to comes from whoever runs those records, usually your host or a DNS provider, not the registrar as such.
You set the nameservers at the registrar. The records themselves live with whoever runs those nameservers: the registrar’s own DNS, your host’s, or a separate DNS provider.
| Role | What it does | Source wording |
|---|---|---|
| Registry | Keeps the master database for a TLD | VeriSign for .com (Cloudflare); “maintain the master database” (ICANN) |
| Registrar | Sells registrations and passes data to the registry | “a dealership for domain names” (Cloudflare) |
| Reseller | Sells on a registrar’s behalf | “in return for a finder’s fee” (Cloudflare) |
| Registrant | You, leasing the name | “they just lease it” (Cloudflare) |
| Nameservers / DNS | Say where the domain points | NS records “tell the Internet where to go” (Cloudflare) |
| Web host | Stores and serves the site files | “rent a space on a server” (Namecheap) |
Which one to log into for each task
- Registrar: renewals, transfers, the authorization code, contact details, privacy, locks and the nameserver setting itself.
- Whoever runs your nameservers: A, MX, TXT and CNAME records.
- Host: site files, databases and, if it provides them, mailboxes.
Not sure who your registrar is? Cloudflare’s DNS setup guide says: “If you do not know your provider, use ICANN Lookup.” An RDAP lookup shows the registrar, and the free Domain Expiry Checker shows when the domain expires and, if it has lapsed, which stage it is in. The status codes in the same record are explained in our guide to domain status codes.
Changing host without moving the registrar
Moving host does not need a transfer, an authorization code or the post-transfer lock. You change the nameservers, or just the records, at your registrar. At Namecheap that means Domain List, Manage, then the Nameservers section, where “CustomDNS” takes “the nameservers provided by your hosting or third-party DNS provider”.
Three warnings from the providers’ own documentation:
- Copy your records first. Namecheap: when you switch nameservers, “the host records will not be added to the new nameservers automatically.” Cloudflare adds that email records (MX, SPF, DKIM, DMARC) must be recreated.
- Turn off DNSSEC. Cloudflare: “Changing nameservers while DNSSEC is active can cause your domain to become unreachable.”
- Allow time. Namecheap says changes “may take up to 24 hours (more, in rare cases)”; Cloudflare says it “may take several hours”. Neither is a fixed figure.
Moving the other way, changing registrar but keeping the host, is a transfer. You will need the domain authorization code, and DNS can stay as it is if the nameservers do not change. One exception: Cloudflare Registrar’s FAQ says “all domains on Cloudflare Registrar use Cloudflare nameservers”, though you can still point the records at any host.
Domain registrar vs hosting: same company or separate?
No source says keeping registrar and host together is better or worse; it is a trade-off. One account and one bill is simpler. Keeping the domain at a separate registrar means leaving a host never puts the name itself at risk.
The risk worth checking is simpler: whose account is the domain registered in? If a developer, agency or host registered it under their own account, the registrant may not be you, and every task in the registrar list above needs their cooperation. Moving it into your name is covered in how to transfer a domain to another person.
A limitation: this guide describes gTLD rules and the published documentation of two providers, checked 19 October 2026. Country-code registries and other registrars can work differently, and menus change.
Frequently asked questions
Can my domain registrar and web host be different companies?
Yes. Point the domain’s nameservers, or its records, at the host. The registration stays where it is.
Does changing web host mean transferring my domain?
No. A host change is a nameserver or DNS record change at your registrar. A transfer, with an authorization code, is only needed to change registrar.
Is a domain reseller the same as a registrar?
No. Cloudflare says resellers sell “on behalf of a registrar”, and that their sites rarely say so. ICANN’s list of accredited registrars shows who actually holds a gTLD registration.
Who do I pay to renew my domain?
Your registrar (or the reseller you bought through). Your hosting renewal is a separate bill, and paying one does not renew the other.
The takeaway Registrar for the name, host for the files, nameservers in between. Keep the registration in your own account, and a change of host becomes a DNS edit rather than a transfer.
