Host-header routing · Invisible rewrite
Point a CNAME. Your page is live on your domain.
cnamely resolves the Host header on every page request and rewrites the root of a mapped domain to a hosted page, article, or full site — invisibly. No redirects, no iframes, no URL flicker. Works behind Cloudflare. Onboarding is handled by our operators.
$ curl -s https://yourbrand.com/.well-known/cnamely-verify
{"service":"cnamely","host":"yourbrand.com"}
$ open https://yourbrand.com/
→ 200 OK served: hosted page address bar: unchanged
- HOST-HEADER ROUTING AT THE FRONT OF EVERY PAGE REQUEST
- 30s RESOLVER CACHE — FAILS CLOSED
- ADMIN & AUTH: 404 ON CUSTOMER HOSTS
Mechanism
The URL never changes. Here's why.
Every page request passes through routing middleware that classifies the Host header. Platform hosts get the platform. A mapped customer host gets its target — rewritten internally, not redirected. The browser address bar shows the customer's domain the whole time.
- Browseryourbrand.comGET /
- DNS / CloudflareCNAME → cnamely · SSL: Flexible or Full
- Routing middlewareclassify Host → resolve mapping (30s cache)
- Hosted contentyourbrand.cominternal rewrite → /p/{slug} · URL unchanged
rewrite, not redirect
Root requests are internal rewrites inside the platform. Visitors never see our URL — only yours.
fail-closed resolver
Unknown or inactive domains get a 404. Resolver errors return 503 with Retry-After — never wrong content on the wrong host.
end-to-end verification
/.well-known/cnamely-verify answers on every host, so we confirm traffic reaches the platform through your real DNS and proxy chain before go-live. The result is recorded on the domain.
Targets
One domain, three kinds of targets.
Each mapped domain points at exactly one target. The root serves it; everything else stays locked down.
Hosted landing page.
A versioned HTML page from our studio, served at your root. Assets rewritten, conversion clicks tracked.
Source page.
Lead-driven public pages backed by a hosted page — with optional timed auto-redirect.
Full passthrough.
The whole platform served on your hostname, when that's what the deal calls for.
For page and source targets, only the mapped content serves on your domain — by design.
Infrastructure
Built like infrastructure, because it is.
Admin surface: 404
/admin and /api/auth are hard-blocked on customer hosts. Custom domains expose only a small public API allowlist — files, OG images, public content, visit tracking.
Bounded staleness
Domain mappings cache for 30 seconds per replica, negative results included. Changes converge across the fleet within the TTL; the editing replica updates immediately.
Cloudflare-friendly
Designed to run behind Cloudflare proxying (SSL mode Flexible or Full). Verification rides the real request chain, so it proves the path your visitors actually take.
Per-domain ingress
Every hostname gets its own deterministic ingress. Apex and www are provisioned independently — explicit, auditable, no catch-alls.
Recorded verification
Each domain stores when it was verified, when it was last checked, and the exact error if a probe fails. DNS lookups are SSRF-guarded; private IPs refused.
Your name on the share card
Source pages derive canonical URLs, Open Graph, and Twitter cards from the serving hostname — your domain gets its own social cards, not ours.
Studio
The pages behind the domains.
Authoring
Pages are built in an operator studio: AI chat generation that writes real, deployable code, a multi-file code editor with live desktop and mobile preview, drafts auto-saved every keystroke pause, and immutable published versions with one-click rollback.
Analytics
First-party visit and conversion tracking, attributed per serving domain. Every view records device, browser, geo, and referrer; clicks to your target URL beacon as conversion events. No third-party scripts.
- versioned publishing
- rollback to any version
- per-host attribution
- visit → jump funnel
Onboarding
Onboarding is managed. Deliberately.
One DNS record on your side. Everything else on ours. There's no self-serve wizard to fight — our operators provision each domain end to end.
We map it
An operator creates your domain mapping: hostname, target type, content.
You point DNS
Add the record at your provider — typically Cloudflare, proxied, SSL set to Flexible or Full. Apex and www are configured separately.
We verify, then it serves
We probe your domain end to end through your real DNS and proxy chain, record the result, and from then on serving is fully automatic.
The fine print, up front.
- Onboarding is operator-managed — you request, we provision. There's no customer dashboard.
- HTTPS on your domain comes from your CDN layer: front it with Cloudflare in Flexible or Full SSL mode.
- Apex and www are separate entries — tell us about both and we'll set up both.
- Single-article domains serve exactly that article; other paths return visitors to the main site.
- Mapping changes propagate across replicas within 30 seconds.
Have a domain that needs a page?
cnamely is an operated platform — access is provisioned, not signed up for. If you work with us, sign in. If not yet, the mechanism above is the pitch.