Safety checks and disabled codes
Which destinations we block, how we review codes, and what scanners see if a code is disabled.
We check every destination you save, including fallback URLs, rule destinations, bio page links and lead form redirects. This protects the people who scan your codes.
Destinations we refuse
A save fails with a message explaining why if the destination:
- isn't an
http://orhttps://link; - contains a username or password;
- uses an IP address or a local hostname instead of a public domain;
- points at another DynaQR link;
- uses a link shortener (use the final URL instead);
- is on a list of unsafe sites (phishing or malware).
Reviews
After you save, we check the destination and the account for risk. Most codes go live as normal. Some are also queued for our team to review. A code that looks dangerous can be disabled automatically. We re-check active destinations every week.
What a disabled code looks like
- In your dashboard, the code shows Disabled and a "This code was disabled" notice. You can't edit, pause or archive it, and it still counts toward your dynamic code limit.
- People who scan it see a "Warning: this link was disabled" page with a Report this code button.
If you think we got it wrong, email [email protected]. If a review clears the code, it goes back to active.
Reporting a code
Each DynaQR link domain has a /report page, and bio pages have a Report link in the footer. Anyone can use them to report a code they think is misused.