Using the ICANN Accredited Registrar List for Registrar Evaluation and Domain Transfers
Use the ICANN accredited registrar list to confirm that a registrar can hold your generic top-level domains and follows ICANN's transfer rules, then evaluate it on what the list leaves out: corporate service, security, ccTLD coverage, governance and how it actually handles transfers. DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, provides procurement guidance and corporate domain management advice on that evaluation.
A typical situation: an IT manager planning a domain transfer checks that the target registrar is ICANN-accredited, sees that it is and moves on. During the transfer, several country-code domains fail because the registrar does not support them directly. Support takes days to answer. Two critical domains arrive without the registry locks the security team expected, because the registrar does not offer them for those extensions. Accreditation was never the problem. It simply did not cover what mattered.
This article explains how to use the ICANN accredited registrar list in registrar evaluation and domain transfers, and what else to check.
What accreditation means for transfers
ICANN-accredited registrars follow ICANN's transfer policy for gTLDs. That policy covers, among other things, authorization codes, the transfer process between registrars and lock periods such as the 60-day lock after registration or transfer. Accreditation gives you a common baseline for how gTLD transfers work.
What accreditation does not cover in transfers
- ccTLD transfers. These follow each registry's own rules, which can differ sharply.
- Transfer support. How quickly the registrar resolves stuck transfers.
- Bulk handling. How well it processes large numbers of transfer-ins.
- DNS coordination. Whether it helps plan DNS moves to avoid downtime.
- Arrival controls. Whether registry locks and approvals are available for every extension.
Using the list in evaluation
Step 1: confirm gTLD accreditation
Check that each candidate is accredited, or clearly discloses the accredited partner it uses.
Step 2: list your extensions
List every extension you hold. For ccTLDs, check each registrar's direct support or partner arrangement, and any local presence requirement.
Step 3: check transfer experience
Ask each registrar how it handles transfer-ins of your size, how it schedules waves and how it resolves failures.
Step 4: check arrival controls
For critical domains, confirm registry lock support by extension, approval workflows and multi-factor access.
Step 5: check support
Named contacts, response times and escalation paths, especially during transfer windows.
Step 6: check governance
Roles, cost-centre billing, audit logs and notifications.
Each row is a question worth asking in writing, so the answers can be compared later.
Why a test wave helps
A test wave of 20 to 50 low-risk domains reveals how the registrar handles codes, timing and confirmations in practice. It costs little, because the domains are not critical, and it often surfaces issues that would otherwise appear in the middle of a large wave. If the test wave is slow or unclear, there is still time to adjust the plan or the registrar choice before critical domains are involved.
A transfer-readiness table
| Check | Covered by accreditation? | What to ask |
|---|---|---|
| gTLD transfer process | Yes, baseline | Confirm compliance |
| ccTLD transfers | No | Direct support or partner, local presence |
| 60-day lock handling | Yes, for gTLDs | How they schedule around it |
| Bulk transfer-ins | No | Experience at your scale |
| DNS coordination | No | Support for planning DNS moves |
| Registry locks on arrival | No | Availability by extension |
| Support during transfers | No | Contacts and response times |
What ccTLD transfers usually involve
Country-code transfers vary more than any other part of a migration. Some registries use authorization codes like gTLDs. Some require the losing registrar to release the domain or the registrant to confirm by email or in writing. Some need a local contact or a trustee service, and some need documents that show the company's presence in the country. Timing can range from minutes to weeks. Planning ccTLDs as separate waves, with the specific registry rules written down, prevents them from holding up the rest of the transfer.
Checking claims before the transfer
Registrars describe their capabilities in good faith, but descriptions are not the same as experience. Before committing, ask for references from clients of similar size who have moved similar portfolios. Ask how a recent large transfer-in went and what went wrong. Where possible, rely on someone who has worked with the registrar directly. A short test wave of low-risk domains is also a practical check: it shows how codes, timing and support work before anything important moves.
Planning the transfer itself
Even with the right registrar, transfers need a plan: complete inventory, tiers, a do-not-move list, DNS moved first where it sits at the losing registrar, low-risk domains first and critical domains last, with authorization codes collected per wave.
Taken together, these checks turn accreditation from the end of the evaluation into its starting point.
Who should be involved
IT runs the evaluation of technical and transfer capabilities. Security confirms arrival controls. Procurement handles supplier checks and terms. Regional teams confirm ccTLD needs.
Common mistakes
- Treating accreditation as proof of transfer quality.
- Assuming ccTLDs follow the same rules as gTLDs.
- Not asking about registry locks by extension.
- Starting transfers before checking support arrangements.
- Moving legacy domains that should expire.
Where an expert helps
DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov evaluates registrars beyond accreditation, from direct experience of how all the major registrars handle transfers, ccTLDs and arrival controls, and decides which domains should transfer at all.
The consultation is remote, confidential and about one hour. You send the domain list; large lists go in advance, and about 200 domains can be reviewed live. No software, subscription or registrar access is required. Kalin has 17+ years in the domain industry, has personally evaluated more than 1.5 million domains, has managed over 800,000 with his team and has handled more than 10,000 domain transactions. Sometimes he carries out migrations himself. The fee is USD 2,500 per hour, with follow-ups at the same rate.
You don't need to rebuild everything. You need to know what can fail.
What to send
- Exports from every registrar and account.
- Every extension you hold.
- The target registrar or shortlist.
- Critical domains and where DNS is hosted.
Takeaway
In the opening scenario, a check of ccTLD support, registry locks by extension and transfer support would have revealed the gaps before the transfer began. The ICANN accredited registrar list is the first check, not the last.
FAQ
Does ICANN accreditation guarantee smooth transfers? No. It sets a baseline for gTLD transfers; experience and support still vary.
Do ccTLDs follow ICANN transfer rules? No. They follow their own registry rules.
What is the 60-day lock? A restriction on transferring gTLDs registered or transferred within the previous 60 days.
How do we check a registrar's transfer experience? Ask for its process at your scale and how it resolves failures.
Should we run a test wave? Yes. A small wave of low-risk domains shows how the registrar handles transfers before critical domains move.
Should critical domains move first? No. Move them last, after the process has been tested.
Can DomainsOptimizer run the transfer? Sometimes Kalin does; more often your team or registrar runs it with his plan.
How long is the review? About one hour, with large lists sent in advance.
Is this about Active Directory or Microsoft 365? No. It is about internet domain names and registrars.