.ave
Is .ave a real TLD? Who’s applying to run it?
Nobody has applied for .ave in its own right, as of 7 October 2026. XYZ named .ave as the replacement string of its .list application.
A short, catchy address-style ending for avenue-themed names, but few serious projects would make it their main identity.
real-estate and hospitality brands, local businesses on a named avenue, and hobbyist hack-domain buyers (e.g. park.ave) looking for a short, playful address-style name
No applications recorded for this TLD yet.
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 as .ave: an everyday location noun sold open to anyone, where the value is that any business or neighborhood can put a where-am-I identity on the right of the dot rather than a what-do-I-sell one.
Another generic place-word betting that local and neighborhood identity (a street, a district, a main-strip merchant) is worth owning, which is the same demand .ave is reaching for, just at settlement scale instead of street scale.
The nearest 2012 example of the specific move .ave makes — taking a clipped, colloquial short form of a longer everyday word and asking buyers to read the full word into three or four letters — though it points at a property-trade audience rather than an address-as-identity one.
What a .ave domain is
.ave is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Places. Nobody has applied for .ave in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .ave domain extension real yet?
.ave 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 .ave domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .ave name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .ave was .place, delegated on 2 July 2014.
Is .ave a real TLD?
Not yet. .ave is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .ave as part of an application for another string. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string reads as the abbreviation of 'avenue', which gives it an obvious address-style use (fifth.ave, park.ave, real-estate and hospitality branding tied to a street) plus incidental meanings in Spanish (bird) and Latin (hail). Verified facts: a single application on the record from XYZ.COM LLC, recorded as a replacement string for .list, with zero contention and no category tag; registration counts, pricing, and launch timing are unknown. Reasoning by analogy (flagged as analogy): existing street-and-place style TLDs such as .street, .place and .lane have, to my knowledge, seen modest registration volume and thin aftermarket activity, with most use being defensive, novelty, or promotional rather than primary identity; .ave is shorter and more hack-friendly than those, which helps memorability but does not change the demand pattern. It is not in the 30-49 band because there is no evident buyer group that needs this ending at volume, and I expect most registrations to be driven by price promotions and word-play rather than a sustained use case; it is above 1-9 because the avenue meaning is real, the string is short and pronounceable, and some real-estate, hospitality and local-business projects over the next 5 years could plausibly choose it. Main market uncertainty: whether real-estate and location-branded businesses adopt address-style endings at all, or continue to treat them as redirects beside a .com, which would hold .ave at novelty volume.