.account
Is .account a real TLD? Who’s applying to run it?
.account is not contested. One application for it is on ICANN’s Reveal Day list, as of 8 October 2026. It is Intercap. Intercap named .account as the replacement string of its .consult application.
A broad, vague word: handy for accountants and "my account" portals, but phishing worries keep serious brands from building on it.
accounting and bookkeeping firms, fintech and SaaS teams wanting account-portal style addresses, and speculators holding short generic words
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: a single abstract generic finance noun that names the thing a customer holds rather than any company, pitched at the same pool of banks and fintechs, and it only works if regulated finance brands move primary identity off .com into a trust-coded utility word.
Also a bare generic finance noun sold to the same institutional registrant pool, but it leans toward one product line a lender offers rather than the universal customer-record object, so the registrant set is narrower.
Same shape of bet - a short, abstract, function-level word that a financial or platform operator would use as a namespace for customer-facing endpoints - but it names an action users perform, not the record they own, so it reads as a transaction rail rather than an identity.
What a .account domain is
.account is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. One application for it is on ICANN’s Reveal Day list.
Is the .account domain extension real yet?
.account 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 .account domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .account name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .account was .money, delegated on 26 November 2014.
Is .account a real TLD?
Not yet. .account is not in the DNS root, so nothing resolves under it. It’s here because .account is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
“IRI2679T-T34407 · Intercap Registry Inc. · primary IRI2679T-T60293 · Intercap Registry Inc. · replacement string of .consult”ICANN
“IRI2679T-T34407 · Intercap Registry Inc. · primary IRI2679T-T60293 · Intercap Registry Inc. · replacement string of .consult”ICANN
- Band chosen: 30-49, usable but limited. The string has real dictionary utility in two directions, accounting services and user-account or login portals, so registrations at volume are plausible on price, and a few accounting firms or fintechs could plausibly adopt an address on it as a primary identity. It is not in the 50-69 band because neither meaning has a community that would choose .account without explanation: accountants already have profession-specific TLDs from the 2012 round (analogy: .accountant and .accountants, which by reputation drew price-driven and low-engagement registrations rather than becoming a professional default), and the portal meaning is one most companies would route under their existing brand domain rather than a new TLD. It is not in the 10-29 band because the word is not a joke or an event; it describes a durable, everyday function and carries a plain-language meaning in many markets. A specific headwind is that any login-flavoured string invites phishing lookalikes, which tends to make security-conscious brands avoid rather than adopt it (inference from the general behaviour of brands around login-themed names, flagged as analogy). On the record there is one confirmed applicant, Intercap Registry Inc., with no contention, which modestly raises the chance of a straightforward commercial launch but says nothing about demand. Main market uncertainty: whether a registry can position .account as a trusted account-portal namespace (for example by verification or brand-restricted policies) rather than a cheap generic, which would move it toward the top of the band.