Custom domain qr code host in ink
SmartQRCode editorial · Updated October 2026
A custom domain qr code host is the hostname baked into the printed URL. It is not a CNAME you can swap after the truck leaves. Apex and www travel as a pair. Only an active host is safe to encode. A Canva file is the right one-off when the payload will never move and you will not count scans.
What a custom domain qr code host encodes
Apex registers www with the same job. An allowance slot while pending still spends the hostname. A retired host still on project can block a later attach. Short code isolation 404s a foreign code on your host.
The camera opens a string. That string is scheme, host, and path. A custom domain qr code host replaces the product apex in that string at create time. Every later scan, whether a 302 or a landing page, is requested on that name. The white label qr scan host article is the scanner-chrome view of the same object.
Statuses describe whether you may encode yet. Pending DNS means the row exists and the name is registered but the records are wrong. Verifying means DNS looks right and certificates are still in flight. TXT challenge means the hostname already lives on another Vercel account. Active is the only status a new code should be created on. Misconfigured means it was active and DNS has since drifted; printed codes may already be failing. Failed does not hold a slot. Retired stops resolving but can leave the hostname on the project.
Pending and misconfigured hold an allowance slot on purpose. A half-configured name still occupies the project. Parking unlimited hosts by never finishing setup would otherwise be free.
Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. Dynamic QR codes and the website URL generator are the usual encodings on a host. Codes that never expire fit packs that outlive a campaign URL. Shelf work lives under retail marketing codes.
How to choose the hostname you will plate
Write the name you want guests to read in the padlock, then refuse to encode anything else.
- Decide apex versus subdomain. Apex is brand.com. A subdomain is usually qr.brand.com. Apex registration also registers www so the pair does not silently split.
- Attach the name and wait for active, including SSL. Do not export during pending_dns or verifying.
- Create the QR against that host. Read the encoded URL in the download, not in the on-screen preview, which encodes /qr-preview.
- Export SVG for cutters and a 300 dpi PNG or PDF for toner at the final millimetre size.
- Keep a four-module quiet zone. Use at least 2 cm across at 30 cm; larger for aisle distance.
- Proof-scan on cellular. Confirm the certificate names the host you intended.
- If an older run already encodes smart-qrcode.com, leave those rows on the platform host. They are a different physical object.
- Document who owns DNS. A registrar change six months later is how active becomes misconfigured.
Details of records and certificates sit in custom scan domain and SSL. The print-in rule is in custom scan domain for QR.
Apex versus a qr subdomain
Apex looks cleaner in a pitch deck. It also means the scan host is the same name as the brochure site, which is a DNS and routing collision you have to design for. The product registers www alongside apex so a guest who types the www variant does not hit a dead certificate.
A qr subdomain keeps marketing on the apex and scans on a dedicated name. Most retainers pick the subdomain because the brochure site already has its own CDN, redirects, and CMS. Putting scans on the apex is a choice, not a default.
Neither choice changes ISO/IEC 18004. Both choices are hosted: they last as long as the provider resolves them. A static Canva URL in the modules has no host of ours and no edit after print.
Can another tenant use my host
They cannot complete a scan. The track path and the landing-page path both compare the code's domain to the request host. A mismatch 404s. That closes the obvious attack: wrapping someone else's destination in your certificate.
Your own codes created on the platform host still resolve there. Attaching a custom domain qr code host does not orphan old ink. It only affects codes created against the new host.
Do not test a client job by scanning through a different client's host. The 404 is correct. If you need a staging scan, use the host that will be in the modules.
Host failures that survive a reprint
Misconfigured DNS after a registrar move leaves cartons in the field requesting a name that no longer points here. The art is fine. The host is not. Restore records or reprint onto a host you still control.
Retired stops resolution. It does not magically detach the hostname from the project. Planning a cutover to a new vendor on the same name takes coordination, not a toggle.
Screenshot exports, dark grounds without invert, and logos that cover finders fail before the host is asked. Fix the symbol, then argue DNS.
A provider pause or an unpaid invoice stops hosted codes on every hostname. F91 does not care whether the padlock says you or us.
What belongs on the print ticket next to the host
Prepress should receive four strings that are not implied by the art: the encoded https URL, the short code, the SKU, and the host status at export time, written as the word active. If the ticket says "client domain TBD," it is not a ticket. It is a wish.
Add the millimetre size, the quiet zone in millimetres at that size, and the file format the press actually plates. SVG for flexo and cutters. 300 dpi PNG or PDF for toner. A 72 dpi RGB screenshot from a laptop is how modules grow grey halos.
Name the person who owns DNS after launch, with a mailbox that will still be read in a year. Registrar transfers are how an active custom domain qr code host becomes misconfigured while the cartons are already in shops. Governance after ink is a different article. The ticket still has to name a human.
If the job is a vehicle wrap or a window, write the viewing distance. 2 cm is a table number. A neighbouring lane is tens of centimetres. The host can be perfect and the camera still fail because the modules are too small from the road.
Copy the encoded URL into the ticket as a paste, not as a retyped hostname. One missed letter in the host is a reprint, and short code isolation will not save you if you encoded the wrong name on purpose.
When the default apex host is enough
If the brief never mentions the padlock, keep smart-qrcode.com in the modules. You still get 302 edits and counts by country and device. You skip allowance slots, TXT challenges, and the chance that a DNS ticket 404s a formed pack.
If the brief also never mentions edits or counts, skip hosting. Canva or another free static generator is the honest file. Print at working size, keep the quiet zone, and do not buy a custom domain qr code host for a poster that dies on Monday.
Questions this raises
Apex is the bare brand name. Registering it also registers www so the pair does not split. A qr.brand.com subdomain keeps marketing on the apex and scans on the subdomain. Pick before you encode.
No. Short codes are checked against the host. A mismatch 404s. Your codes still resolve on smart-qrcode.com if they were created there.
When the padlock name is not part of the brief. Hosted types on smart-qrcode.com still edit after print. A Canva static file is enough when you will never edit or count.
Retired stops resolving. The hostname can remain on the project. Do not assume you can attach the same name elsewhere the same afternoon.
Pending DNS, verifying, TXT challenge, active, and misconfigured all hold a slot. Failed and retired do not. A half-finished host still spends the hostname on the project.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.