Updated on 23 Jul 2026

You type a web address into a browser, and a page loads. Most of the time. The whole thing feels instant – but between the name you typed and the page you see, a chain of organisations, databases and records all had to agree on where to send you.

Domain registration is the process that puts your name into that chain. The actual registration can be quick, but the choices around it can follow you for years – renewal settings, DNS access, TLD rules and the registrar you trust with it all. Once you understand what’s happening behind the scenes, domain names feel less like internet admin and more like something you can properly control.

What happens when you register a domain name

Registering a domain name is a bit like reserving a table at a restaurant. You don't buy the table. You book it for a set period, and your name goes on the list so nobody else can claim it while it's yours.

When you register a domain, you're paying for the exclusive right to use that name for a fixed term. Your contact details go into a public (or privacy-protected) database, and DNS records get created so that browsers know where to find your site.

You don't own the name outright. You lease it, renew it and manage it through a registrar. If you stop renewing, the name eventually goes back into the pool for anyone else to register. The process itself is straightforward once you know what to expect. If you’re ready to choose and secure a name, start with how to register a domain name.

The organisations behind every domain

Three types of organisations work together to keep the domain system running. Each one has a different job, and they sit in a chain from global oversight down to the company you hand your money to.

ICANN

ICANN (the Internet Corporation for Assigned Names and Numbers) coordinates the global domain name system. It sets the policies for how domains are created, managed and transferred, accredits registrars, and maintains the root zone of the internet. This is the master directory that tells the whole system where to find .com, .org, .net and every other extension.

ICANN doesn't sell domains to the public. It runs the framework that everyone else operates within. Think of it as the regulator that decides the rules of the game but doesn't play.

For country-code TLDs, like .uk, .de or .au, ICANN's role is less direct. Those extensions are managed by national registries under their own policies. For example, Nominet runs .uk and DENIC runs .de. These registries connect to the same global root system, but they set their own registration rules, pricing structures and dispute processes. That's why you’ll find that registering a .co.uk domain sometimes works a bit differently from registering a .com.

Registries

A registry manages one specific top-level domain (TLD). For example, Verisign runs .com and .net and Nominet manages .uk and .co.uk. The registry is the organisation that holds the definitive database of every single domain registered under its extension. It also maintains the zone files that make DNS lookups possible.

If it helps, think of the registry as a land registry. It records who holds what, keeps the records accurate and makes sure the system works. But, like ICANN, it doesn't deal with the public directly. You can't contact Verisign and ask to buy a .com. Instead, you go through a registrar.

Each registry also decides the rules for its TLD. Some require registrants to meet specific criteria, which might be a trading address in the UK for certain .uk domains, for instance. Others, like .com, are open to anyone anywhere in the world.

Domain registrars

A domain registrar is usually the only company you deal with directly when registering a domain name. For generic TLDs, such as .com or .net, registrars are accredited by ICANN and connected to the relevant registry operator, such as Verisign. For country-code TLDs, such as .uk, registrars work under the rules of the relevant national registry.

When you search for a domain, pay for it and configure your DNS records, you're doing all of that through your registrar. They handle the billing, the account management and the interface you log into. Behind the scenes, they submit the registration to the registry, which adds it to the master database.

Registrars compete on price, support and the services they bundle alongside domains, such as hosting, email, SSL certificates, and website builder tools. With Fasthosts domain names, you can register your domain, manage DNS, and add hosting, email or a website builder from the same account.

Some registrars also work through resellers. These are third parties that are authorised to sell domains on the registrar's behalf. The registrar still handles the actual registration with the registry, but the reseller is your day-to-day contact. If you're buying through a web agency or a smaller hosting provider, there's a good chance they're reselling for a larger registrar.

Who do you deal with?

In almost every situation, you deal with your registrar. They're the company you pay, the dashboard you log into and the support team you contact if something goes wrong.

You'd only interact with a registry directly in unusual circumstances, like a domain dispute through Nominet, for example, or a bulk transfer that needs registry-level approval. And you'd only encounter ICANN if you needed to file a complaint about a registrar's conduct or pursue a domain dispute through the Uniform Domain-Name Dispute-Resolution Policy (UDRP).

For day-to-day domain management (renewals, DNS changes, contact updates, transfers), your registrar is the single point of contact.

Why different TLDs have different rules

A domain extension isn’t just the bit after the dot. It decides which registry manages your domain, which transfer process applies, how your contact details are handled and, in some cases, who’s allowed to register the name in the first place. That’s why a .com, .co.uk and .app domain can have different rules, even when you buy them from the same registrar.

Generic TLDs (gTLDs)

These are the extensions managed under ICANN's direct authority – .com, .net, .org, .info, .biz and others. They're open to anyone, regardless of location. Registration, transfer and renewal follow ICANN's standardised policies, which includes the requirement to verify your email address within 15 days and a 60-day transfer lock after registration.

gTLDs are the most uniform. The rules are the same whether you register through a UK-based registrar or one in another country.

Country-code TLDs (ccTLDs)

Each country has its own two-letter extension, like .uk for the United Kingdom, .de for Germany, .fr for France, and .au for Australia. These are managed by national registries, and each one sets its own policies.

For UK businesses, the most common options are .co.uk and .uk. Both are managed by Nominet. The main difference – .co.uk has been around since the early days of the internet and is deeply familiar to UK users. The shorter .uk extension was introduced in 2014 and is gradually becoming more common, though .co.uk still dominates in public recognition.

Nominet's rules differ from ICANN's in a few ways. Transfers between registrars work through a tag system rather than EPP authorisation codes. So, your current registrar changes the "tag" on your domain to point to the new registrar, and the move happens within hours rather than days. WHOIS privacy also works differently. Individual registrants have their personal data hidden by default under Nominet's opt-out policy, whereas .com WHOIS privacy usually requires a paid add-on through your registrar.

These differences are worth knowing because they affect how you manage your domain after registration. A .co.uk domain and a .com domain registered through the same account may follow different rules for transfers, disputes and data visibility.

New and specialist TLDs

Since 2014, hundreds of new generic TLDs have launched, such as .shop, .tech, .agency, .london, .blog, .app and many more. These are managed by a range of registries and follow ICANN's gTLD framework, but individual registries can still set additional policies.

For example, .app (run by Google) requires all websites to use HTTPS. Some geographic TLDs, like .london, may require registrants to have a connection to the area. Others are completely open.

These extensions give you more naming flexibility, but they're less widely recognised than .com or .co.uk. A .tech domain might work well for a software business, but a .com still carries more instant familiarity with a general audience. A newer extension can work well when it says something useful about your business. For a closer look at that choice, read more about sector-specific domain names.

WHOIS and domain ownership records

When you register a domain, your contact details are recorded in a database called WHOIS. Historically, this information was fully public, and anyone could look up a domain and see the registrant's name, address, email and phone number.

That changed in 2018 when the EU's General Data Protection Regulation (GDPR) came into force. For gTLDs like .com and .net, registrars are now required to redact personal data from public WHOIS results. Most WHOIS lookups for these extensions now show the registrar's name and a redacted contact, rather than the registrant's personal details. If someone has a legitimate reason to reach the domain holder, such as for a trademark dispute, they can request the data through the registrar.

For .uk domains, Nominet has its own approach. Individual registrants are opted out of public WHOIS display by default. Business registrants have their organisation name and address shown, but individual contact details (like a personal phone number) are hidden unless the registrant chooses to make them public.

This means your personal details are better protected than they used to be, but they do still exist in registrar and registry records. If privacy is important to you, it's worth checking exactly what your registrar displays and whether they offer any additional privacy options.

What DNS registration does behind the scenes

DNS (the Domain Name System) is the part of domain registration that makes your website reachable. Without it, your domain is just a name in a database. DNS is what connects that name to a live server.

Every website has a numerical IP address, like 185.45.16.22. But those are difficult to remember, and nobody types that into a browser. DNS translates your readable domain name into that IP address, so browsers know where to go.

A few DNS records do most of the work:

  • A records point your domain to an IPv4 address
  • AAAA records do the same job for IPv6
  • CNAME records point one domain to another, often for subdomains like www.
  • MX records tell email servers where to deliver mail
  • TXT records help with verification, SPF, DKIM and other security checks

The lookup chain

When someone types your domain into a browser, their request moves through a chain of DNS servers.

First, the browser checks its own cache – has it looked up this domain recently? If not, it asks a recursive DNS resolver, usually run by the visitor's internet provider. The resolver checks the root name servers, which point to the TLD servers for your extension (.com, .co.uk). The TLD servers point to the authoritative name servers for your specific domain. These are the servers that hold your DNS records. Those name servers return the correct IP address, and the browser loads your page.

The whole process takes milliseconds, and because resolvers cache results, repeat visits skip most of those steps entirely.

What happens when DNS goes wrong

If your DNS records are misconfigured, the consequences are immediate. Point your A record to the wrong IP address and visitors see someone else's site or an error message. Delete an MX record by accident and you stop receiving email. Let your name servers lapse and your entire domain goes dark.

This is also where your hosting becomes an important consideration. Your DNS records point to your hosting provider's servers. If those servers are slow, unreliable or frequently offline, your site suffers. And it won’t matter how good your domain name is. Your domain gets people to the door, but your hosting decides how quickly that door opens, which is why reliable Web Hosting counts from day one.

Renewals, expiry and domain squatting

Domains run on a registration period. This is usually 1 or 2 years, though some registrars let you register for up to 10. When that period ends, the domain doesn’t disappear overnight. It moves through a few stages first.

The exact timings vary by TLD and registrar, but the pattern usually looks like this:

  • Grace period – you can still renew at the normal price, and your site may stay connected.
  • Redemption period – recovery may still be possible, but it usually costs more than a standard renewal.
  • Pending delete – the domain is being prepared for release.
  • Open registration – the domain becomes available for someone else to register.

This is where domain squatters and drop-catch services come in. Automated tools monitor expiring domains and snap up valuable names within seconds of release. If your domain includes a common word, a brand name or a short, memorable phrase, there's a real chance someone will grab it if you let it lapse. They may then offer to sell it back to you, but at a significant markup. 

Auto-renewal is the simplest protection. Most registrars offer it, and it's worth turning on the day you register. It doesn't commit you to keeping the domain forever – you can cancel before the renewal date if you no longer need it – but it stops an accidental lapse from becoming a serious problem.

Transfers and why the process differs by TLD

If you want to move your domain to a different registrar, you can do that through a domain transfer process. The steps depend on the type of TLD you’re moving.

For most domains, the process falls into one of two routes:

  • For gTLDs like .com, .net and .org, you request an authorisation code, also called an EPP code or transfer key. You give that code to the new registrar, confirm the transfer and wait. It usually takes 5 to 7 days.
  • For .uk domains, Nominet uses a tag-based system. Your current registrar changes the tag to point to the new registrar, and the transfer can often complete within hours.

In both cases, you should back up any DNS records and email settings before starting a transfer. Some registrars reset DNS records to defaults during a transfer, which can temporarily disrupt your site and email if you're not prepared.

Domain disputes and name protection

Registering a domain name doesn't give you a trademark, and holding a trademark doesn't automatically give you the matching domain. These are separate systems, and they sometimes collide.

If someone registers a domain name that matches or closely resembles your registered trademark (and they're using it in bad faith) you have options.

For gTLDs, the main route is the UDRP (Uniform Domain-Name Dispute-Resolution Policy), administered through ICANN-approved dispute resolution providers like the WIPO Arbitration and Mediation Center. You file a complaint, provide evidence that the domain matches your trademark and that the registrant has no legitimate interest in it. A panel decides whether the domain should be transferred to you or cancelled. The process typically takes a couple of months and costs a few thousand pounds.

For .uk domains, Nominet runs its own Dispute Resolution Service (DRS). The process is similar in principle, but it follows Nominet's own rules rather than ICANN's UDRP. Costs and timescales are broadly comparable.

Neither process is fast or cheap, which is why many businesses take a preventive approach – registering their brand name across several extensions (.com, .co.uk, .uk and any relevant specialist TLDs) at the time of registration. It costs a few extra pounds a year, but it's far cheaper than resolving a dispute later.

The system works if you stay on top of it

The domain registration system is old enough to be dependable, but it still has a lot of moving parts. ICANN sets the global rules, registries keep the TLD databases in order, registrars give you the dashboard, billing and support you use, DNS points the name to the right server, and WHOIS keeps a record of who registered what.

Most of the time, you don't need to think about any of this. Your registrar handles the complexity, your DNS records route traffic in the background and your domain just works. But it pays to understand the machinery, particularly when something goes wrong. A missed renewal, a botched DNS change or a registrar that doesn't give you the tools you need can all cause problems that are much easier to fix if you understand what's happening behind the scenes.

Choosing a name for a new project, or checking whether your current setup still makes sense? You can search for domain names with Fasthosts and keep DNS, hosting and email in one place.

Frequently asked questions

Do I own my domain name once I register it?

Not exactly. You have the exclusive right to use it for the length of your registration period, which could be anything from 1 to 10 years. You need to renew before it expires, or it will eventually become available for someone else to register. Ownership in the legal sense (like owning property) doesn't apply to domain names.

What's the difference between a domain registrar and a domain registry?

A registry manages a top-level domain (like .com or .co.uk) and holds the master database of every name registered under it. A registrar is the company you buy through. They’re accredited by the registry or ICANN to sell domains and manage your account. You deal with the registrar. The registrar deals with the registry.

What happens to my website if my domain expires?

Your site goes offline. Visitors see an error page or a registrar-placed holding page. During the grace period (typically 30-45 days) you can renew at the normal price. After that, you may still be able to recover the domain during the redemption period, but it will cost significantly more. Once the domain is fully released, anyone can register it. Including domain squatters.

Is a domain name the same as a website?

No. A domain name is the address – the name people type to reach you. A website is the content that sits at that address, stored on a hosting server. You need both: a domain to be found and hosting to serve your pages. They can come from the same provider, but they're separate services.