.flagscape
Is .flagscape a real TLD? Who’s applying to run it?
.flagscape is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Bank of America.
A coined, brand-style string with no dictionary meaning; useful only to the organization behind it, with no open market expected.
the applicant organization itself, for internal or customer-facing addresses under a name it already uses; not a namespace the public is expected to register in
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 coined two-word corporate brand asset that is not the company's own name and means nothing to the public, applied for by a single corporation purely to fence in an internal piece of its brand system, with no second buyer and no need for anyone outside the company to recognize the string.
Same bet in structure — an invented compound word with no dictionary existence, owned end-to-end by one corporation as the name of an internal initiative rather than its public identity — though it was pointed at an audience outside the company's walls in a way a portal name is not.
Same bet of a single corporation claiming a coined in-house program label that carries no standalone meaning and that no other applicant would ever want, differing only in that its name was built to be seen by the company's customers rather than by its own staff.
What a .flagscape domain is
.flagscape 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 .flagscape domain extension real yet?
.flagscape 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 .flagscape domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .flagscape name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .flagscape was .redumbrella, delegated on 11 December 2015.
Is .flagscape a real TLD?
Not yet. .flagscape is not in the DNS root, so nothing resolves under it. It’s here because .flagscape is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Bank of America · first recordedICANN
- Band chosen: 1-9 (no realistic market). The string 'flagscape' is a coined compound with no generic dictionary meaning and no recognizable category (the record carries no category tag), which is the typical profile of a single-registrant brand TLD rather than an open namespace. The record shows one applicant (ML 35 LLC, status confirmed) and no contention, consistent with a string nobody else sees commercial value in. By analogy (flagged as analogy), coined brand strings delegated in the earlier round have functioned as closed corporate namespaces: zero third-party registrations, no aftermarket, and value limited to whatever internal routing or marketing use the brand itself makes of them. It is not in the 10-29 band because that band assumes at least shallow public or event-driven demand, and nothing about this string suggests the public would seek addresses under it; it cannot be below 1-9 by definition. The score sits near the top of the band rather than the floor because a brand operator can still get real end-use utility from a dedicated namespace it controls. Main market uncertainty: whether the operator intends any outward-facing use at all (customer logins, campaign addresses) versus purely internal infrastructure; the former would give the TLD some visible footprint even without an open market, the latter leaves it effectively invisible.