You've set up the redirect and changed the DNS, but it isn't working yet. Work through the checks below in order. Most issues turn out to be DNS propagation or browser caching.
The DNS is verified, but my browser still shows the old site
Browsers and operating systems cache DNS results and redirects, sometimes for a long time. Test the redirect through a route that doesn't use that cache:
- Open the URL in a private or incognito window.
- Try a different browser or device.
- Use the redirect tester, which requests the URL from our network.
- Add a random query string to bypass local caches, for example
https://example.com/?v=2.
If the tester shows the correct redirect, the setup is right and your browser catches up once its cache expires.
redirect.pizza doesn't detect the DNS change
DNS changes take time to propagate. Allow up to 24 hours, although it's usually much faster.
- Check how far the change has spread with WhatsMyDNS.
- Compare the detected records with the required ones under Hostnames. A common mistake is leaving an old A or CNAME record in place next to the new one.
- Press the refresh icon next to the record in redirect.pizza to force a re-check.
The redirect works, but shows a certificate error
redirect.pizza provisions SSL certificates automatically once the DNS points at us. Issuing the certificate takes a few minutes after verification. If you still see a warning after that, check whether your domain has CAA records that block Let's Encrypt or Sectigo.
Still not working?
The redirect troubleshooting guide covers more scenarios, including redirect loops and mixed content. If that doesn't solve it, contact us via the chat or email support@redirect.pizza and mention the hostname involved. We're happy to help.