Quick answer
What happens after ClaimExpired catches a name?
A name caught by ClaimExpired 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. Once the 60-day transfer lock that follows a new registration ends, the auth code moves the name to any registrar.
In brief
- Day 0: the name is caught and registered for one year.
- Within 24 hours: the ticket shows the name and asks for a registrant email.
- Days 0 to 60: DNS by ticket; transfers are locked by the registry rules.
- After day 60: the auth code moves the name out, free.
What can be done with the name, and when?
| When | What is possible | How |
|---|---|---|
| Day 0 | Registration for one year, WHOIS privacy on | Done by ClaimExpired |
| Within 24 hours | See the name and give a registrant email | Ticket |
| Days 0 to 60 | Point DNS to your site or mail | Ticket |
| After day 60 | Get the auth code and transfer out | Ticket, then your registrar |
| Before day 365 | Renew, or transfer out to renew elsewhere | Ticket or new registrar |
Why is there a 60-day lock?
Because registries and registrars block transfers for 60 days after a new registration, under ICANN's transfer rules. A caught name counts as a new registration, so it cannot change registrar before day 60. DNS can still change at once, so the name can serve a site or mail from the first day: pointing a caught domain shows how.
Whose name is on the registration?
A caught name needs a registrant email, as ICANN requires; ClaimExpired asks for it in the ticket when the name is caught, and keeps it private behind WHOIS privacy. WHOIS privacy hides that email from public lookups. ClaimExpired asks for no ID document. If the registry of a country-code extension requires more registrant details than an email, the ticket says so before the name is filed, and the credit can move to another name.
What does the second year cost?
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. Many owners move the name to their usual registrar after day 60 and renew it there, as moving a caught name explains. Renewing in time matters: a name that expires again starts the cycle in expired domain lifecycle once more.
What should I do in the first week?
Give a registrant email in the ticket, point the DNS where the name should go, and check that nothing old still points at it. According to ClaimExpired's survey of 17 November 2026, caught names at other services also come with one year included, so the first renewal date is the same idea everywhere: one year after the catch. Old links, mail and search results may still reach the name for weeks after a drop.
If the name had a site before, a redirect or a fresh page avoids serving errors to old visitors. If it had mail, expect stray messages for a while; an MX record pointed at a mailbox you watch shows what still arrives. None of this needs the auth code: everything is done by ticket until day 60.
After-the-catch questions
Can I use the name for email at once?
Yes. Ask for the MX and other DNS records in the ticket; they apply within the DNS caching time.
Is the auth code free?
Yes. It is given in the ticket after the 60-day lock, with no exit fee.
Can I sell the name?
Yes, once it is yours to transfer: after day 60 the auth code moves it to a buyer or a marketplace.
What if the name had a bad history?
Old spam or penalties stay with the name; checking an expired domain explains how to check before backordering.
Verdict
- Point DNS on day one by ticket, and move the name out after day 60 if you prefer another registrar.
- Note the renewal date: day 365 comes quickly.
Three .com, .net or .org names, the first year included on each catch.