.bug
Is .bug a real TLD? Who’s applying to run it?
.bug is not contested. One applicant has said publicly that it applied to run it, and nobody else has, as of 16 August 2026. It is Oinkadot.
A playful name ending for bug trackers, security pages, and pest control; fun for a few, rarely a serious company's main address.
software teams and security researchers wanting a memorable home for bug reports, bug bounty, and disclosure pages, plus pest-control businesses and insect enthusiasts who see the literal word as a fit
One of 25 strings the Oinkadot partnership (Ray King of Porkbun and Todd Han of Dynadot) applied for in the ICANN 2026 round, per Domain Name Wire's exclusive.
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 short everyday-looking English noun that software people have annexed as their own vocabulary, sold to builders of a specific technical artifact who would put their primary identity on the word for the thing they make (or hunt).
Same bet on developer vernacular, where the string's value depends entirely on the engineering in-crowd recognizing it and it means nothing to anyone else, so adoption rides on dev tooling rather than a broad category market.
Both are short common nouns naming a problem or defect rather than a business category, with no incumbent industry that owns the word, so the bet is on connotation pulling in issue-and-complaint uses rather than on a defined buyer pool.
What a .bug domain is
.bug is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One applicant has said publicly that it applied for .bug.
Is the .bug domain extension real yet?
.bug 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 .bug domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .bug name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .bug was .bot, delegated on .
Is .bug a real TLD?
Not yet. .bug is not in the DNS root, so nothing resolves under it. It’s here because an applicant said publicly that it applied for .bug in the ICANN 2026 new gTLD round. Every claim on this page links to its source.
- Oinkadot · first recordedDomain Name Wire (Andrew Allemann)
“A new partnership has applied for 25 top level domain names in this year's ICANN TLD expansion round.”Domain Name Wire (Andrew Allemann)
- Band chosen: 30-49, usable but limited. The string has two coherent buyer stories: a developer/security angle (bug reporting, bug bounty, QA tooling, disclosure pages) and a literal one (pest control, entomology). But in both, .bug reads as a clever secondary address, not a primary identity; the word carries a negative connotation in software (a bug is a defect), which weakens it as a brand signal for the very audience most likely to notice it. It is not in the 50-69 band because there is no evidence of sustained primary-identity demand and adoption would need explaining to nearly every buyer; it is above the 10-29 band because the developer-tooling and pest-control use cases are functional and recurring, not purely event-driven or joke registrations, and the applicant context (both Oinkadot principals run consumer registrars, per the verified facts) plausibly gives it real retail shelf placement, which by analogy tends to help volume for quirky strings. By analogy with other short, witty tech-adjacent TLDs, such strings typically see modest registration volume driven by novelty and price promotion, a thin aftermarket, and occasional standout single uses rather than category-standard status; that analogy, not any measured data, is the basis here, and specific volumes for those analogs are unknown. Main market uncertainty: whether the security/bug-bounty community treats .bug as a recognized convention for disclosure and bounty pages (which would push it toward the top of this band or above) or whether it settles as a novelty/redirect namespace with the negative-connotation problem capping serious use.