J
Jeanus
Help centre
All articlesContact support
Help/Troubleshooting

Custom domain wont verify

DNS zone-doubling, propagation delay, TXT vs CNAME.

Updated 2 July 2026

You have added a CNAME for your custom portal domain and hit Verify, but Jeanus says "Not yet verified". The four most likely causes:

1. DNS has not propagated

DNS changes usually propagate within minutes but can take up to 48 hours in edge cases. Test your CNAME directly with dig cname customers.yourdomain.com or an online tool like whatsmydns.net. If it does not resolve to Jeanus's edge, wait and try again.

2. Cloudflare proxy is on

If your DNS is on Cloudflare, the CNAME record often defaults to "Proxied" (orange cloud). Set it to "DNS only" (grey cloud) so the CNAME resolves cleanly. You can turn the proxy back on later once verification is successful - or leave it off if you want Jeanus to handle SSL directly.

3. Zone-doubling

Some registrars auto-add a CNAME for the whole zone. Check you do not have two CNAMEs pointing the same subdomain in different directions - only the Jeanus one should be there.

4. Using an apex domain

You cannot point the root domain (yourdomain.com without a subdomain) at Jeanus via CNAME - the DNS spec does not allow CNAME on the apex. Use a subdomain like portal or customers instead.

Still stuck after 24 hours?Email help@pixelandshovel.co.uk with the domain you are trying to verify and a screenshot of your DNS records. We can look up the SSL cert issuance status and tell you whether the block is on the DNS side or the platform side.