.radar
Is .radar a real TLD? Who’s applying to run it?
Nobody has applied for .radar in its own right, as of 7 October 2026. Oinkadot named .radar as the backup string of its .wire application.
A memorable suffix for monitoring and trend-spotting tools, but few serious projects would pick it as their main address.
monitoring, alerting and trend-tracking products (tech radars, price and threat watchers, weather and aviation apps) wanting a product-sounding name; secondarily marketing teams running "on the radar" campaigns
Nobody has applied for .radar in its own right.
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 .radar: a short, vivid everyday noun that means keeping an eye on something, sold on connotation to watchdog, tracker and monitoring projects that want it as a verb-like suffix, rather than to any one industry that owns the word.
Also a surveillance-metaphor word bought by people whose product is watching a field and telling others what moved, but it is an agent noun (the one who looks) rather than the instrument that does the looking, so it sells a role instead of a capability.
Same shape of bet - an unowned generic noun naming the output of monitoring, whose buyers are editorial and data publishers attaching it as a suffix to a subject - but it sells the finished document rather than the live detection that gives .radar its pull.
What a .radar domain is
.radar is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our AI & tech category. Nobody has applied for .radar in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .radar domain extension real yet?
.radar 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 .radar domain?
You can’t yet. A .radar name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .radar was .watch, delegated on 23 January 2014.
Is .radar a real TLD?
Not yet. .radar is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .radar as part of an application for another string. Every entry on this page links to its source.
- Oinkadot · first recordedICANN
“OI2692T-T66958 · Oinkadot Inc · replacement string of .wire”ICANN
- Band chosen: 30-49, usable but limited. .radar is a concrete English noun with an idiomatic second meaning ("on the radar"), which gives it more naming utility than most abstract generics: left-of-dot words compose into product-like names (price.radar, threat.radar, trend.radar, weather.radar) that read as a tool rather than a web address. The natural buyers are monitoring, observability, alerting and trend-publishing products, plus some weather, aviation and automotive-detector brands. It is not in the 50-69 band because there is no evidence, known to me, of sustained demand for a monitoring-flavoured namespace: by analogy (flagged as analogy) single-noun generic TLDs from the 2012 round that name an activity or object rather than a category of business — .watch, .report, .review, .zone — settled into volume-and-price registrations with weak brand signal and thin resale, and I expect .radar to behave like those rather than like a category standard such as .news or .app. It is not in the 10-29 band because the word is not a joke or a one-event term: it is a plausible primary identity for a small class of real products, and the idiom gives marketers a reason to register beyond vanity. Within the band I place it low-to-mid: the buyer class is narrow and most would still treat a .radar name as a campaign or product alias beside a .com or .io primary. Applicant facts on the record are neutral: one standard application from Oinkadot Inc, recorded as a replacement string for a primary application for .wire, with no contention recorded; this suggests .radar would launch as a general-purpose commercial namespace rather than a brand or community TLD, which fits the open-market reading above. Main market uncertainty: whether any recognisable monitoring or observability vendor adopts a .radar name as its primary identity in the next 5 years; one such anchor would pull the string toward the top of the band, while none would leave it a low-volume, price-driven TLD with a shallow aftermarket.