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 & domainsPlus+
Branded short links on your own domain
Use first-party verified branded hosts, keep slugs unique per domain, and isolate multiple brands, clients, or products without collision.
Per-domain
Slug uniqueness
Strict
Host matching
Multi-brand
Workspace isolation
app.nimriz.com/domains
Verified domains
Strict host matching · per-domain slugs
go.northwind.devPending
TXT _nimriz.go → nim-verify=8f3c…
/_health, /api/*, /.well-known/* stay reserved · managed-domain loops blocked
3
Domains
48
Links
3
Brands
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With Branded links & domains
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you 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.
- Apex and www are treated as separate records - no silent aliasing between hosts.
DNS verification, scoped to your workspace
1
Add host
go.brand.com
2
Add DNS record
CNAME → edge.nimriz.com
3
Nimriz verifies
Strict host matching on
How it works
1
Verify your domain
Add a DNS record to prove ownership. Nimriz validates the record and enables the domain for your workspace - strict host matching applies immediately.
2
Create short links under that host
Every link is scoped to a specific domain. The same slug can exist on separate domains because lookups are always keyed by host plus short code, not slug alone.
3
Manage multiple brands from one workspace
Add more domains as your brand portfolio grows. Each domain stays isolated - one workspace can run agency clients, product lines, or regional brands without collision.
Everything included
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.
Multi-brand workspace
Operate multiple client or product domains from one workspace. DNS ownership is scoped per domain so no brand bleeds into another.
Reserved path protection
System paths like `/_health`, `/api/*`, and `/.well-known/*` stay outside the public slug namespace regardless of what short codes exist.
Loop prevention
Managed-domain loop prevention blocks shortening back into another Nimriz-managed redirect host - a common footgun with multi-tenant link platforms.
Redirect posture control
302 stays the default for change-friendly campaigns. Choose 301 per link only when a permanent cached redirect is explicitly what you want.
How teams keep brands separate
A single workspace can manage multiple domains while keeping redirect handling explicit instead of guesswork.
Brand A host
go.acme.com/launch → acme.com/spring-launch
Brand B host
lnk.startup.io/demo → startup.io/demo-day
Same slug, different brands
"launch" is valid on both domains - no collision, no aliasing.
Redirect posture
302 by default; 301 is a deliberate per-link choice, not a global setting.
Host resolution · same slug, no collision
/launch on two brands
No collisionBrand A
go.acme.com
go.acme.com/launch
acme.com/spring-launch
Brand B
brand-b.to
brand-b.to/launch
brand-b.com/q2-event
Lookups are keyed by host + short code, never by slug alone. The same launch is valid on every verified host.
302 by default301 is a deliberate per-link choice, never a global setting.
What this means operationally
- Host resolution happens before slug lookup, so routing stays explicit for agencies, multi-brand teams, and client 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.
- DNS verification scopes ownership to a workspace without requiring platform-level admin access.
Ready to try it?
Branded links & domains is available on supported plans
Create an account to explore Nimriz, then use pricing to choose the plan and setup path that matches this workflow.