Frequently asked questions
Yes, if they encode a domain you control. Import them with bulk import or with help from our support team: every path and destination stays, and the printed codes keep scanning once the domain points to RedirHub. Codes that encode another vendor’s domain stay with that vendor; set up the same destinations on your domain for the next print run.
Only if the printed code encodes an active redirect URL. If it does, the destination behind that redirect can be updated at any time. A code that encodes a final web address directly cannot be repointed — the address is part of the pattern.
Scan it and look at the address bar as the page opens. If you briefly see a short redirect domain before landing on the final page, it is redirect-backed. If it goes straight to the destination, the destination is baked in.
No. The pattern encodes the redirect URL, and that URL never changes. Only the rule behind it does.
Yes. Scans travel through a domain you own, with HTTPS issued automatically. Core includes 25 connected domains and Pro 250.
It is a normal HTTP redirect, resolved before the destination page starts loading. In practice people see the destination, not the hop.
Yes. Each scan is recorded with volume over time, location, device and referrer, and the data is available in the dashboard or through the API.
RedirHub is built to manage redirect records at scale, with bulk import and export and a REST API available on every plan. How many you can manage depends on your plan and setup.
Redirects resolve while the account and connected domain are active. This is worth planning for with any redirect-backed print run, whichever provider you use.