Black Friday. Up to 25% extra credits.See packs

.risk

Is .risk a real TLD? Who’s applying to run it?

Nobody has applied for .risk in its own right, as of 18 November 2026. Hyperion named .risk as a backup string for its .audit application. ICANN’s list shows it as deactivated: the application cannot move to it.

Commerce · on the record since Oct 7, 2026, updated Nov 18, 2026
applicants
0 applications · 1 deactivated backup

Nobody has applied for .risk in its own right.

backups
  • HyperionDeactivated backupregister.mu ↗

    The applicant kept its .audit application and did not switch to this replacement (backup) string: shown as deactivated on the ICANN String Confirmation Day list, 17 November 2026

    named as replacement for .audit Oct 7, 2026 · named as a backup for .audit, deactivated by ICANN Nov 17, 2026

    Deactivated backup for .auditGeneric · Applicant supportICANN HL2584-T22214ICANN ↗

Will names sell?

◈AI score
31/ 100
Usable but limited

A narrow professional-vertical name for risk and compliance firms; usable, but the word itself warns rather than reassures.

assessed by claude-fable-5-1 · Oct 7, 2026

Last round the AI scored the 2012 strings blind to their fate. Strings it scored 60 or more hold a median 27,168 names today; those under 30, a median of 30. .risk’s closest 2012 strings hold .safety 2, .insurance 675 and .security 931.

AI score 31 of 100. .com scores 96, .ai scores 84.

For comparison, .com scores 96 and .ai scores 84 on the same rubric.

How the AI’s blind 2012 read held up: its score of each 2012 string against the names it holds today808 2012-round TLDs. Scored 60 or more: median 27168 names. Scored under 30: median 30 names. .risk's closest 2012 strings: .safety scored 30, 2 names; .insurance scored 68, 675 names; .security scored 56, 931 names.101001K10K100K1M020406080100scored 60+: median 27Kunder 30: median 30.safety · 30 · 2.insurance · 68 · 675.security · 56 · 931the AI’s blind 2012 score of each string (its own scale) →names held today (log) →

a 2012-round TLD.risk’s closest 2012 strings: score · names

The 2012 read is a separate, time-locked score on its own scale, so .risk’s score above is not placed on it. Names: the registries’ reports to ICANN, 2026-10. Non-brand 2012 TLDs in the root.

closest 2012 strings
3 of 1,408

The nearest 2012 strings, and how many names each holds today

The closest 2012 string, .safety, held 2 names, June 2026. .insurance held 675; .security held 931. Chosen by AI from every string in the 2012 round, without being told what happened to any of them.

  1. .safetystrong parallel2 names, June 2026live since 2015 · uncontested in 2012 · scored 30* in 2012 · Safety Registry Services, LLC.See .safety in Stats

    Same bet: an abstract professional-discipline noun with no product behind it, sold to consultancies, compliance functions and standards bodies, and leaning on the natural left-of-dot qualifier construction (food.safety / cyber.risk) rather than on any single owner class.

  2. .insurancemoderate675 names, June 2026live since 2015 · 4 applications in 2012 · scored 68* in 2012 · fTLD Registry Services LLCSee .insurance in Stats

    Same kind of wager on the industry that exists to price and transfer risk, with brokers and carriers as the primary-identity buyers, but it is a hard commercial category with established consumer demand and ad budgets, where risk is a soft abstract that no one searches for.

  3. .securitymoderate931 names, June 2026live since 2015 · 3 applications in 2012 · scored 56* in 2012 · Symantec CorporationSee .security in Stats

    Another abstract discipline noun bought by the same enterprise-assurance buyer and used the same qualifier-prefix way, but it had already hardened into a concrete vendor product category that gives it a defined registrant base risk never had.

Names are from the registries’ monthly reports to ICANN. Each name opens the TLD’s stats page: how it grew, who sells it, and the 2026 strings compared with it. * A separate 2012-only read, time-locked to what was public that year, on a different scale from this page’s score.

who it’s for

risk-management, insurance, compliance and GRC software firms, plus cyber-risk and financial-risk consultancies wanting a descriptive hackable name (e.g. cyber.risk)

What a .risk domain is

.risk is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. Nobody has applied for .risk in its own right. It is named on ICANN’s list as part of an application for another string.

Is the .risk domain extension real yet?

.risk is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.

When can you buy a .risk domain?

You can’t yet. A .risk name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .risk was .safety, delegated on 24 December 2015.

Is .risk a real TLD?

Not yet. .risk is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .risk as part of an application for another string. Every entry on this page links to its source.

Considering a name on .risk?Appraise a name on this TLD →

This record is corrected in the open. See the changelog and methodology.