.sabre
Is .sabre a real TLD? Who’s applying to run it?
.sabre is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Sabre GLBL Inc..
A company-owned brand domain: useful to Sabre for its own sites, but nobody else can register or resell addresses on it.
the applicant itself and its internal product, partner and customer-facing properties; there is no third-party buyer group
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: an enterprise B2B technology vendor putting its whole corporate identity on a short, evocative English common noun that says nothing about what the company sells, so the string only works if the company's own name is already the thing customers recognize.
Also a non-consumer firm claiming a borrowed common noun with no descriptive link to its business, where the value is a closed namespace for partners and institutional counterparties rather than any public demand for the word itself.
Same shape of bet — a services company whose name is an ordinary word, meaning the application has to defend an attractive generic string purely on the strength of the corporate mark, not on the string's meaning.
What a .sabre domain is
.sabre is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .sabre domain extension real yet?
.sabre 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 .sabre domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .sabre name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .sabre was .oracle, delegated on 3 March 2015.
Is .sabre a real TLD?
Not yet. .sabre is not in the DNS root, so nothing resolves under it. It’s here because .sabre is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Sabre GLBL Inc. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The record shows a single confirmed application by Sabre GLBL Inc., filed under the ICANN brand application type, which means the namespace is expected to be closed to the public: the only registrant is the operator, so there is no aftermarket and no third-party primary-identity use. It is not in the 30-49 band because registrations at volume or on price cannot happen on a closed brand string, and the string carries no demand independent of the company. It is not in the 1-9 band because a dot-brand has genuine, if narrow, end-use utility: by analogy, dot-brands from the prior round run by large technology and automotive companies have been used as real primary identities for product sites, customer portals and redirect schemes, and a travel-technology platform with many partner and agency touchpoints plausibly benefits from a trusted, operator-controlled namespace for APIs, portals and anti-phishing. Also by analogy, a large share of earlier dot-brands saw little or no live use and some were later retired, so the realistic outcome within 5 years is modest internal deployment. The word sabre also has generic meanings (the sword, sports team names, the fencing discipline), but under a brand application those meanings do not translate into a market. Main market uncertainty: whether the operator actually migrates customer-facing or partner-facing properties onto the string rather than holding it defensively, which is the difference between the top and bottom of this band.