Custom domain not verifying? You're in the right place.
If you've set up your custom domain in ConvertKit and it isn't verifying, it'll say "Unverified" in your account's Domains settings.
Try verifying the DNS records again by clicking the Verify button:
Your custom domain won't work until it's verified, so it's important to ensure it's verified as shown below before you share your custom domain URLs:
If your domain isn't verifying, keep reading for the most common reasons why and how to resolve them!
Give it some time
Some DNS servers can take up to 24 to 48 hours to update their records.
Typically, it will take faster than that, but unfortunately, the length of time this takes is out of our control. The only solution is to wait it out.
If it's been longer than 48 hours and your domain still isn't verifying, there are a few other things to check!
NOTE: Even if it hasn't been a full 48 hours yet, it's still worth double-checking the following potential reasons in the meantime, to ensure that one of them is not the actual cause.
Make sure you hadn't included the "www"
If you had manually connected your custom (sub)domain to ConvertKit, check that you had omitted the www when filling out your custom domain in the Your Custom Domain field.
For example, instead of filling out the Your Custom Domain field with www.yourdomain.com, you should have filled it out with just yourdomain.com.
If you had included the www when filling out your custom domain, remove the custom domain from your account and try setting it up again—without the www this time.
Double-check your DNS records
If you had manually connected your custom (sub)domain to ConvertKit, the DNS records you added to your host need to be exactly as they are shown in ConvertKit.
You also have to include all three records.
If your DNS records are incorrect, edit them in your host. Alternatively, delete them entirely and re-add them to your host.
After that, wait some time and verify your custom domain again.
Check for conflicting DNS records
If you had manually connected your custom (sub)domain to ConvertKit, make sure that you have no other A records or AAAA records present in your DNS records.
If you do have any other A or AAAA records present, they may need to be removed before you can use your custom domain with ConvertKit.
After removing your A or AAAA records, wait some time and verify your custom domain again.
☝️ Remove DNS records with caution. We can't advise as to what effect that might have on your website as each case is different.
If you have extra A or AAAA records present and you're not sure what they are doing, we'd recommend consulting your web developer or host before removing them, just in case.
(At the very least, make a backup of your A and AAAA records so you can easily re-add them if something goes wrong.)
Still having trouble?
If you've checked all of the above and it's been longer than 48 hours and your custom domain still isn't verifying, please reach out to us, including a screenshot of your DNS records.