Verified branded hosts
Bring your own domain and keep each host explicit. Nimriz treats apex and www as separate records instead of silently aliasing them.
Branded links & domains
Branded links, protection, and expiration
Use first-party or verified branded hosts, keep slugs unique per domain, and add protection or expiration controls when a link needs tighter handling.
What teams get
- Connect branded short domains with DNS verification and explicit host-level control.
- Keep short codes unique per domain so brands, products, or clients never collide.
- Protect sensitive links with a password and let expired traffic fall back cleanly instead of breaking the visitor journey.
Availability
Available now
Domain-bound slug uniqueness
The same short code can safely exist on multiple domains because lookups are keyed by host plus short code, not by slug alone.
Password-protected links
Gate a redirect behind a password when access should stay controlled without changing the short URL itself.
Expiration and landing controls
Use expiration where policy requires it and send invalid or expired traffic to branded fallback destinations instead of dead ends.
How teams keep brands separate
A single workspace can manage multiple domains, protect sensitive links, and still keep redirect handling explicit instead of guesswork.
Brand host
https://go.acme.com/launch
Protection
Optional password gate for invite-only or internal campaign materials.
Expiration
Expired traffic falls back to a branded destination instead of a dead redirect.
Redirect posture
302 stays the default; 301 is still a deliberate per-link choice.
What this means operationally
- Host resolution happens before slug lookup, so routing stays explicit for agencies, multi-brand teams, and customer domains.
- Reserved paths such as `/_health`, `/api/*`, and `/.well-known/*` stay outside the public slug namespace.
- Managed-domain loop prevention blocks shortening back into another Nimriz-managed redirect host.
- Password gates and expiration controls work with the same short-link model rather than forcing a separate protected-link workflow.