What is .restaurant?
.restaurant entered the DNS root zone on August 8, 2014, 12 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
Binky Moon, LLC operates a large portfolio of 196 TLDs, including .academy, .accountants, .agency, .apartments and .associates.
On the technical side, .restaurant is served by 6 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .restaurant, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP.
Same registry, other endings
195 other TLDs share this operator.
.restaurant FAQ
What does .restaurant mean?
.restaurant is a generic top-level domain named for the word "restaurant", and it's aimed at food & drink. It doesn't belong to any country.
What is .restaurant used for?
.restaurant 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 .restaurant?
None. .restaurant is a generic top-level domain, so it isn't tied to any country.
Who owns the .restaurant domain extension?
Binky Moon, LLC operates .restaurant as its registry, under a registry agreement with ICANN.
When was .restaurant created?
.restaurant was delegated to the DNS root zone on August 8, 2014.
Is .restaurant a valid domain?
Yes. .restaurant is an active top-level domain in the DNS root zone, delegated in 2014, so .restaurant addresses work in every browser.
Can I buy a .restaurant domain?
.restaurant names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Binky Moon, LLC's policy if you're unsure.
Is .restaurant DNSSEC-signed?
Yes, the root zone holds a DS record for .restaurant.
Sources
Data from IANA root zone version 2026102000. Last changed October 7, 2025. Spotted something wrong? Tell us.
