Buy expired domains with crypto · pay in BTC, USDT, USDC, ETH, SOL, LTC · no ID · first year included · price back if missed
Backorder a name

Guide · transfers · ICANN Transfer Policy read 18 November 2026

How do you transfer a caught domain to another registrar?

Last updated: · 4 min read

Quick answer

How do you transfer a caught domain to another registrar?

Wait for the 60-day lock after registration to end, get the auth code, then start a transfer at your new registrar and approve it. ClaimExpired hands over the auth code in your ticket once the 60 days pass. The first year, included in the $25 .com backorder, is usually extended by the transfer.

In brief
  • 60-day rule: ICANN's Transfer Policy lets a registrar deny a transfer within 60 days of the creation date (section I.A.3.7.5).
  • Auth code: where the registrar issues it on request, it must do so within 5 calendar days (section I.A.5.2).
  • At ClaimExpired: DNS changes on request in the ticket until then; the auth code comes after the lock.
  • Renewal: after the first year, renew where the name sits, or move it out free with the code.

What are the steps?

Five steps, following ICANN's Transfer Policy as updated on 21 February 2024.

  1. Note the creation date

    Read the registration event in the RDAP record of the caught name and add 60 days.

  2. Ask for the auth code

    After day 60, ask for the transfer code in your ClaimExpired ticket.

  3. Start the transfer

    At your new registrar, enter the name and paste the code. Copy it exactly; codes are case-sensitive.

  4. Approve and pay

    Confirm the transfer by the method the new registrar uses, and pay its transfer fee, which usually adds a year.

  5. Check the result

    Once complete, check the registrar in RDAP and set your DNS at the new registrar.

When can a transfer be refused?

ClaimExpired read the transfer-denial grounds in ICANN's Transfer Policy on 18 November 2026; these are the ones that touch a newly caught name.

Grounds in ICANN's Transfer Policy that let or make a registrar refuse a transfer, as they apply to a caught domain
GroundSectionMay or must denyApplies to a caught name?
Within 60 days of the creation dateI.A.3.7.5May denyYes, for the first 60 days
Within 60 days after a prior transferI.A.3.7.6May denyOnly after you move it once
60-day lock after a Change of Registrant, unless opted outII.C.2, I.A.3.8.5Must denyOnly if the registrant changes

Why is there a 60-day wait?

Because the policy lets registrars refuse a transfer within 60 days of the creation date, and most do. The rule protects new registrations from being moved away by fraud. A caught name is a new registration, so the clock starts on the catch day.

A caught name is registered for one year with WHOIS privacy and shown in the ticket within 24 hours of the drop. DNS changes are made on request in the ticket; the transfer code (auth code) is given once the 60-day transfer lock that registries apply after a new registration ends, so the customer can move the name to any registrar. During the lock, the DNS guide shows how to use the name right away.

What does the auth code do?

It proves to the new registrar that the holder agrees to the move. ICANN's policy calls it the AuthInfo code. Where the registrar issues it on request, the policy gives a deadline of five calendar days and asks for the transfer lock to be removed.

At ClaimExpired the code is given in the ticket after the lock. The help page on caught names covers what else the ticket handles.

Should you transfer the name at all?

Only if you want it managed at a registrar of your choice. After the first year the name is renewed at the price of a normal registration at the registrar that holds it, or moved out free with the auth code. Keeping it where it is costs nothing extra during the included first year.

According to ClaimExpired's survey of 17 November 2026, Gname's $26 .com channel and Park.io's $99 also included registration. ClaimExpired includes the first year at $25. The backorder guide compares the rest.

Frequently asked questions

Can the 60-day lock be skipped?

Not for a new registration in practice: the policy lets the registrar refuse, and the code is given only after the lock at ClaimExpired.

Does a transfer add a year to the registration?

For .com and most gTLDs, the new registrar's transfer fee usually includes one more year. Check your new registrar's terms.

Will my site go down during the transfer?

Not if the DNS records stay the same. Copy them to the new registrar or keep the same nameservers before you start.

Can I change the registrant before transferring?

Yes, but a change of registrant can trigger another 60-day lock unless you opt out where offered. Transfer first if you can.

Does WHOIS privacy move with the name?

No. Privacy is a registrar service. Turn it on again at the new registrar if it offers it.

Verdict
  • Use the name through DNS for 60 days, then move it with the auth code.
  • Or keep it where it is: the first year is already paid in the backorder.
Sources (4)
  1. Transfer Policy (updated 21 February 2024) — ICANN (read 2026-11-18)
  2. Transfer Policy (2016 version) — ICANN (read 2026-11-18)
  3. EPP Status Codes: What Do They Mean, and Why Should I Know? — ICANN (read 2026-11-18)
  4. rdap.org — rdap.org (read 2026-11-18)

Catch a name, then take it anywhere

$25 for a .com, .net or .org, first year included, auth code after the 60-day lock.

$25.00 a .com · pay in crypto

Backorder a name