What is .food?
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 .food names for sale at any registrar.
ICANN's records put the delegation of .food on November 10, 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 April 21, 2016.
Internet Naming Company LLC also runs 7 other TLDs, including .country, .diy, .hiv, .lifestyle and .living.
Under the hood, the root zone points to 4 name servers for .food, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .food haven't been tampered with on the way. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.registry.click).
Same registry, other endings
7 other TLDs share this operator.
.food FAQ
What country is .food?
None. .food is a generic top-level domain, so it isn't tied to any country.
Who owns the .food domain extension?
Internet Naming Company LLC operates .food as its registry, under a registry agreement with ICANN.
When was .food created?
.food was delegated to the DNS root zone on November 10, 2016.
Is .food a valid domain?
Yes. .food is an active top-level domain in the DNS root zone, delegated in 2016, so .food addresses work in every browser.
Can I buy a .food domain?
No. .food is a brand TLD under ICANN Specification 13, so names are reserved for Internet Naming Company LLC.
Is .food DNSSEC-signed?
Yes, the root zone holds a DS record for .food.
Sources
Data from IANA root zone version 2026102000. Last changed June 16, 2026. Spotted something wrong? Tell us.
