DOMAIN EXTENSION GUIDE

.bug Domain Names

No public delegation yet

The .bug extension is a concise, highly memorable string suited to technical, product and troubleshooting uses. It has been publicly associated with the 2026 new gTLD round, but it is not present in the IANA root zone database, so it is not yet delegated for public registration. Publicly announced information identifies Oinkadot as the applicant associated with .bug.

.bug registrations are not available yet. Search related extensions or get a launch alert.

Get launch alerts

Application and status facts

Verified status information is kept separate from illustrative naming ideas.

Extension
.bug
Current status
No public delegation yetNew gTLD Program: 2026 Round application window - ICANN
Root-zone delegation status
No root-zone delegation confirmed in recorded public sources.Root Zone Database - IANA
Announced applicant or applicants
Oinkadotrapidwombat.com - rapidwombat.com
Number of publicly announced claims
1
Contested
No
Public disclosure date
2026-08-15rapidwombat.com - rapidwombat.com
Application round/programme
ICANN application programme information recorded.New gTLD Program: 2026 Round application window - ICANN
Registry operator
Not verified
Registration availability
Public registration is not confirmed by this guide.Root Zone Database - IANA
Last fact checked
2026-08-25

A public application, applicant identity, approval, registry operation, root-zone delegation and live registration availability are separate facts.

Illustrative uses

What could a .bug domain be used for?

If delegated, .bug would suit clear, specialist branding around defects, debugging and incident response.

Bug tracking portalsUse for issue dashboards, defect triage and status pages.
Developer toolsIdeal for products that help engineers find, reproduce or fix problems.
Cybersecurity reportingUseful for responsible disclosure, vulnerability intake and security notices.
Quality assuranceFits testing labs, release checks and product validation teams.
Incident updatesA strong fit for service advisories and outage communications.
Debugging resourcesGreat for tutorials, scripts, utilities and support material.
Product supportWorks well for help centres focused on known issues and fixes.
Technical communitiesSuitable for forums, meet-ups and open-source collaboration.

Domain name ideas

Example names only. Illustrative examples only. Availability has not been checked.

tracker.bugstatus.bugfix.bugdebug.bugreport.buglabs.bug

Possible audiences

Who is .bug for?

  • Software companies
  • Security teams
  • QA professionals
  • Open-source projects
  • DevTool founders
  • IT support teams

Benefits and considerations

Benefits

  • Highly relevant meaning
  • Memorable branding
  • Clear positioning

Considerations

  • Not yet delegated
  • Niche fit
  • Potential confusion

Related domain extensions

Relevant DomainUI marketplace listings

No closely matched public DomainUI marketplace listings are available for this guide right now.

Browse domains for sale

Frequently asked questions

Is .bug available to register now?

No. It is not currently shown in the IANA root zone database, so it is not publicly delegated for registration.

What is .bug best for?

It is best for debugging, defect tracking, QA, support and security-related projects.

Who is publicly associated with .bug?

Publicly announced information identifies Oinkadot as the applicant associated with .bug.

Would .bug suit a consumer brand?

Possibly, but it is strongest where the meaning of bug is relevant and useful.

Is .bug a good choice for security teams?

Yes, especially for vulnerability reporting, disclosures and remediation pages.

How does .bug compare with .dev or .tech?

It is more specific and playful, while .dev and .tech are broader technology choices.

Sources and review information