# Domain transfer rules by extension (2026 data) > Domain transfer rules for 40 extensions, checked 19 October 2026: 29 extend the term, 9 move in real time, .uk needs no code. Free CC BY 4.0 table. - URL: https://transferoffshore.com/data/domain-transfer-rules-by-extension/ - Last updated: 2026-10-19 - Publisher: TransferOffshore (https://transferoffshore.com) One row per extension: how the domain moves, whether a year is added, how long the code stays valid, which lock applies after registration, how long it takes and who runs the registry. 40 extensions, each with a confidence label. **Quick answer — What are the domain transfer rules for each extension?** As of 19 October 2026, TransferOffshore's table of 40 extensions shows that 29 extend the term on transfer, 8 keep the old expiry date and 3 depend on the registrar or conflicting sources. 9 complete immediately or in real time, 20 list a 60-day lock after registration, and only .uk moves without a code. ## Key numbers - **29 / 40** extend the term on transfer - **8 / 40** keep the old expiry date - **9 / 40** complete immediately or in real time - **20 / 40** list a 60-day lock after registration - **1 / 40** moves without a code (.uk) ## Domain transfer rules for 40 extensions Read on 19 October 2026. "Registrar notes" means a registrar knowledge base, a secondary source. Linked extensions have their own transfer guide on this site; the six marked "not sold here" are listed for reference only. | Extension | Mechanism | Year added | Code validity | Lock after registration | Typical time | Registry | Confidence | | --- | --- | --- | --- | --- | --- | --- | --- | | [.com](https://transferoffshore.com/transfer/com/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | Verisign | Primary + secondary | | [.net](https://transferoffshore.com/transfer/net/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (ICANN may-deny) | Up to 5 days | Verisign | Primary (ICANN only) | | [.org](https://transferoffshore.com/transfer/org/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | Not stated | Up to 5 days | Public Interest Registry | Secondary | | [.info](https://transferoffshore.com/transfer/info/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | Identity Digital | Secondary | | [.biz](https://transferoffshore.com/transfer/biz/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | GoDaddy Registry | Secondary | | [.xyz](https://transferoffshore.com/transfer/xyz/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | XYZ.COM LLC | Secondary | | [.app](https://transferoffshore.com/transfer/app/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | Not stated | Up to 5 days | Google Registry | Secondary | | [.dev](https://transferoffshore.com/transfer/dev/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (ICANN may-deny) | Up to 5 days | Google Registry | Primary (ICANN only) | | [.online](https://transferoffshore.com/transfer/online/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | Radix | Secondary | | [.shop](https://transferoffshore.com/transfer/shop/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | Not stated | Up to 5 days | GMO Registry | Secondary | | [.store](https://transferoffshore.com/transfer/store/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (assumed) | Up to 5 days | Radix | Primary (ICANN only) | | [.site](https://transferoffshore.com/transfer/site/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (assumed) | Up to 5 days | Radix | Primary (ICANN only) | | [.tech](https://transferoffshore.com/transfer/tech/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (assumed) | Up to 5 days | Radix | Primary (ICANN only) | | [.top](https://transferoffshore.com/transfer/top/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days, also after a transfer | Up to 5 days | .top Registry | Secondary | | [.pro](https://transferoffshore.com/transfer/pro/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days (ICANN may-deny) | Up to 5 days | Identity Digital | Primary (ICANN only) | | [.cloud](https://transferoffshore.com/transfer/cloud/) | EPP auth code | +1 year (10-year cap) | Not fixed (gTLD rules today) | 60 days | Up to 5 days | Aruba PEC | Secondary | | [.io](https://transferoffshore.com/transfer/io/) | EPP auth code (also a one-time password for some operations) | Yes, length not stated | Not published | 60 days | About 5 days | Internet Computer Bureau (Identity Digital) | Secondary | | [.ai](https://transferoffshore.com/transfer/ai/) | EPP auth code | +2 years at the registry (since 15 Jan 2025) | Not published | None found | Losing registrar has 7 days | Government of Anguilla; run by Identity Digital | Secondary | | [.co](https://transferoffshore.com/transfer/co/) | EPP auth code (16 to 48 characters) | Yes, length not stated (5-year maximum term) | Not published | 60 days, also after a transfer | Up to 5 days | .CO Internet | Secondary | | [.me](https://transferoffshore.com/transfer/me/) | EPP auth code | Yes, length not stated | Not published | 60 days | About 5 days | doMEn | Secondary | | [.tv](https://transferoffshore.com/transfer/tv/) | EPP auth code | Yes, length not stated | Not published | 60 days, also after a transfer | Up to 5 days | GoDaddy Registry (registrar notes: Verisign) | Secondary | | [.cc](https://transferoffshore.com/transfer/cc/) | EPP auth code | Yes, length not stated | Not published | 60 days, also after a transfer | Up to 5 days | eNIC (Verisign) | Secondary | | [.gg](https://transferoffshore.com/transfer/gg/) | EPP auth code | Yes, length not stated | Not published | None stated | Real-time | Island Networks | Secondary | | [.to](https://transferoffshore.com/transfer/to/) | Auth code (16 to 48 characters) | Yes, length not stated | Not published | 60 days | About 5 days | Tonic | Secondary | | [.ch](https://transferoffshore.com/transfer/ch/) | Transfer code from the current registrar | No | Not published | None found (60 days after a transfer, secondary) | Not stated | SWITCH | Mixed | | [.de](https://transferoffshore.com/transfer/de/) | AuthInfo from the current provider | Registrar-specific (notes: renews 1 year) | 30 days, single use | None found | Immediate | DENIC | Primary (mechanism) | | [.uk](https://transferoffshore.com/transfer/uk/) | IPS tag change, no code (until 9 Feb 2027) | No (expiry kept) | No code; from 2027 a TAC valid up to 14 days | None found | Not stated (times out after 15 days) | Nominet | Mixed | | [.nl](https://transferoffshore.com/transfer/nl/) | Transfer token, due within 5 days | Registrar-specific (notes: renews, default 1 year) | Not found | None | Immediate | SIDN | Primary + secondary | | .pl | Auth code | No | Not published | None | About 5 days | NASK | Secondary | | .be | Transfer code emailed by the registry | Conflicting sources | 7 days | None found | Real-time (secondary) | DNS Belgium | Mixed | | .at | AuthInfo, or a registry token request | No | 21 days (registry token) | None | Immediate | nic.at | Secondary | | .cz | AuthInfo from the registrar or CZ.NIC | No | Not published | None found | Not stated | CZ.NIC | Secondary | | .fi | Transfer key, due within 5 working days | No | 30 days | None | Real-time (secondary) | Traficom | Primary + secondary | | .nz | Authorisation code (ex-UDAI), single use | No | 30 days | None (blocked in the Registration Grace Period) | Real-time | InternetNZ | Primary + secondary | | .eu (not sold here) | Transfer authorisation code | Yes per registrar notes (not confirmed by EURid) | 40 days or until used | None | Real-time | EURid | Mixed | | .us (not sold here) | EPP auth code | Yes, length not stated | Not published | 60 days | 10 days (registrar notes, unverified) | GoDaddy Registry | Secondary | | .fr (not sold here) | Auth code | +1 year (10-year cap) | Not published | None | 8 days (22 if refused) | Afnic | Primary | | .ca (not sold here) | Auth code, due within 5 calendar days | +1 year (10-year cap) | Not published | Not stated | Real-time (secondary) | CIRA | Primary | | .es (not sold here) | AuthCode sent by the registry; admin contact approves by email | No | 10 days | None | Up to 10 days | Red.es | Primary + secondary | | .it (not sold here) | AuthInfo | +1 year (secondary) | Not published | None | Conflicting: 1 day (nic.it) or 5 days | Registro .it | Mixed | You may reuse this table under CC BY 4.0 with a link to this page. Prices for the extensions we sell are on the [price list](https://transferoffshore.com/pricing/). ## What are the key findings? **Most transfers buy time, but not all.** 29 of the 40 extensions extend the registration when a transfer completes. For 19 of them the gain is exactly one year, capped at 10 years in total: the 16 gTLDs in the table plus .fr, .ca and .it. One extension, .ai, adds two years at the registry; TransferOffshore bills a .ai transfer as 2 years, the transfer price plus one renewal ($172.98). For 9 others, registrar notes confirm a renewal but not its length. **Eight keep the expiry date.** .uk, .ch, .pl, .at, .cz, .fi, .nz and .es do not add time. If one of these expires soon, renew it before or right after the move. A transfer alone will not save it. **Three depend on the registrar or on conflicting sources.** DENIC (.de) and SIDN (.nl) bill registrars by period, so the registrar decides how the term is counted. For .be, DNS Belgium's pages and a registrar knowledge base disagree. **Nine are fast.** .de, .nl and .at move immediately once the code matches. .gg, .be, .fi, .nz, .eu and .ca are described as real-time. The gTLDs all allow up to 5 days, because the losing registrar has five calendar days to object. **One needs no code.** A .uk moves when the current registrar changes its Nominet IPS tag. That changes on 9 February 2027, according to Realtime Register. ## How long is a transfer code valid? For gTLDs, there is no fixed lifetime today. The ICANN Transfer Policy in force sets deadlines for giving the code, not for how long it works. Each registrar decides. Seven country-code registries publish a lifetime: - **.be:** 7 days, and the code is emailed by DNS Belgium itself. - **.es:** 10 days, and the administrative contact must also approve by email. - **.at:** 21 days for a code requested from the registry. - **.de, .fi, .nz:** 30 days. The .de and .nz codes work for one transfer only. - **.eu:** 40 days, or until used. The adopted ICANN reform will bring gTLDs in line: a Transfer Authorization Code valid for 14 days and usable once. Nominet plans the same 14-day ceiling for .uk from February 2027. ## Which locks block a transfer after registration? 20 of the 40 extensions list a 60-day lock after registration. Two sources create it. For gTLDs, ICANN's Transfer Policy lets the registrar refuse a transfer within 60 days of creation or of a previous transfer. Some registries turn that option into a hard registry lock; registrar notes list it for .com, .info, .biz, .xyz, .online, .cloud and .top. Several country codes apply their own 60-day lock: .io, .co, .me, .tv, .cc, .to and .us. For .co, .tv, .cc and .top, registrar notes also list a lock after each transfer. .ch may set one for 60 days after a transfer too, but only a secondary source says so. Most European registries, and .nz, have no such lock. .de, .nl, .pl, .at, .fi, .nz, .es, .fr and .it list none. In .nz, the only block is the Registration Grace Period. ## What changes with the ICANN TAC rules? The ICANN Board adopted the Transfer Policy Review recommendations on 7 June 2026 (resolution 2026.06.07.04). It directed ICANN to implement them "subject to prioritization". **No effective date has been published.** Until the new policy takes effect, the 2024 text applies, including the 60-day locks. A phase-in of about 18 months appears on one blog; we could not verify it. The main changes in the Final Report of 4 February 2025: - The auth code becomes the Transfer Authorization Code (TAC). Registrars must issue it within 120 hours. - A TAC is valid for 14 days (336 hours) and can be used once. The registry enforces both. - The lock after creation becomes 30 days (720 hours) instead of 60. The same 30 days apply after an inter-registrar transfer. - The Gaining FOA disappears. The losing registrar's notice becomes a "Transfer Confirmation", and the 5-day auto-approval is stated as 120 hours. - The 60-day lock after a change of registrant is removed, with its opt-out. A separate Change of Registrant Data policy replaces it. - New notices: one within 10 minutes of a TAC being issued, and one within 24 hours of a completed transfer. The report text we read keeps the one year added on a gTLD transfer. A separate change from 4 August 2026, announced by Realtime Register, concerns registrant-only approval. It is not part of this reform. Our [ICANN transfer policy news page](https://transferoffshore.com/news/icann-transfer-policy-changes/) follows the implementation. ## How was this table built? Every row was read on 19 October 2026 from free public sources. Each one carries a confidence label: - **Primary:** a registry document or an ICANN text. Example: Afnic's procedure guide for .fr, CIRA's rules for .ca. - **Primary (ICANN only):** the gTLD rule comes from ICANN's Transfer Policy, which binds every gTLD registrar, but the registry was not checked one by one. That applies to .net, .dev, .pro, .site, .store and .tech. - **Primary (mechanism):** for .de, DENIC's page confirms how the code works; the term rule comes from a registrar. - **Primary + secondary:** a registry page confirms part of the row, a registrar knowledge base the rest. - **Secondary:** a registrar knowledge base, mostly the per-extension pages of CentralNic Reseller, or press. They describe registry behaviour as a large registrar sees it. - **Mixed:** sources conflict, or a key fact is secondary only. The count: 14 rows rest at least partly on a primary source, 21 on secondary sources only, and 5 are mixed. Registry operators come from the IANA root zone database where registrar notes disagree. Where a fact could not be confirmed, the cell says so rather than guess. What this table does not cover: registry premium prices, transfer fees at other registrars, and rules for second-level names such as .co.uk. ## How can I reuse or cite this data? You may reuse this table under CC BY 4.0 with a link. Copy it, adapt it or publish it, commercially or not, as long as you credit TransferOffshore and link to this page. A suggested citation: "Domain Transfer Rules by Extension (2026 Data), TransferOffshore, checked 19 October 2026." Rules change. Nominet's move to codes in 2027 and the ICANN reform will both change rows here. The date at the top of the page tells you when the table was last checked. If you find an error, write to support@transferoffshore.com with a source. ## Which of these extensions can I transfer to TransferOffshore? 34 of the 40. The 28 linked extensions have a full [transfer guide](https://transferoffshore.com/transfer/). .pl, .be, .at, .cz, .fi and .nz are also sold, with Domain protection, but have no guide yet. .us, .eu, .fr, .ca, .es and .it are not sold here: their registries require a local presence or an identity check. For the extensions we sell, a transfer costs the same as a renewal: .com $12.49, .net $12.99, .io $53.49. Payment is in crypto, with no ID. Up to 20 domains fit in one request, and your nameservers are kept by default. ## Questions about transfer rules ### Which extensions add a year when transferred? 29 of the 40 in this table extend the term. All gTLDs add exactly one year, capped at 10 years, under ICANN's Transfer Policy. .fr, .ca and .it also add one year. .ai adds two. Nine country codes renew on transfer without a stated length, according to registrar notes. ### Which extensions transfer instantly? Nine are immediate or real-time once the code matches: .de, .nl and .at move immediately, and .gg, .be, .fi, .nz, .eu and .ca are described as real-time. Several of these times come from registrar notes. gTLDs such as .com take up to 5 days. ### When do the new ICANN TAC rules start? No date is published. The ICANN Board adopted the Transfer Policy Review on 7 June 2026, subject to prioritization. An implementation team still has to draft the final text. Until then, the 2024 Transfer Policy applies, with its 60-day locks. ### Why does .uk need no auth code? Nominet uses IPS tags. The current registrar sets the domain's tag to the new registrar's tag, and the domain moves without a code and without a change of expiry. Nominet plans code-based transfers from 9 February 2027, according to Realtime Register. ### Can I use this table on my own site? Yes. The table is published under CC BY 4.0. You may copy and adapt it, including for commercial use, as long as you credit TransferOffshore and link to this page. Please keep the check date with the data. ## Sources (read on 19 October 2026 unless dated otherwise) 1. [Transfer Policy (updated 21 February 2024)](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy) — ICANN (2026-10-19) 2. [Transfer Policy, 2016 text](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en) — ICANN (2026-10-19) 3. [Transfer Policy Review: Final Report to the GNSO Council](https://gnso.icann.org/sites/default/files/policy/2025/correspondence/tpr-team-to-gnso-council-04feb25.pdf-en.pdf) — ICANN GNSO (2025-02-04) 4. [Approved resolutions, regular meeting of the ICANN Board, 7 June 2026](https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-07-06-2026-en) — ICANN (2026-06-07) 5. [Registrant FAQs](https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en) — ICANN (2026-10-19) 6. [Per-extension registry rules (one page per TLD)](https://kb.centralnicreseller.com/domains/tlds/com/) — CentralNic Reseller (2026-10-19) 7. [Provider transfer of .de domains](https://www.denic.de/en/products/de-domains/provider-transfer/) — DENIC eG (2026-10-19) 8. [Transferring your domain name](https://www.sidn.nl/en/nl-domain-name/transferring-your-domain-name) — SIDN (2026-10-19) 9. [Standardisation of the inter-registrar transfer process (proposal)](https://registrars.nominet.uk/wp-content/uploads/2023/04/Standardisation-Inter-Registrar-Transfer-Process-March-2023.pdf) — Nominet (2023-03) 10. [Nominet standardises .uk domains from February 2027](https://realtimeregister.com/blogs/nominet-standardises-uk-domains-from-february-2027) — Realtime Register (2026-10-19) 11. [Identity Digital is now managing .ai domains](https://domainnamewire.com/2025/01/23/identity-digital-is-now-managing-ai-domains-heres-what-this-means-for-registrants/) — Domain Name Wire (2025-01-23) 12. [Procedure guide (.fr)](https://www.afnic.fr/wp-media/uploads/2023/12/Afnic-Procedure-Guide-2024-01.pdf) — Afnic (2024-01) 13. [General registration rules (.ca)](https://www.cira.ca/en/resources/documents/domains/general-registration-rules/) — CIRA (2026-10-19) 14. [Domain name transfers (.es)](https://www.dominios.es/sites/dominios/files/2024-10/domainnametransfers_sgnd_7_20_oct_24.pdf) — Red.es (2024-10) 15. [How can I change registrar? (.fi)](https://www.traficom.fi/en/fi-domains/applying-and-using-fi-domains/how-can-i-change-registrar) — Traficom (2026-10-19) 16. [.nz Rules, version 3.2](https://internetnz.nz/assets/Archives/nz-Rules/Version-3.2-of-.nz-Rules-17-March-2026.pdf) — InternetNZ (2026-03-17) 17. [How can I obtain a transfer authorisation code?](https://help.eurid.eu/hc/en-gb/articles/25997104330525-How-can-I-obtain-a-transfer-authorisation-code) — EURid (2026-10-19) 18. [Transfer code (.be)](https://www.dnsbelgium.be/en/transfer-code) — DNS Belgium (2026-10-19) 19. [Regolamento di assegnazione v8.0 (.it)](https://www.nic.it/sites/default/files/documenti/2022/Regolamento_assegnazione-v8.0.pdf) — Registro .it (2022) 20. [Transferring a .ch domain](https://www.nic.ch/transfer/) — SWITCH (2026-10-19) 21. [Grace periods explained](https://identity.digital/help-articles/grace-periods-explained) — Identity Digital (2026-10-19) 22. [ICANN updates gTLD transfer policy from 4 August 2026](https://realtimeregister.com/blogs/icann-updates-gtld-transfer-policy-from-4-august-2026) — Realtime Register (2026-10-19) **Move your domains with the rules in hand** Up to 20 domains per request, nameservers kept, paid in crypto, no ID. [Start a transfer](https://transferoffshore.com/app/domains/transfer?lang=en) · [See all extension guides](https://transferoffshore.com/transfer/) --- TransferOffshore: TransferOffshore is the domain transfer service of DomaineGoat LLC, a company incorporated in Panama: move one domain or a whole portfolio with its auth codes, keep your DNS running, and pay in crypto with no ID. Domains are registered through our ICANN-accredited registrar partner, shown in the RDAP record.