Is .eat right for your food brand? Three decisions before launch

If a customer can smell the kitchen before they finish reading your homepage, the domain should already sound like food. .eat is a new generic top level domain for restaurants, delivery brands, grocery labels, recipe publishers, beverage makers, and hospitality teams that sell a meal or a food experience.

Short .com names in food were claimed long ago. A clear brand on .eat can sit on a napkin, a delivery bag sticker, or a radio spot without a spelling lecture. The ending will not fix slow kitchens or cold fries. It will tell the visitor what category they entered before the first scroll.

Google Registry opened Sunrise for .eat on 1 September 2026. It ends 9 November, Early Access runs 10 to 16 November, and General Availability begins 17 November at 16:00 UTC. Selected names may also be allocated through an invitation-only Qualified Launch Period. SoxDomains currently lists registration and renewal by quote rather than publishing an unverified price.

Decision one: does the complete name sound like your business?

Independent kitchens, multi city groups, ghost kitchens, meal kits, private label groceries, wine clubs, food media, catering halls, and reservation tools all benefit when the URL itself advertises the plate. The visitor should not need a subtitle to understand the category.

Holding companies with a mature .com can still park a seasonal campaign, a delivery only brand, or a recipe library on .eat. Keep corporate news on the established domain. Put the food specific journey on the ending that matches the hunger intent.

Five kitchen ready jobs for a .eat URL

• Order in one tap. Host the live menu and checkout on a string guests can type from outdoor signage.
• Split delivery identity. Keep the dining room brand intact while the bag brand lives on .eat.
• Teach the recipe. Publish videos, newsletters, and allergen notes under a food native ending.
• Name the cuisine. Combine a neighborhood or cuisine word with .eat when the matching .com is gone.
• Standardize franchise pages. Give operators in many cities the same extension pattern for local landings.

How to name a food domain people can order from

Read the full address like a server repeating an order back. Drop spellings that need a footnote on packaging. Prefer the one or two words guests already use for the restaurant or product line. Type it on a phone with greasy thumbs in mind: autocorrect will punish clever misspellings.

Skip turning every seasonal dish into a domain. Choose the brand people will search next year. If you sell across languages, check that the second level does not create an awkward or offensive meaning in any market you serve.

Defend the brand, not the entire menu

Buy the primary .eat brand, the misspelling guests already make, and any catering or delivery sub brand that takes real payments. Leave unused dish names alone. Empty defensive stacks steal budget from kitchen labor and paid ads that actually fill seats.

Decision two: is paying earlier commercially justified?

Sunrise is not a marketing slogan. It requires a Trademark Clearinghouse record that matches the second level you want. Without that record, prepare for Early Access or wait for open registration instead of inventing a trademark story.

Early Access adds a one-time fee that decreases as the week moves toward General Availability. Paying earlier can make sense for an exact name tied to an approved launch, but it does not guarantee success. A longer, clear alternative may be a better use of budget than urgency built around an untested label.

Open the SoxDomains .eat page, send the shortlist of menu ready names, and request a quote for the phase that matches your trademark status. Request .eat quote

Decision three: can customers order securely on launch day?

.eat is a secure namespace and browsers require HTTPS. Prepare the certificate before changing menus, packaging or QR codes. Then test ordering, reservations, password recovery, transactional email and the redirect from the old address on a phone outside the company network.

Launch fees are the tasting menu. Renewals are the rent. Ask for registration cost by phase, expected renewal, transfer rules, and privacy options. Put the yearly total beside POS software, delivery commissions, and photography so finance sees the domain as another line of restaurant operations.

Register under an organization account owned by the company, not the chef’s personal Gmail. Turn on strong sign in protection, store recovery contacts, and write down who can change nameservers after a partner dispute. A delicious domain that nobody can renew still closes the restaurant online.

Go live only when ordering still works

Do not reprint takeout bags or change QR codes until the domain sits in your account and the menu loads. Set the redirect or site, configure SPF, DKIM, and DMARC for reservation mail, and test “forgot password” on the ordering account. Announce after those checks pass.

What finance and restaurant operations actually need

Finance wants a number and a date. Give both: the quote for the chosen phase, the expected renewal, and the go live date tied to a menu or campaign. Explain that Sunrise and Early Access are scarce windows, not endless promotions. Kitchen managers want to know whether guests will type a new URL on the bag. Show them the shortlist, the radio test result, and the redirect plan from any old ordering link.

Keep one shared note with the winning string, rejected options, TMCH status if any, quote reference, intended launch date, and the person who owns renewals. That page stops the next seasonal campaign from reopening a closed naming debate and speeds recovery if ownership changes after a partnership split.