What is .fire?
Brand TLDs operate under Specification 13 of ICANN's registry agreement. It lets a trademark owner keep every second-level name for itself, so you won't find .fire names for sale at any registrar.
ICANN's records put the delegation of .fire on June 7, 2016. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on June 25, 2015.
Amazon Registry Services, Inc. operates a large portfolio of 51 TLDs, including .amazon, .audible, .author, .book and .bot.
Under the hood, the root zone points to 8 name servers for .fire, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .fire haven't been tampered with on the way. Registration data is published over RDAP.
Same registry, other endings
50 other TLDs share this operator.
.fire FAQ
What country is .fire?
None. .fire is a generic top-level domain, so it isn't tied to any country.
Who owns the .fire domain extension?
Amazon Registry Services, Inc. operates .fire as its registry, under a registry agreement with ICANN.
When was .fire created?
.fire was delegated to the DNS root zone on June 7, 2016.
Is .fire a valid domain?
Yes. .fire is an active top-level domain in the DNS root zone, delegated in 2016, so .fire addresses work in every browser.
Can I buy a .fire domain?
No. .fire is a brand TLD under ICANN Specification 13, so names are reserved for Amazon Registry Services, Inc.
Is .fire DNSSEC-signed?
Yes, the root zone holds a DS record for .fire.
Sources
Data from IANA root zone version 2026102000. Last changed February 14, 2025. Spotted something wrong? Tell us.
