What does a domain transfer readiness check establish?
This checker reads public registration data and applies its versioned transfer-policy checks. It can identify a published transfer prohibition or a recent registration event. It cannot access your registrar account, obtain an authorization code, or confirm that the receiving registrar will accept the transfer.
Read unknown findings alongside blockers. A missing transfer date does not prove that the name hasn't moved recently. A record without a transfer-prohibited status also says nothing about whether you can sign in to the account.
Which transfer locks can you remove?
| Finding | What to verify |
|---|---|
clientTransferProhibited | The registrar set a transfer prohibition. Check its unlock process; an account switch may be available, but other restrictions can still apply. |
serverTransferProhibited | The registry set a prohibition. Ask the registrar why it exists and what is required to remove it. |
| Recent registration or transfer | The reported event falls within the tool's policy timing check. Confirm the actual restriction and any exception with the registrar. |
| Missing date or account information | The public record cannot settle that condition. Check your account or ask support rather than treating the gap as permission. |
The EPP status reference explains these codes. A code names a condition, not always the reason behind it.
How should I read the 60-day policy check?
The implemented policy model checks 60-day windows after registration and registrar transfer. The ICANN Transfer Policy includes exceptions and distinctions: a recent transfer can have a shorter restricted period, and a registrar may offer an opt-out before a change-of-registrant lock applies.
That makes a timing finding a reason to verify the registrar's rule, not a guaranteed unlock appointment. The result identifies the policy version used. A proposed or adopted replacement must not be treated as effective merely because it was announced.
Changes to registrant details are particularly important before a move. This tool cannot reconstruct that account history from a public last-changed timestamp. Ask the registrar before changing contact details solely to prepare a transfer.
How do I prepare the transfer without interrupting service?
First confirm where DNS is hosted. Moving the registration does not itself copy your DNS zone, website, or mail service. If DNS hosting comes with the outgoing registrar, find out whether it continues after the move.
Keep a copy of the zone and verify any replacement nameservers before switching. If DNSSEC is enabled, coordinate the keys and parent DS records with the providers. A mismatched signing chain can cause validating resolvers to reject answers. Use the DNSSEC checker and nameserver checker to inspect those parts separately.
Once the service arrangements are clear, follow the receiving registrar's transfer process. This commonly involves unlocking the domain, retrieving an authorization code, starting the transfer, and completing the requested confirmations. Approval methods and timing vary, so use the provider's instructions rather than expecting one universal email sequence. Keep the authorization code out of this tool and out of public messages.
What still needs an account check?
Confirm access to the current account, a working contact route, any required authorization code, renewal status, and the registrar's explanation of outstanding restrictions. The checker cannot determine whether a balance, verification request, dispute, or recent account change affects your case.
If expiry is approaching, resolve renewal timing before relying on a transfer to save the name. The expiry checker shows the public dates, but the registrar must confirm the deadline and payment.
Do country-code domains use the same process?
Not necessarily. The generic-domain timing model is not a substitute for a country-code registry's transfer policy. Check the registry's documented procedure, required identifiers, eligibility rules, and any renewal effect. The TLD directory helps identify the registry.
This is a remote, point-in-time check. The submitted domain goes through stack127's server to registration services, and registered responses may be cached for up to 24 hours. It doesn't initiate a transfer or monitor one. Use the registrar lookup to find the public provider details when you need to follow up.