Branded Domain for QR Codes: How to Choose, Set Up and Test One

13 November 2026Branded Domain for QR Codes: How to Choose, Set Up and Test One

Branded Domain for QR Codes: How to Choose, Set Up and Test One

Hand-drawn QR and domain title card

A branded domain for QR codes means the web address a scan passes through is yours, such as go.yourbrand.com, instead of a generic short link owned by a QR platform. It matters for two reasons: people see a name they recognise before the page loads, and you keep control of the address printed in the code. The part many guides skip is permanence. A branded domain only helps if the redirect behind it keeps working for as long as the print run is on shelves, walls and packaging. Qrlytics is built around that second point: codes created during an active subscription stay functional, whatever happens to billing later.

Qrlytics
qrlytics.app
Keep Printed QR Codes Working
Qrlytics keeps codes created during an active subscription functional, with dynamic URL updates and real-time analytics for QR campaigns.
Visit

TL;DR

  • A branded domain replaces the platform’s default short link with your own subdomain, so scanners and security filters see a name they know.
  • Use a dedicated subdomain (for example go.yourbrand.com), not your main website address, and keep it for the life of the print.
  • Setup is a DNS record, usually a CNAME, plus verification and an HTTPS certificate. Test on real phones before anything goes to press.
  • The domain is only half the safeguard. The redirect service behind it must keep running, and you must keep the domain registration renewed.
  • Dynamic codes let you change the destination later without reprinting, which is what makes a printed branded code a long-term asset.

Table of Contents

  • What a branded domain for QR codes actually is
  • Why businesses put their own domain in QR links
  • How to choose the domain or subdomain
  • How to connect a branded domain: the DNS setup
  • Test it before it goes to the printer
  • What happens when the domain, DNS or platform changes
  • A worked example: a restaurant group
  • Common mistakes to avoid
  • Where Qrlytics fits
  • Our perspective
  • FAQ
  • Sources

What a branded domain for QR codes actually is

Three things get confused, so it helps to separate them.

The destination URL is the page a scanner finally lands on, such as a menu, a product page or a campaign landing page.

The redirect URL is the short address that is encoded inside the QR code. With a dynamic code, the pattern is simple: the code holds a short link, the short link points to the destination, and you can change the destination whenever you like. We explain that mechanism in our guide to dynamic versus static QR codes.

The branded domain is the host name of that redirect URL. By default it belongs to the QR platform. When you use a branded domain, it belongs to you.

This is also different from a branded QR code design, which is about logo, colours and frame. Design changes how the square looks. A branded domain changes what is written inside it. The two work best together, and our piece on branded QR codes that survive print and tracking covers the visual side.

What a branded domain for QR codes actually is

Why businesses put their own domain in QR links

The reasons are practical rather than cosmetic.

Recognition before the click

Most phone cameras show a preview of the link before the browser opens. A preview that shows your own name looks like it belongs to you. A preview that shows an unfamiliar short domain looks like any other link, and in an age of QR-code scams, people are right to hesitate at those.

Fewer problems with filters

Corporate mail gateways, browser warnings and security apps are more cautious about generic shared short-link domains, because those domains are used by every kind of sender, good and bad. A domain tied to your business, with a clean history, is a more predictable thing for filters to evaluate. No setup removes the need to test, which is covered below.

Ownership of the address

If your printed code carries a platform’s domain, the platform decides what happens to that address. If it carries yours, you hold the registration and the DNS records. That is the foundation for moving between providers later without touching the printed material.

One consistent name across campaigns

A single subdomain used on packaging, posters, flyers, menus and event signage makes your codes recognisable as a family. It also makes reporting tidier, because every scan comes through one named host. For how consistency pays off, see why QR code consistency matters for marketers.

How to choose the domain or subdomain

This is the decision you will live with longest, because it ends up in print. Take it slowly.

  1. Use a subdomain of a domain you already own. Something like go.yourbrand.com or scan.yourbrand.com keeps the brand in the address and leaves your main website untouched.
  2. Keep it short and easy to say. Short hosts leave the code less dense, and a less dense code scans more reliably at small sizes.
  3. Do not tie it to a single campaign. A name like spring-sale.yourbrand.com becomes awkward when the same code lives on after the sale. Pick a name that is still true in three years.
  4. Do not reuse your main site’s address for redirects. Keeping redirects on their own subdomain means a website redesign, a CMS migration or a change of hosting cannot accidentally break the code path.
  5. Make sure one person or team owns the registration. The most common cause of a dead branded domain is a lapsed renewal on a card that expired or an email nobody reads. QRCodeFYI lists domain expiration among the usual causes of QR link rot, alongside platform shutdowns and expired SSL certificates.

If you are choosing between a brand-new domain and a subdomain of your main one, the subdomain usually wins. It inherits the reputation you have already built and costs nothing extra to register. A separate domain makes sense when the codes represent a distinct brand or product line.

A note on search visibility

Your domain decisions are not purely a QR question. A domain and its subdomains are part of your wider web presence, and it pays to think about how your content is found. One example of what structured content planning can do is this organic growth case study, which shows a site growing from 1,548 to 3,359 clicks a month.

How to connect a branded domain: the DNS setup

The exact screens differ between registrars and platforms, but the sequence is the same.

Step 1: Decide the host name

Pick the subdomain from the section above and write it down exactly. This is the value you will enter in two places, so a typo here causes most failed setups.

Step 2: Add the domain in your QR platform

In your platform’s domain settings, enter the subdomain. The platform then shows you the record you need to create, usually a CNAME that points your subdomain to a host the platform controls. A CNAME is a DNS alias: it tells the internet that your subdomain should be answered by another server.

Step 3: Create the record at your DNS host

Log in where your DNS is managed. This may be your registrar, your website host or a separate DNS service. Add a new CNAME record with the host name set to your subdomain label (for example, go) and the value set to exactly what the platform gave you. Copy and paste both values; do not retype them.

Two cautions where setups commonly go wrong:

  • A CNAME cannot sit on a bare root domain (yourbrand.com) alongside other records. That is one more reason to use a subdomain.
  • If your DNS host offers a proxy or “orange cloud” style option, follow the platform’s instruction on whether to enable it. A proxy in the wrong mode can block certificate issuance.

Step 4: Wait for propagation and verification

DNS changes can take from a few minutes to several hours to be visible everywhere. Most platforms check the record automatically and mark the domain as verified. If it stays unverified after a few hours, compare the record character by character with the one the platform asked for.

Step 5: Confirm HTTPS

Every scan should land on a secure address. Once the record resolves, the platform normally issues a certificate for your subdomain. Open the short link in a browser and confirm there is no certificate warning. An expired or missing certificate is another of the standard causes of dead QR links, so note the renewal arrangements as well.

Step 6: Create a test code and a real code

Create one throwaway dynamic code on the new domain and confirm it redirects. Only then create the codes for print.

Test it before it goes to the printer

Printing is the point of no return, which is why dynamic codes matter so much: the code itself cannot change, but its destination can. Even so, run this routine on every branded-domain code before it goes to press.

  1. Scan on more than one phone. Use at least one iPhone and one Android handset, with the default camera app and not a dedicated scanner.
  2. Check the link preview. The preview should show your subdomain, spelled correctly, with no warning.
  3. Test on mobile data and on Wi-Fi. Some corporate or guest networks filter differently from a mobile network.
  4. Confirm the landing page works on a phone. Load time, layout and any consent banner should all behave.
  5. Check that tracking survives the redirect. If you use campaign parameters, confirm they arrive intact on the landing page and that your analytics tool records the visit. Our guide to UTM parameters for QR codes walks through avoiding unattributed direct traffic, and the Tag Manager guide for QR landing pages covers the page side.
  6. Print a proof at the real size. Scan it from the distance people will actually stand at, in the lighting where it will hang. Make sure the logo or frame does not hurt readability; our notes on high quality QR codes cover contrast and size.
  7. Record the result. Note the date, devices and outcome so the next campaign starts from a known good baseline.

What happens when the domain, DNS or platform changes

A branded domain protects you from one risk and leaves two others. Knowing which is which is the whole value of this section.

Risk 1: the platform’s default domain is withdrawn. This is the one a branded domain removes. Since the host in your code is yours, you can in principle point it at a different service later.

Risk 2: the domain or its DNS lapses. Your registration expires, someone deletes the CNAME during a clean-up, or the certificate is not renewed. Every printed code on that subdomain breaks at once. Put the renewal in a shared calendar, use auto-renew, and list the subdomain in your DNS documentation as “do not delete”.

Risk 3: the redirect service stops working. A dynamic code relies on the provider’s redirect infrastructure and an active account. With many services, cancelling or missing a payment switches the codes off, and printed material becomes useless overnight. A custom domain does not fix this on its own, because the domain still points at a service that is no longer answering.

This third risk is the one we built Qrlytics to remove. Codes created during an active subscription stay functional permanently, regardless of billing status. If you ever need to move, our 7-step migration guide shows how to keep printed codes working, and how to update QR code links without reprinting explains the destination changes that sit behind it.

A worked example: a restaurant group

Imagine a restaurant group with twelve venues, each with a table-top menu code, a window poster and a takeaway bag sticker.

  • They choose menu.groupname.com as the single redirect subdomain.
  • They create one dynamic code per venue and per placement, so each scan can be told apart in reporting.
  • A seasonal menu change means updating destinations, not reprinting thirty-six pieces of material.
  • A year later the group redesigns its website. Because redirects live on their own subdomain, nothing changes for the codes.

The saving is not abstract. Table-top stands, laminated cards and window vinyls are the kind of print that is slow and costly to replace, and a lifecycle plan for the codes is what keeps them in use. Our article on QR lifecycle management covers that planning.

Common mistakes to avoid

  • Using a campaign-specific subdomain that no longer makes sense later.
  • Registering the domain under one employee’s personal account. When they leave, so does your access.
  • Testing only on one phone, then discovering a warning on another.
  • Changing the DNS record without checking which codes depend on it.
  • Printing static codes pointing straight at a long landing-page URL. They cannot be edited afterwards and are denser to scan.
  • Ignoring consent banners in testing. A banner that blocks the page or strips campaign parameters can ruin attribution. Qrlytics describes its analytics as GDPR-compliant, which helps on the tracking side, but the landing page’s own banners still need checking.

Where Qrlytics fits

A branded domain is one layer of a reliable QR programme. The other layers are a permanent redirect, an editable destination and analytics you can trust. Qrlytics offers dynamic QR codes with URL updates, real-time scan analytics, global scan heat maps, lifecycle scheduling, CSV export and API access for developers. You can start on the Free plan without a credit card, and Pro unlocks unlimited codes, advanced analytics and API access. Pro has no published price on the pricing page.

If you are building a campaign now, the dynamic QR code generator is the place to create codes you can edit later, and QR code tracking shows what you can measure once they are live.

Qrlytics

To see how permanent, trackable codes work in practice, create a free account at Qrlytics and make your first dynamic code.

Our perspective

Most advice about branded domains stops at the look of the link. We think the more important question is what stands behind it.

A name you own in the preview builds trust, and we encourage anyone printing at scale to think carefully about their address. But a printed code is a promise to everyone who scans it, sometimes years later. The promise breaks when a redirect is switched off because a subscription lapsed, not when a link looks unfamiliar.

That is why we guarantee that codes created during an active subscription keep working permanently, whatever happens with billing. Combined with editable destinations and scan analytics, it turns printed material into a measurable channel that you control, not a cost you have to repeat.

The

FAQ

Do I need a branded domain for every QR code?

No. One subdomain can serve every code you create, which is the neater approach and keeps reporting consistent. Create a separate domain only for a distinct brand.

Can I use a branded domain with a static QR code?

A static code holds the destination address directly, so it can carry your own domain only if the page itself lives there. It cannot be redirected or edited later. Dynamic codes give you the redirect layer that makes a branded short address worthwhile.

What DNS record do I need?

Usually a CNAME on a subdomain, pointing to the host that your QR platform specifies. Copy the values exactly as shown, then wait for verification and confirm the HTTPS certificate has been issued before printing.

What happens if my domain registration expires?

Every code using that subdomain stops resolving until you recover the registration, so use auto-renew and a named owner. Treat the domain as part of the print run, not as a website detail.

Does a branded domain improve scan rates?

It can build confidence at the moment of scanning, because people see a name they recognise. Results depend on your audience and placement, so compare scan analytics across codes. Our guide to ways to boost QR code scans lists what else makes a difference.

Sources

  • QR Code Link Rot: Prevention and Monitoring, QRCodeFYI

Recommended

  • Marketers: Branded QR Codes That Survive Print and Tracking
  • Avoid Costly Reprints: QR Code Best Practices for Marketers
  • Examples of branded code landing pages for marketers
  • How to generate QR codes: the marketing pro’s guide