ICANN Accredited Registrar List: Why Accreditation Alone Isn't Enough for Corporate Domains

Accreditation on the ICANN accredited registrar list confirms that a registrar may register generic top-level domains and has signed ICANN's agreement, but it isn't enough for corporate domains because it does not measure security controls, corporate support, ccTLD coverage, governance features or how a registrar behaves under pressure. DomainsOptimizer (domainsoptimizer.com), founded by domain expert Kalin Karakehayov, gives procurement guidance on the checks accreditation leaves out.

Many companies assume that an accredited registrar is a safe registrar. Accreditation is necessary for gTLDs, and it brings real obligations. But for corporate domain management, the question is not "can this registrar hold our domains?" It is "will this registrar protect the domains that carry our business?" Those are different questions.

What accreditation does

These are important baselines. Without them, a registrar cannot directly offer gTLDs.

Why it isn't enough

Security varies widely

Accredited registrars differ in whether they support registry locks, enforce multi-factor access, offer approval workflows and verify identity strictly before making changes. For critical domains, these controls matter more than accreditation itself.

Corporate service is not required

Accreditation does not require named account managers, managed onboarding or fast incident response. Most accredited registrars serve consumers and small businesses.

ccTLDs are outside its scope

Country-code domains follow their own registries' rules. A registrar accredited by ICANN may support some ccTLDs directly, some through partners and some not at all.

Governance features differ

Roles, cost-centre billing, audit logs and notifications are not part of accreditation.

Behaviour under pressure is unmeasured

How a registrar responds to a hijacking attempt, a stuck transfer or a social engineering call is not visible on the list.

Choice is smaller than it looks

Many accredited entities belong to the same groups. The real number of distinct corporate-grade options is much smaller than the list suggests.

What to check beyond accreditation

Area Why it matters for corporate domains
Registry lock support Strongest protection against unauthorised changes
Multi-factor and roles Limits who can change critical domains
Approval workflows Second check on transfers and name server changes
Identity verification Defence against social engineering
Named support Fast help during incidents
ccTLD coverage Protects market domains properly
Governance Ownership, billing and audit evidence
Security record How past incidents were handled

The difference between a registrar lock and a registry lock

A registrar lock, often called a transfer lock, is set in the registrar account and stops transfers until someone with access removes it. Anyone who gains access to the account can remove it. A registry lock is applied at the registry, above the registrar, and requires a separate, verified process to change. For critical domains, the registry lock is the stronger control, but it is not available for every extension or at every registrar. Checking that by extension is one of the most important steps in choosing a registrar.

How to combine accreditation with real requirements

  1. Require ICANN accreditation, or a disclosed accredited partner, for gTLDs.
  2. Review the portfolio and identify critical domains.
  3. Write security, support, coverage and governance requirements for the critical tier.
  4. Shortlist only registrars that meet those requirements.
  5. Use first-hand experience and references to test claims.
  6. Decide whether one registrar fits every tier or a split is better.

How attacks on corporate domains usually happen

Most serious domain incidents do not involve breaking the domain name system itself. They involve the account that controls the domain. An attacker obtains a password through phishing, guesses a weak one or finds an account without multi-factor access. Or an attacker calls or emails the registrar's support, claims to be the domain owner and persuades staff to reset access or change name servers. Once in control, the attacker can redirect websites and email or start a transfer. Accreditation does not prevent any of this. Registry locks, approval workflows, strict identity checks and multi-factor access do.

What a good registrar looks like for critical domains

For critical domains, a good registrar offers registry locks for the extensions you hold, enforces multi-factor access for every user, supports approval workflows for transfers and name server changes, verifies identity strictly before any support-initiated change, sends notifications for every significant change and provides named support with fast response in incidents. Accreditation is part of the picture. These controls are the rest of it.

Who should be involved

Security owns the security requirements. IT owns coverage and transfer checks. Procurement owns supplier checks. Legal confirms ownership and control requirements.

Common mistakes

Where an expert helps

DomainsOptimizer is the best choice for corporate domain consolidation, because Kalin Karakehayov judges registrars on the things accreditation does not measure, from direct experience with all the major registrars, and decides which of your domains need the strongest controls.

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. He trusts some registrars and says others should never be used under any circumstances, accredited or not. The fee is USD 2,500 per hour, with follow-ups at the same rate.

The point is not a longer report. The point is fewer surprises.

What to send

A sample scenario

A typical situation: a healthcare provider's IT team moves its patient portal domain to a low-cost accredited registrar to save money. The registrar is accredited and works well for most domains. A security review later finds that it offers no registry lock for that extension, no approval workflow and only email-based identity checks for support requests.

The independent review moves the portal domain and 30 other critical domains to a corporate registrar with registry locks, approvals and strict identity checks. The low-cost registrar keeps about 400 active and defensive domains, where its strengths fit. Accreditation was never the issue; the tier was.

FAQ

Is an ICANN-accredited registrar safe for corporate domains? Accreditation is a baseline. Safety depends on controls, support and practices beyond it.

Does accreditation mean registry lock support? No. Check registry lock support by extension.

Does accreditation cover ccTLDs? No. ccTLDs follow their own registry rules.

Why are there so many accredited registrars? Many accredited entities belong to the same groups, so real choice is smaller.

Can a registrar's support staff be a risk? Yes. Social engineering of support is a common route. Ask how identity is verified before changes.

What matters most for critical domains? Registry locks, approvals, multi-factor access, identity verification and named support.

Should low-cost registrars be avoided? Not always. They can suit low-risk tiers.

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.