Corporate Domain Management Procurement: Beyond the ICANN Accredited Registrar List

Corporate domain management procurement should go beyond the ICANN accredited registrar list by starting from a reviewed portfolio, writing requirements per tier, checking ccTLD and governance needs, testing registrar claims against real experience and comparing offers on the same scope. The list is a baseline for gTLDs; the decision comes from everything after it. DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, provides procurement guidance for that process.

Procurement teams are used to supplier registers, frameworks and certifications. The ICANN accredited registrar list looks like one of those. It is useful, but it is not a framework of approved corporate suppliers. This article sets out a procurement approach that starts where the list ends.

What procurement needs that the list cannot give

  • A scope. Which domains, by tier, need to be held and where.
  • Requirements. Security, support, coverage, governance and commercial terms.
  • A real shortlist. Registrars that meet critical-tier requirements, not every accredited name.
  • Evidence. Answers to specific questions, checked against experience.
  • A comparable price. Quotes on the same reviewed scope.
  • An audit trail. Why each registrar was chosen for each tier.

Stage 1: review the portfolio

Gather exports from every registrar and account. Look beyond them for domains in agency, subsidiary and personal accounts, using hosting accounts, server IPs and research tools. Tier the domains and remove legacy names from scope.

Stage 2: write requirements

Critical tier: registry lock support by extension, approval workflows, multi-factor access, identity verification, named support and incident response.

Active tier: reliable renewals, DNS, ccTLD coverage, bulk tools.

Defensive tier: cost, blocking or monitoring options.

All tiers: roles, cost-centre billing, audit logs, notifications, exit terms.

Stage 3: check accreditation and coverage

For gTLDs, confirm ICANN accreditation or a disclosed accredited partner. For each ccTLD, check direct support, partners and local presence requirements.

Stage 4: shortlist

Include only registrars that meet the critical-tier requirements on paper. Usually that means a small number of corporate registrars, plus possibly a lower-cost registrar for the active or defensive tier.

Stage 5: issue questions

Send the same written questions to every shortlisted registrar, with the reviewed scope.

Stage 6: evaluate

Score answers against weighted requirements. Test claims against references and first-hand experience. Note gaps by extension.

Stage 7: decide and contract

Choose one registrar or a split by tier. Check exit terms, registry lock pricing, support commitments and transfer assistance before signing.

Stage 8: plan the transfer

DNS first where needed, low-risk domains first, critical domains last, codes per wave and accounts closed after final checks.

Handling ccTLDs in procurement

Country-code domains need their own line in the requirements. For each ccTLD, procurement should know whether the registrar supports it directly or through a partner, whether local presence is needed and how the registrar provides it, whether registry locks are available and how transfers work. Listing ccTLDs in the scope document, with these questions next to each, makes the answers comparable across registrars.

A procurement framework

Stage Output Owner
Review Reviewed scope by tier Project lead, IT
Requirements Weighted requirements IT, security, legal, finance
Accreditation and coverage Eligibility by extension IT, procurement
Shortlist Small list of qualified registrars Procurement
Questions Comparable answers Procurement
Evaluation Scores and gaps Panel with adviser
Contract Signed terms Procurement, legal
Transfer plan Waves and order IT

Why domain procurement needs specialist input

Procurement teams are skilled at running fair processes, but domain registrars are a specialised market. Few procurement professionals know which registrars support registry locks for which extensions, how ccTLD local presence services work or how a registrar handles a large transfer-in. Without that knowledge, it is hard to write precise requirements or spot vague answers. Specialist input closes that gap, so the process is not only fair but also well informed.

It also gives the procurement team confidence when registrars push back, because each requirement has a clear reason tied to the portfolio.

How the framework saves time

The framework may look longer than picking from the accredited list, but it usually saves time. A reviewed scope removes hundreds of domains from every quote and transfer. A short, qualified shortlist cuts the number of responses to read. Specific questions produce answers that can be scored quickly. And a clear transfer plan prevents the delays that come from discovering ccTLD or DNS issues halfway through.

Who should be involved

Procurement leads the process. IT, security, legal and finance own their requirements. An independent adviser helps translate domain needs into requirements and test registrar claims.

Common mistakes

  • Using the accredited list as a shortlist.
  • Writing requirements after meeting registrars.
  • Quoting on the full export.
  • Weighting price above critical-tier security.
  • Skipping exit terms.
  • Leaving ccTLDs to the transfer phase.

Where an expert helps

DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov supports corporate domain management procurement beyond the ICANN accredited registrar list: he reviews the portfolio, writes requirements per tier and tests registrar claims from direct experience with all the major registrars.

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 and has managed over 800,000 with his team. Evaluation sessions after responses arrive are follow-ups at the same rate, USD 2,500 per hour.

To be fair about the limits: DomainsOptimizer does not run procurement platforms or hold domains, and its rate is at the premium end. It adds the domain-specific judgement that procurement teams rarely have in-house.

You don't need to rebuild everything. You need to know what can fail.

What to send

  • Exports from every registrar and account.
  • Procurement policies or templates.
  • Every extension you hold.
  • Critical domains and where DNS is hosted.
  • Current contracts and renewal dates.

A sample scenario

A typical situation: a logistics group's procurement team must justify its registrar choice to auditors. Its previous selection was based on accreditation and price.

The new process reviews 2,400 domains, removes about 850 legacy names, writes weighted requirements and shortlists three registrars. One fails registry lock requirements for four key ccTLDs. The group chooses a corporate registrar for 140 critical and brand domains and a lower-cost registrar for the active tail. The auditors receive a clear trail from scope to decision.

FAQ

Is the ICANN accredited registrar list a supplier framework? No. It confirms authorisation for gTLDs, not suitability for corporate domain management.

What should procurement start with? A reviewed portfolio, tiered, with legacy domains removed.

How many registrars should be shortlisted? Usually only those that meet critical-tier requirements, often two to four.

How should ccTLDs be handled? Checked extension by extension for direct support, partners and local presence.

What evidence do auditors expect? A reviewed scope, written requirements, scored responses and a reasoned decision.

Who should score responses? A small panel from IT, security and procurement, ideally with an independent adviser.

Can the result be two registrars? Yes. A split by tier is common.

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.