.ops
Is .ops a real TLD? Who’s applying to run it?
.ops is contested: 5 applications for it are on ICANN’s Reveal Day list, as of 8 October 2026. They are Open Culture Foundation, GoDaddy Registry, Mux Registry, Starlight (Namecheap) and Identity Digital. XYZ named .ops as a backup string for its .outlet application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. easyDNS named .ops as a backup string for its .geek application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A natural fit for DevOps and tech-operations teams, but most will likely keep it for tools and side projects rather than their main brand.
devops, SRE, security-ops and AI/ML-ops teams and tooling vendors; companies wanting a short operations-flavored address for status pages, internal platforms, or -ops branded products
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .geek application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .outlet application, shown as deactivated: another applicant applied for the same string or named it as a backup
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet exactly: a clipped piece of engineering-insider jargon for a job function, whose buyer is technical practitioners and the tooling vendors selling to them, and which only works if that community treats its own shorthand as a badge worth putting primary identity on.
A generic IT/infrastructure function noun sold as identity to the same infra-and-tooling buyer, but it is the unclipped formal word aimed at firms describing what they build rather than insider shorthand a practitioner community claims for itself.
An operational-function word whose natural use is a company's functional surface (help desk, status, escalation) rather than a brand, so it makes the same bet that an internal business function is worth a top-level label — just aimed at customer service instead of infrastructure.
What a .ops domain is
.ops is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. 5 applications for it are on ICANN’s Reveal Day list.
Is the .ops domain extension real yet?
.ops is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .ops domain?
You can’t yet. A .ops 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 .ops was .dev, delegated on 18 December 2014.
Is .ops a real TLD?
Not yet. .ops is not in the DNS root, so nothing resolves under it. It’s here because .ops is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Starlight (Namecheap) · noteDomain Name Wire
- XYZ · first recordedICANN
- easyDNS · first recordedICANN
- Open Culture Foundation · first recordedICANN
- GoDaddy Registry · first recordedICANN
- Mux Registry · first recordedICANN
- Starlight (Namecheap) · first recordedICANN
- Identity Digital · first recordedICANN
“AM2619T-T66700 · Acid Medal, LLC · primary · contention set 2026-172 MEI2699T-T15549 · Mirfak Exploration, Inc. · primary · contention set 2026-172 MRL2648T-T99642 · Mux Registry L.L.C-FZ · primary · contention set 2026-172 NA2631T-T23964 · Registry Services, LLC · primary · contention set 2026-172 OCF2539-T20706 · Open Culture Foundation · primary · contention set 2026-172”ICANN
“AM2619T-T66700 · Acid Medal, LLC · primary · contention set 2026-172 ETI2627T-T87828 · easyDNS Technologies Inc. · replacement string of .geek · Deactivated MEI2699T-T15549 · Mirfak Exploration, Inc. · primary · contention set 2026-172 MRL2648T-T99642 · Mux Registry L.L.C-FZ · primary · contention set 2026-172 NA2631T-T23964 · Registry Services, LLC · primary · contention set 2026-172 OCF2539-T20706 · Open Culture Foundation · primary · contention set 2026-172 XL2625T-T50991 · XYZ.COM LLC · replacement string of .outlet · Deactivated”ICANN
“For us, moving into the registry side is a natural extension of what we have been building.”Domain Name Wire
- The string rides a live naming convention in tech (DevOps, GitOps, MLOps, SecOps), giving it a large, well-funded best-fit buyer pool, and the applicant is a registry venture of a major registrar (per the verified facts), which plausibly helps distribution. By analogy, though, developer-adjacent TLDs other than a small handful of standouts have tended to see volume registrations without becoming primary identities — ops-flavored strings like .tools, .systems, or .cloud read as secondary/utility namespaces in practice (analogy, not measured here). I place .ops at the top of the 30-49 band: above the band below because the semantic pull and buyer category are real and current, but below 50-69 because there is no demonstrated sustained demand yet and serious tooling companies today mostly brand on incumbent tech TLDs, so adoption still needs explaining. Main market uncertainty: whether devops/AI-ops vendors treat .ops as a primary identity or only as a redirect/utility layer under their existing domains.