QR code custom domain: why the redirect domain should be yours

What the short URL in a QR code actually is

A dynamic QR code does not hold your destination. It holds a short address on a redirect server, and the server sends each scan to the destination you have set. That indirection is what makes the code editable and trackable, and it creates a dependency: whoever controls the domain in the short address controls where every printed copy goes.

On a default plan that domain belongs to the platform, on QRCodeKIT as on every other: our codes carry qrkit.co, and older ones uqr.to. That is fine for a flyer that will be recycled next month. It is a structural weakness for a menu, a label, a sign or a vehicle that will be scanned for years, because the platform's decisions, its prices, its terms, its continued existence, become decisions about your print.

What a custom domain changes

A QR code custom domain replaces the platform's domain in the short URL with a subdomain you own, so the printed code carries a branded short URL on your domain. The code then holds qr.yourbrand.com/spring rather than a link on the platform's domain. Technically the subdomain still points at the platform, through a DNS record called a CNAME that says "for this hostname, ask the platform's server". The platform serves the redirect exactly as before.

The difference is who can change that record. You can. If you move to another platform, you recreate the codes there with the same endings and repoint the CNAME. Propagation takes from minutes to a day, and every printed code follows you without a reprint. If the platform raises its prices, changes its terms or closes, you have an exit that does not involve the printer. The switching guide walks through that move, platform by platform.

QRCodeKIT's help centre calls this white-label URL masking. It is not the same as white-labelling a whole QR platform to resell to clients under your own brand, which the agencies piece covers.

Two further benefits come along. A branded short URL is recognisable to the person scanning, which helps them tell a genuine code from a fraudulent one; the trusted-domain piece and the quishing explainer make that case. And a branded short URL reads well printed beside the code as an alternative to scanning, one of the options the European Accessibility Act piece lists.

What a custom domain does not change

It does not move where scans are processed; the redirect still runs on the platform's infrastructure, so hosting and data residency are still the platform's. It does not change analytics, design or code types. It does not make static codes editable, because static codes have no redirect at all. And it does not help codes already printed on the vendor's domain: those stay where they are, which is why this decision belongs before the first print run, not after.

Whose domain is it?

"Custom domain" means different things on different platforms. The test is simple: a domain is yours if you registered it and you can change its DNS records. Read on each vendor's own pages, last checked 8 October 2026, and re-verified quarterly.

A vendor-registered domain and a white-labelled subdomain of the vendor's domain both look branded in print, and both leave the vendor in control. If a sales page says "custom domain", ask who the registrant will be.

Choosing the subdomain and the endings

Pick a subdomain that will still make sense in five years and that you will never need for anything else: qr, go, scan, link. Avoid campaign and product names in the hostname. QRCodeKIT, like most platforms, uses a subdomain for this; the bare root domain and the www hostname are not supported.

Then decide how endings will be set. Most platforms generate a random ending for each code and let you edit it. On QRCodeKIT the ending is editable on every plan, one code at a time, and it should be set before printing, because changing an ending after print makes the printed code unusable. A convention that lasts looks like campaign-place-language: qr.yourbrand.com/menu-madrid-en. The same convention makes any future move easier, because reproducing the endings on a new platform is a matter of reading them off a list. Bulk creation from CSV cannot set endings, so codes you want to name are created or edited individually.

How to set it up on QRCodeKIT

A subdomain you own is included on Pro (one) and Enterprise (several). The setup has two halves: your DNS provider and your QRCodeKIT account. The help-centre article has the details.

At your DNS provider:

1. Open the DNS management page for your domain and add a new record of type CNAME.
2. In the host, name or subdomain field, enter the subdomain you chose, for example qr. Root domains and www are not allowed.
3. In the target, value or points-to field, enter whitelabel.qrkit.co.
4. Leave the TTL as it is and save.

In QRCodeKIT:

1. Open Settings, then Custom domains, and add your subdomain. Then ask our support team to activate it.
2. Open a code, choose Customize QR, and edit the short URL: select your subdomain and set the ending.
3. Download the code and scan it with two phones before anything goes to the printer.

If you manage codes from an AI assistant through the MCP connector, create the code there and set its subdomain and ending in the dashboard before printing.

A checklist before the first print run

• The subdomain sits under a domain your organisation registered and renews, not a colleague's personal account and not the vendor's.
• The CNAME record points at the platform and the subdomain is active.
• Every code that will be printed shows your subdomain in its short URL, with a meaningful ending.
• The ending convention is written down where the next person will find it.
• A printed proof has been scanned with two phones and the redirect followed to the end.

The cost, and how to think about it

On QRCodeKIT a subdomain you own comes with the Pro plan at $50 a month billed yearly, or $65 monthly, alongside 1,000 codes, unlimited scans and ten seats. See the pricing page. Elsewhere the price and the ownership vary, as the table above shows, and the comparison series covers each platform in depth.

Whatever the price, weigh it against the reprint. A restaurant group's menus, a brand's packaging run, a fleet's vehicle graphics, a campus's signage: any one of those costs more to reprint than years of the plan that would have made reprinting unnecessary. For material that lasts less than a season, the platform's domain is fine. For everything else, the domain in the print should be yours, and the time to decide is before the ink.

Frequently asked questions