Bring your own domain.
Run branded links on your own domain with a single DNS record. Your links, your data, your exit — export to nginx, Caddy, CSV or JSON whenever you like. No lock-in, ever.
Generic works. Yours wins.
Three places a branded domain quietly outperforms any shared shortener — in print, in feeds, and on Google.
Printed once. Working forever.
A QR on ten thousand flyers can't be reprinted — on your own domain it never has to be. Leave rii tomorrow, point the domain anywhere, and every printed code keeps resolving. On a shared shortener domain, the day the provider dies, so does your print run.
Example: a printed flyer QR pointing at a generic shortener link stops working if the provider disappears; the same QR on links.yourbrand.com keeps resolving, because you can point your own domain anywhere.
People click what they recognize.
Same share, same preview — watch the card: only the domain people see before they click changes. A name your audience already knows converts; unknown shortener domains get skipped, filtered, or flagged.
Example: the identical share — the only difference is the link domain. As rii.link/x3f9 it gets a 2.1% click-through rate; as links.yourbrand.com/launch it reaches 6.2%.
Every click builds your domain. Not ours.
Search engines and mail filters score domains by their history. On your own domain that history compounds for you — rankings, previews, deliverability. On a shared domain you inherit everyone else's.
Example: a search result for links.yourbrand.com/launch with its own sitelinks and history, while the generic rii.link short link carries no history of its own.
Live on your domain in minutes.
Point one CNAME at rii.link and you're done — we handle SSL, renewals and the routing engine behind it.
CNAME links.yourbrand.com → cname.rii.link
Your links. Your data. Your exit.
Export everything, any time. Switching away is a feature, not a threat — which is exactly why you won't want to.
# rii.link export — nginx
server {
listen 443 ssl;
server_name links.yourbrand.com;
location = /summer-sale { return 302 https://myshop.com/summer; }
location = /app { return 302 https://apps.apple.com/id123; }
location = /menu { return 302 https://myshop.com/menu; }
}Your domain does more than links.
Connect the domain once — email forwarding already works today, and there's more on the way.
Email forwarding
LiveReceive mail on your link domain without running a mail server — forwards land in the inbox you already use.
Nameserver delegation
PlannedHand us the zone and skip DNS bookkeeping entirely — records, SSL and routing managed as one.
Ready to build smarter connections?
Branded links, visual routing and LLM-ready responses — start free, no credit card needed.