What is .menu?
.menu entered the DNS root zone on November 30, 2013, 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.
On the technical side, .menu 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 .menu, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.menu).
.menu FAQ
What does .menu mean?
.menu is a generic top-level domain named for the word "menu", and it's aimed at food & drink. It doesn't belong to any country.
What is .menu used for?
.menu 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 .menu?
None. .menu is a generic top-level domain, so it isn't tied to any country.
Who owns the .menu domain extension?
Dot Menu Registry, LLC operates .menu as its registry, under a registry agreement with ICANN.
When was .menu created?
.menu was delegated to the DNS root zone on November 30, 2013.
Is .menu a valid domain?
Yes. .menu is an active top-level domain in the DNS root zone, delegated in 2013, so .menu addresses work in every browser.
Can I buy a .menu domain?
.menu names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Dot Menu Registry, LLC's policy if you're unsure.
Is .menu DNSSEC-signed?
Yes, the root zone holds a DS record for .menu.
Sources
Data from IANA root zone version 2026102000. Last changed July 5, 2024. Spotted something wrong? Tell us.
