Subdomain requests

Request a name for a project you already host.

Host your project first, then ask for a name. If the request is approved, we add the DNS record your host asks for — usually one CNAME — to the and.guide zone on Cloudflare. Hosting and HTTPS stay on your platform. How requests work

Manual request

Request a subdomain

Approved names get one DNS record in the and.guide zone that points at your host. An availability check is not an approval.

Request standards

It is DNS only: we add a record that points the name at your host. We do not host sites, forward email, or issue certificates.
Reserved infrastructure names are blocked, and names that impersonate brands, people, or internal services are rejected.
Spam, parked pages, and misleading landing pages are not approved.
Records that stop pointing at a working project may be removed, so the name cannot be claimed by someone else.
Requests are reviewed manually. There is no promise of approval or of a response time.

How it works

Step 1

Host the project yourself

Deploy it on the platform you already use — Cloudflare Pages, Vercel, Netlify, GitHub Pages, or your own server — and note the DNS record it asks for, usually a CNAME target.

Step 2

Send the name and the record

Tell us the subdomain you want, the record type and value your host gave you, and what the site is for.

Step 3

We add one DNS record

After a manual review we add that record to the and.guide zone on Cloudflare. You then finish the custom-domain and HTTPS steps on your platform.

Direct fallback

If the live endpoint is unavailable, email admin@and.guide with the subdomain, the DNS record your host asks for, and a short project description.