Step 1
Check the name
We validate the hostname format and flag obviously reserved names before you prepare a request.
Product overview
A manual system for thoughtful names.
The request flow is intentionally narrow. It is for legitimate projects that need a clear public hostname on the root domain, not for bulk signup theater, disposable pages, or automatic provisioning claims.
Step 2
Describe the use
Tell us what should live there, who it is for, and why that hostname deserves a place on the root domain.
Step 3
Manual review
Requests are reviewed manually. Clear, legitimate projects get priority. Approval is limited and never guaranteed.
What fits well
- Documentation hubs, handbooks, notes collections, and public references.
- Small products, sandboxes, launch previews, and carefully named experiments.
- Personal projects or editorial surfaces that can explain their purpose clearly.
What gets rejected
- Reserved infrastructure names are blocked.
- Names that impersonate brands, people, or internal services are rejected.
- Low-effort spam, parked pages, or misleading landing pages are not approved.
- Manual review matters more than speed. Instant approval and fake SLA language are not part of the product promise.
The promise is clarity, not instant provisioning.
and.guide does not promise automatic setup, managed hosting, fake response-time tiers, or guaranteed approval. The real promise is smaller: clear naming rules, an understandable request path, and enough documentation to make better decisions before you ask.
Open the request form