.hey: A Name for the First Question
You join a community you've been meaning to try.
There are channels, pinned messages, and a calendar of events. You have one question: can someone new come along on Saturday?
If you're building an assistant for that first conversation, .hey is a name to consider. It's a Handshake extension for personal identities, communities, products, services, and communication-focused projects, open for registration on HeadlessDomains.com.
Make the first question easy to ask
Suppose a community assistant helps new members find the right event and understand how to join. A useful introduction tells someone what they can ask, where the answers come from, and how to reach a person when the assistant doesn't know.
Your .hey name can identify that first point of contact. Link it to the service you maintain and explain its scope before someone starts a conversation.
A new member shouldn't have to understand your whole community to ask whether an event is open to beginners. Choose a name and description that make that small request feel welcome.
Let the answer earn the friendly name
For the Saturday question, the assistant might point to the current event details and explain whether a reservation is needed. If the listing doesn't say who can attend, it should send the question to an appropriate contact rather than inventing an answer.
That behaviour belongs in your service. The .hey ending doesn't make an agent friendly or give it access to a community's private conversations.
Start with the information people are allowed to see. Keep member records behind their existing access controls and explain what someone should avoid sharing in a public conversation.
If the answer needs a person, show the newcomer where to ask. Check that someone is there to receive the question.
Choose a name that fits the conversation
The .hey page uses hello.hey, team.hey, and welcome.hey to show the format. These are illustrative names, not names confirmed available to register.
For your project, consider how someone would mention it to a friend. Would they know where to ask their first question? Would the description tell them whether they are contacting a person, a community assistant, or a product's support service?
.hey also suits a personal public identity. If the service belongs to you, make the person behind it clear and publish the official links people should use to contact you.
Connect it to the place people can ask
After registering, connect the public identity to your actual service, with an accurate description and operator information. The after-registration guide covers the practical setup.
HeadlessDomains.com and SkyInclude maintain API and command-line infrastructure that lets compatible agents inspect headless names and find connected services without browser-native resolution. .hey belongs to the Handshake naming system, separate from ICANN extensions.
The name doesn't host a conversation or run the assistant. You choose and maintain the tools behind it.
Before you register
The .hey page lists these prices, checked October 8, 2026:
- Human registration: $9.95 USD per year.
- Agent registration through MPP: 8.95 pathUSD per year.
- Renewal: $9.95 USD.
Check the exact name, current quote, payment amount, and renewal terms at checkout. .hey uses partner-backed registration, with the final availability and price confirmed through the provider.
They wanted to know whether they could come on Saturday. An answer and a place to ask again may be enough.