Register.Domains Register.Domains
Cart

View Domains

Check Out

Your cart is empty

Contact Us

For email assistance, just contact us

Services

How Long Does Domain Registration Take? Processing Time by Extension

Written by Steven White ·

How Long Does Domain Registration Take? Processing Time by Extension

Most domains register in minutes. A .com, .net, .org, almost any new gTLD and open country codes such as .co.uk, .de or .ca are live the same day. In the Register.Domains catalog of 1,187 active extensions (October 2026), 893 are set to register the same day; the other 294 take from 2 days to 10 weeks, because the registry checks documents (a local company, a trademark, an ID) or reviews each application by hand: about 5 days for .cn, 2 weeks for .sa, 3-4 weeks for .swiss and 4-6 weeks or more for .edu. You can search a name and see its extension's requirements before you order.

Figures checked on 11 October 2026 against our own extension settings and product pages, and against the published rules of the registries named below. Registry rules change: each extension links to its page, which is kept up to date.

The short answer: it depends on who checks the application

The time a domain takes is not decided by the registrar's checkout but by what the registry does with the application. There are four cases:

  1. Real-time registration (minutes). The registrar sends the order to the registry's system and gets an answer at once. This is how .com, .net, .org, nearly all new gTLDs and most open ccTLDs work.
  2. Registered at once, checked afterwards (minutes, then a deadline). The domain is created immediately, but the registry or the registrar must verify the owner's email, phone or identity within a fixed period, or the domain is suspended.
  3. Documents before registration (3 days to 3 weeks). The registry will not create the domain until it has seen a company certificate, a trademark or an ID that matches the name. The clock starts when the documents arrive, not when you pay.
  4. Manual review (2 to 8 weeks). A person at the registry reviews every application, sometimes on signed paper forms. Nothing a registrar does makes this faster.

Registration time across 1,187 extensions

This is the processing time we quote for every extension we sell, grouped by length. It includes the time a registry takes to review documents once they are complete, so it is what to plan for, not a best case.

Registration time Extensions Share Examples
Same day (usually minutes) 893 75% .com, .net, .org, .io, .ai, .co, .de, .co.uk, .ca, .com.au, .fr, .it, .es
2-3 days 120 10% .no, .gr, .nz, .co.th, .com.hk, .com.my
4-7 days 93 8% .cn, .vn, .eg, .co.jp, .ie, .qa
8-15 days 40 3% .sa, .com.sa, .om, .lk, .iq
3-4 weeks 35 3% .jo, .com.np, .swiss, .edu
5-10 weeks 6 0.5% .bg, .com.kw, .gm

The split is very different between generic and country extensions:

Type Active extensions Same day Slower
Generic TLDs (.com, .shop, .app…) 544 537 (98.7%) 7 (.edu, .swiss, .int and a few others)
Country codes, first level (.de, .cn, .sa…) 222 127 (57%) 95
Country codes, second level (.co.uk, .com.cn, .co.jp…) 408 223 (55%) 185

In other words: if you are buying a generic extension, the wait is almost never the problem. If you are buying a country code, nearly half of them involve some kind of check.

The slow ones: what the registry checks and how long it takes

These are the extensions people most often ask about: the time we quote, and what the registry itself publishes. Where a registry's own figure is shorter than ours, the difference is almost always the documents: the registry's clock starts when it has everything it needs.

Days: identity or company checks

Extension Time What holds it up
.cn, .com.cn About 5 days Every owner verifies their identity (passport or business licence). The registrar checks the documents and sends them to CNNIC within one working day; CNNIC re-reviews them within two working days, and the domain is only registered once it passes (CNNIC Implementing Rules art. 19 and registration FAQ).
.co.th About 3 days A Thai company (company affidavit, VAT P.P.20, commercial registration) or a Thai trademark. Since March 2026, THNIC lets you register first and send the documents within two to four weeks, or it may suspend the name.
.com.hk About 3 days A Hong Kong Business Registration Certificate for the head office (a branch is not accepted) or an overseas-company certificate (HKIRC Registration Policy 3.6). Plain .hk generally needs no documents and registers the same day.
.com.my About 3 days A company or business registered in Malaysia; MYNIC cross-checks every application against the eligibility rules (Registrant Policy 10.1.2). Plain .my is open to anyone.
.vn, .com.vn About 4 days Vietnam verifies the holder of every .vn domain: a passport or company certificate plus a signed form. The domain stays pending until they arrive.
.co.jp About 7 days Only companies registered in Japan, one .co.jp per company. JPRS checks eligibility against the commercial register and notifies the result “in principle” within 10 days (JPRS rules art. 18). Plain .jp only needs a Japanese address and registers the same day.
.ie About 7 days A real connection to Ireland. Once that is proven, the registry says applications are “usually processed within 3 hours, Monday to Friday” and go live at the next zone reload (every odd hour). The wait is the proof: an application without it is held for up to 27 days.
.qa About 7 days Open to anyone, no documents (Qatar's regulator lists .qa as “open for all”), but the owner's phone number must be confirmed after registration. .com.qa is only for businesses registered in Qatar.

Weeks: manual review or local-company rules

Extension Time What holds it up
.sa, .com.sa Up to 2 weeks A company registered in Saudi Arabia or a trademark registered there, matching the name (SaudiNIC Regulations v5.0, 4-1 and 4-3). SaudiNIC reviews every application and can ask for documents at any time; it publishes no processing time.
.jo, .com.jo About 3 weeks A company with a trademark registered in Jordan (or a Madrid trademark covering Jordan) that matches the name, a power of attorney and a local presence. The clock starts when the documents are complete.
.com.np About 3 weeks A trademark or company registered in Nepal that matches the name; foreign trademarks are not accepted.
.swiss 3-4 weeks Only the Swiss community. Applications that pass a first check are published on Tuesdays for 20 days; if nobody objects or competes, the name is assigned “in principle within a period of 3 days” (nic.swiss). The registry also checks the company's UID and its link to the name.
.edu 4-6 weeks or more Only accredited U.S. post-secondary institutions. EDUCAUSE staff review every application, which “can take 4-6 weeks or even longer depending on the application volume”; the name is not active until approved.
.bg Allow up to 5 weeks with paper forms The owner must identify themselves, with a qualified digital signature or with documents. Under the registry's terms in force since 9 August 2026, an application must be confirmed within 24 hours, documents are checked within three business days, and proving a right to the name is optional (without it the name is registered as “unprotected”).
.com.kw Up to 8 weeks A company name or trademark matching the domain, a local representative in Kuwait and a signed letter of authorization. The 8 weeks count from the day the documents arrive.

Two patterns repeat. First, where a name must match a company or a trademark (.sa, .jo, .com.np, .com.kw, .eg), the registry rejects names it cannot tie to a certificate, so the time depends on how clean that match is. Second, where a local presence is required, a Trustee or local-presence service removes the eligibility problem but not the registry's review time. Our guide to ccTLD local presence requirements lists which countries need one.

Registered is not the same as working

A domain can be registered in seconds and still not load, or be suspended a few days later. Three things happen after the order:

1. Contact verification

Every ICANN-accredited registrar, and a growing number of country registries, now verify that the owner is reachable, often after the domain already exists. Miss the deadline and the domain stops working.

Where What is checked Deadline and consequence
.com, .net, .org and all ICANN gTLDs The owner's email address or phone number, with a code or link The registrar must verify within 15 days of a registration, transfer or change of owner; with no response, it verifies manually or suspends the domain (ICANN 2013 RAA, WHOIS Accuracy Program Specification)
.de Full name, street address (not a P.O. box), working phone and email; you confirm a verification email If the details cannot be verified, the registry takes the domain out of the zone and later deletes it
.dk The registry may ask the owner for ID and proof of address The domain does not work until the check is done; after 25 days it is suspended and then deleted
.pt The owner's tax number; the registry may ask for a tax certificate or ID The domain stays pending until the details are confirmed
.qa The owner's phone number An unconfirmed domain can be deleted by the Qatari authorities
.co.no The owner's email address and phone number Confirmation is needed to keep the domain active
.bg Confirmation of the application by email or digital signature Within 24 hours, or the application lapses (Register.BG terms 7.1.3)

The practical rule: use contact details where you can actually be reached, and answer the registry's email the day it arrives.

2. Nameserver checks

Some registries test your DNS before they accept it. In our catalog, 34 extensions are flagged for this, including .de, .it, .dk, .no, .pt, .si, .hu, .lu, .is, .com.br and .co.za. Germany's registry, for example, requires that “all name servers stated in the request must be reachable and authoritative for the requested zone”. If you register one of these and point it to a hosting provider that has not yet created the zone, the registration or the nameserver change fails until it has. Create the DNS zone first, then change the nameservers. Our Google Workspace MX records guide walks through the order.

3. DNS caching (the “propagation” delay)

Registries publish new domains fast. The .com registry agreement commits Verisign to update the .com zone within 3 minutes for 95% of changes, and ICANN's standard contract for new gTLDs requires 60 minutes or less for 95% of probes. The .ie registry reloads its zone every odd hour. After that, there is one more delay that has nothing to do with the registrar. If you, your browser or your office network looked the name up before you registered it, DNS resolvers remember the “this domain does not exist” answer for a period set by the registry (RFC 2308). On 11 October 2026 that period was 15 minutes for .com and .net, about 1 hour for .org, 2 hours for .de and 3 hours for .uk. After that, changes to your own records take as long as the TTL you set on them (RFC 1035): a record with a 1-hour TTL can be served from cache for up to an hour after you change it. The “up to 48 hours” you often see quoted applies to changing the nameservers of a domain that already works, because resolvers may keep the old ones cached; it is not the time a new registration takes.

How long does a domain transfer take?

For .com and the other gTLDs, a transfer usually finishes within five days of the request. Once you request the transfer with the authorization code, ICANN's Transfer Policy gives the current registrar five calendar days to respond; if it does not, the transfer is approved automatically (Transfer Policy §3.5). Approving the transfer email from your current registrar can end the wait earlier.

Two limits to know:

  • Not right after registration. Today a registrar may refuse a transfer within 60 days of registration or of a previous transfer (§3.7.5-3.7.6). The new Transfer Policy, adopted by the ICANN Board on 7 June 2026, makes this a mandatory 30-day (720-hour) restriction and keeps the five days, written as 120 hours. As of October 2026, ICANN has not set the date it takes effect.
  • Country codes follow their own rules. In our catalog, 1,177 extensions are given up to 10 days to complete an incoming transfer, and 10 are given up to 21 days because their registries process transfers by hand: .sa, .com.sa, .iq, .com.iq, .com.kw, .mo, .com.mo, .gm, .aw and .bf.

The step-by-step process is in our guide on how to transfer your domain name, and you can start one from the domain transfer page.

How to get a slow extension registered faster

  • Read the requirement before you order. Every extension page lists what the registry asks for. Most delays are documents that arrive late or do not match.
  • Have the documents ready as PDFs or color scans: company certificate, trademark certificate, passport. For .com.hk the certificate must be the head office's, not a branch's; CNNIC asks for color copies for .cn.
  • Make the name match exactly. Where the domain must match a company or trademark (.sa, .jo, .eg, .ua, .com.np), a missing word or an added hyphen is enough for a rejection.
  • Use real, reachable contact details and answer verification emails or calls the same day; several registries suspend or delete domains whose details cannot be confirmed.
  • Use a Trustee or local-presence service where you are not eligible: it solves eligibility for extensions such as .sa, .jo, .no, .it or .hu, though the registry still takes its usual time.
  • Order early if you need the domain for a launch date: for a 3-8 week extension, start before the website is built, not after.

Ready to start? Search your domain name to see whether it is available and what its extension requires, or go straight to the page for .cn, .sa, .jp and .co.jp, .ie or .swiss.

More Articles

Google Workspace MX, SPF, DKIM and DMARC in one table
Google Workspace MX, SPF, DKIM and DMARC in one table

Google Workspace needs one MX record: smtp.google.com with priority 1. This guide puts the five DNS records Workspace uses in one table, explains the legacy ASPMX set, gives the order and waiting times that avoid lost email, and covers the ccTLDs (.de, .it, .no) whose registries check your nameservers before accepting a DNS move.

.ai goes multilingual: 57 IDN languages from 19 October
.ai goes multilingual: 57 IDN languages from 19 October

The .ai registry enables internationalized domain names (IDNs) for .ai, com.ai, net.ai, off.ai and org.ai on 19 October 2026, after a test phase for registrars from 7 October. This guide lists all 57 supported languages and scripts with their IDN tags, explains the difference between a language and a script entry, shows how IDN .ai names look in punycode, and covers what to check for browsers and email.

.dot launch: dates, rules and the route that fits you
.dot launch: dates, rules and the route that fits you

.dot, the new open domain extension from Dish DBS, reaches General Availability on 2 November 2026. This guide covers the Sunrise, Early Access and GA dates, which route fits trademark owners, developers and everyone else, the registry rules registrars don't publish, and how it differs from Polkadot's .dot names.

More Articles