QRinio

Step by step

Fix QR domain verification problems

Domain verification checks more than a TXT record. QRinio also confirms public routing and an HTTPS challenge at the claimed hostname. A pending status means the hostname is not yet available for creating branded resources; repeatedly pressing verify does not repair DNS.

QRinio · BundS GmbH

Updated:

Example dataQRinio

example.com

Illustrative address: qr.example.com/r/summer. The printed address stays the same when its destination changes; this example domain is not connected.

A domain has the correct TXT token but still serves the previous hosting provider’s page, so its HTTPS challenge fails.

Narrow down the error step by step

First check that you created records for the exact subdomain. Some DNS interfaces append the domain name automatically, so entering it twice can place a record under the wrong name. Then compare publicly resolved records and the certificate.

If DNS is correct but the HTTPS check fails, inspect routing at the hosting entry point. A login screen, redirect to the main website or old server assignment can intercept the check. Keep working old QR hostnames available during a move.

How it works

  1. 01

    Compare the exact hostname, proof record name and value with the account instructions.

  2. 02

    Check that its public CNAME and addresses lead to the intended ingress and not a private network.

  3. 03

    Verify the certificate covers the hostname and that the challenge path reaches QRinio without a login or unrelated redirect.

What to keep in mind

DNS caches take time to refresh. Remove stale routing records carefully and check from an external network before retrying. The verified-domain and pending-domain allowances are separate.

Frequently asked questions

Why can HTTPS fail when my website opens?
The site may redirect to another host, use an unsuitable certificate or route the challenge somewhere else. Verification checks the exact hostname, not just a reachable homepage.

Keep exploring