[jivings]

Yes. DNS shows it should be redirecting to leavemealone.helpkit.so but it actually redirects to dinkydani.gitbook.io

[bauruine]

help.leavemealone.com. is a CNAME to leavemealone.helpkit.so which again is a CNAME to helpkit-ssr.onrender.com. and so forth till you get the A records. Your browser then connects to that IP and there you get the 302 redirect. I'm still not sure what I should see here.

EDIT: This is a CNAME chain and although it's not recommended it's valid https://serverfault.com/a/309660

[jivings]

The A records that you've gotten to are unrelated to Gitbook and there are no 302 redirects on our side. As far as I understand it's some internal redirect happening in Cloudflare's network.

You can read more info here: https://community.cloudflare.com/t/dns-subdomain-no-longer-w...

[bauruine]

Thanks for the explanation. I still don't know exactly what's going on here. How do the DNS records look on the Cloudflare UI?

[bauruine]

Then you have to ask helpkit.so why they are using render.com to do the redirect.

[jivings]

The request is never hitting HelpKit's servers.

[bauruine]

But it's hitting their DNS zone and they have decided to add a CNAME to helpkit-ssr.onrender.com for leavemealone.helpkit.so.

[jivings]

help.leavemealone.app -> CNAME -> help.leavemealone.com -> CNAME -> leavemealone.helpkit.so

Gitbook is nowhere in the chain