.chevron
Is .chevron a real TLD? Who’s applying to run it?
.chevron is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Chevron.
A corporate-name namespace: useful only to the applicant itself, with no public registrations or resale market expected.
the applicant company and its affiliates, for owned product, regional, and campaign addresses; no third-party buyer group is likely
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: an integrated oil-and-gas major putting its own corporate name on a dot-brand, a word nobody else could credibly claim, whose value depends entirely on the parent company moving its identity there.
Nearest match on both word-type and buyer: a global petroleum major's own name that is also an ordinary English noun, betting that corporate ownership of a dictionary word reads as the brand rather than as a category.
Same single-corporation energy dot-brand bet on a proper name with no generic demand behind it, but from a narrower single-market producer rather than a globally recognised consumer-facing major.
What a .chevron domain is
.chevron 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 .chevron domain extension real yet?
.chevron 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 .chevron domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .chevron name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .chevron was .statoil, delegated on 19 June 2015.
Is .chevron a real TLD?
Not yet. .chevron is not in the DNS root, so nothing resolves under it. It’s here because .chevron is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Chevron · first recordedICANN
“CDNL2697T-T67462 · Chevron Domain Name LLC · primary”ICANN
- Band chosen: 10-29 (vanity/joke/narrow), at the upper edge. The record shows a single confirmed application from Chevron Domain Name LLC, whose name matches the string; by analogy with earlier-round applications where the applicant entity name matched the string, this pattern is typical of a company applying for its own name as a namespace it controls, and I reason from that analogy. Such namespaces (analogy: earlier-round company-name TLDs) have generally seen no open registration and no aftermarket, because only the operator and its affiliates can hold names; a subset put the TLD into visible use for redirects, regional sites, or campaigns, while many stayed dormant and some were later retired. That is why it is not in the 30-49 band: there is no volume registration, no price-driven demand, and no aftermarket at all, so the 'usable but limited' criteria of registrations at volume do not apply. It is not in the 1-9 band because the string does have a real, if closed, end-use: a company-controlled namespace can carry primary-identity value for its owner (trust signal, phishing resistance, consistent branding across markets), which an address under it would deliver if the owner chose to lead with it. The word also has a generic meaning (a V-shaped stripe or insignia) that could in theory interest other parties, but with the applicant pattern on the record that generic demand is unlikely to be served. Main market uncertainty: whether the operator will actually migrate customer-facing properties onto the TLD as a primary identity or treat it defensively as a redirect, which by analogy separates the handful of actively used company-name TLDs from the dormant majority.