Most new redirects that "don't work" are waiting on DNS or being hidden by the browser cache. Check that DNS points to RedirHub, then test in a private window. If the redirect works but lands in the wrong place, check the method, Path forwarding and Query forwarding.
1. Does DNS point to RedirHub?#
Open the redirect in the dashboard and click Check DNS. Until it shows DNS verified, visitors still reach your old server. DNS changes can take up to 24 hours; use WhatsMyDNS to follow the progress around the world. More in How long does the DNS change take?
- Old records left behind: remove other A, AAAA or CNAME records for the same name. If two records remain, some visitors get the old server.
- Wrong host field: most providers want @ for the root domain and just www (not www.example.com) for www.
2. Is your browser showing an old result?#
Browsers cache DNS answers and permanent redirects (301 and 308). After a change, your own browser may keep showing the old behavior while everyone else already sees the new one. Test the redirect:
- in a private or incognito window, or another browser,
- with a random query string, for example https://example.com/?v=2,
- with the Redirect tester, or from the command line:
bashcurl -I https://example.com/some-pageThe Location header shows exactly where RedirHub sends the request. While you are still testing, use 302 so browsers don't remember an unfinished destination.
3. "Not secure" or a certificate error#
The SSL certificate is issued right after DNS is verified, and the status moves from Queued to Provisioning to Secured, usually within minutes. If it stays stuck, check for CAA records on your domain: they must allow letsencrypt.org and sectigo.com (see What DNS types can I use?). More about certificates in Automatic HTTPS.
4. The redirect works but lands in the wrong place#
- Every page goes to the homepage: turn on Path forwarding so old-domain.com/about goes to new-domain.com/about.
- UTM tags or other parameters are lost: turn on Query forwarding.
- The path appears twice, or {host} / @ shows up in the URL: see Destination URL Variables.
- A specific path goes to the root destination: paths are matched exactly and are case sensitive; when no path matches, the root redirect is used. See Matching.
5. www works differently from the root domain#
A redirect for example.com also covers www.example.com, but only when www points to RedirHub in DNS too, usually with a CNAME record. If www still points to your old host, www visitors never reach RedirHub. If you created a separate redirect for www, that one wins for www requests.
6. Frame (Masking) shows a blank page#
The destination probably refuses to be shown inside a frame, or it uses http:// instead of https://. Only the destination's owner can change that; otherwise use a 301 or 302. See Redirect Methods Explained.
Still having trouble?#
If it still doesn't work after a few hours, contact us through the chat in the dashboard or at support@redirhub.com. Include the domain and the URL you tested, and we'll take a look.