What is .cooking?
ICANN's records put the delegation of .cooking on March 31, 2014. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on November 21, 2013.
Registry Services, LLC operates a large portfolio of 36 TLDs, including .abogado, .beer, .biz, .blackfriday and .boston.
Under the hood, the root zone points to 6 name servers for .cooking, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .cooking haven't been tampered with on the way. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.cooking).
Same registry, other endings
35 other TLDs share this operator.
.cooking FAQ
What does .cooking mean?
.cooking is a generic top-level domain named for the word "cooking", and it's aimed at food & drink. It doesn't belong to any country.
What is .cooking used for?
.cooking is mostly used for food & drink. Like most gTLDs, it's a label of intent rather than a guarantee — check the site, not just the ending.
What country is .cooking?
None. .cooking is a generic top-level domain, so it isn't tied to any country.
Who owns the .cooking domain extension?
Registry Services, LLC operates .cooking as its registry, under a registry agreement with ICANN.
When was .cooking created?
.cooking was delegated to the DNS root zone on March 31, 2014.
Is .cooking a valid domain?
Yes. .cooking is an active top-level domain in the DNS root zone, delegated in 2014, so .cooking addresses work in every browser.
Can I buy a .cooking domain?
.cooking names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Registry Services, LLC's policy if you're unsure.
Is .cooking DNSSEC-signed?
Yes, the root zone holds a DS record for .cooking.
Sources
Data from IANA root zone version 2026102000. Last changed October 14, 2026. Spotted something wrong? Tell us.
