Per-Space addresses
When address routing is enabled, every published Space—including Community and Free—uses https://your-label.htmlspace.app/. Anonymous Community publishing receives a server-generated label. Verified registered owners can choose or change a label in Domain; a paid plan or Dedicated mode is not required for the basic address.
The stable URL follows the Space current content. A Release preview URL is separate and identifies a specific immutable Release.
Address changes and compatibility
New chosen labels use 3–32 ASCII lowercase letters or numbers with internal hyphens. Unicode and xn-- punycode labels are not accepted. Platform, infrastructure, and HTMLSpace brand labels are reserved. Existing labels are grandfathered.
The first generated-to-chosen change has no prior cooldown; after that, a Space has a 30-day cooldown. An account may acquire up to 3 labels in a rolling 12 months, and a Space may retain up to 3 prior labels. The first generated label counts as an alias and the first chosen label counts toward the account quota.
An owner may reactivate a label retained by the same Space; this counts toward cooldown and account quota but does not use another alias slot.
Current and prior labels remain permanently reserved to the same Space. Prior labels redirect directly to the latest address when the Space is publicly eligible; suspended or deleted Spaces return not found. Browser storage, service workers, installed PWAs, permissions, and authentication state do not migrate; external API CORS allowlists may need an update.
Shared-path URLs and prior-label hosts use 308 redirects that preserve the path and query. Previous-origin write requests return not found. Redirect activation and caching are environment-gated.
The Dashboard supports independent custom-domain additions, removal and TXT ownership checks. Ownership verified does not mean website routing or HTTPS is active; public activation remains unavailable pending edge setup.
Tips and limits
- Use only the TXT ownership record displayed for your saved connection. Routing and certificate DNS records must come from approved setup, not guessed values. Never change nameservers, MX or email records for this setup.
- Keep links to the stable URL for your current site and use a release-scoped URL only when you need to inspect a particular Release.
Custom domains and paid hosting
Active Premium or Advanced is required to add or serve custom domains. Adding a domain uses the displayed setting-edit credit charge; removal is free. Public activation remains separately gated and pending acceptance.
After paid hosting expires, existing entries may be retained, ownership-checked, explicitly renewed or removed without a paid plan or a verification credit charge. Custom-domain serving stops immediately at expiry; it resumes only after paid-plan renewal and fresh routing, certificate and Space-readiness checks. Your included HTMLSpace address is unaffected.
An existing claim held by another account is not transferred automatically. Ownership conflicts require manual review, fresh DNS proof and explicit operator approval.
Where certificate setup is enabled, copy only the exact certificate authorization CNAME displayed for your connection. It is separate from the ownership TXT and website routing records. Use Check connection again after DNS propagation; certificate preparation alone does not activate hosting.
Where manual recovery is enabled, an active Premium or Advanced owner can request review with fresh claimant-specific TXT proof and consent to the normal domain-add charge. Proof alone never transfers a hostname. An operator must approve interruption, finish old-resource and edge cleanup, then check proof again. The normal addition charge is captured once only when the replacement connection succeeds; it still needs fresh hosting readiness.
Domain tab checklist
- Open the Space editor and select Domain.
- Review the current per-Space address.
- Check availability, then review the current and new full URLs before confirming an address change.
- Treat any custom-domain entry as pending until the platform confirms activation.