Reserved subdomains

What names you can't claim, and why.

A handful of subdomains under nura24.com are reserved for the platform itself and can't be claimed by a workspace. If you try, the signup form says "subdomain is reserved" and you'll need to pick something else.

The list

Platform infrastructure: app, www, api, cdn, admin, mail
Marketing surfaces: help, docs, status, blog
Locale subdomains: es, pt-br, fr, de, it, ro (and any future locale code we add)

Why these specifically

<tenant>.nura24.com/admin is the agent dashboard for every workspace. We need this to point at a single host, not yours.
api.nura24.com, cdn.nura24.com, mail.nura24.com are reserved for future infrastructure (REST API, asset CDN, transactional mail).
Locale subdomains serve the marketing site in that language. Allocating ro.nura24.com to a tenant would conflict with nura24.com/ro being Romanian for everyone else.
admin, help, docs, status, blog are platform-level pages that serve all workspaces — we keep them centralized for SEO and onboarding.

What if I really want one of these?

If you have a strong reason (you're a Romanian-language support firm called "Ro" and you want ro.nura24.com), get in touch via the contact form — we don't have a process for releasing reserved names today, but we'll consider it case-by-case.

Custom domain workaround

The reserved list applies only to subdomains under nura24.com. If you attach a custom domain, you control every part of the URL — you can host your portal at help.acme.com even though help.nura24.com is platform-only.