All Collections
Troubleshooting: Custom Domain Not Verifying
Troubleshooting: Custom Domain Not Verifying

If your custom domain is showing as unverified after adding the DNS records to your host provider, here's what to check for.

Updated over a week ago

Custom domain not verifying? You're in the right place.

If your landing page's custom domain isn't verifying, it'll say 'Unverified' on the domains page of your account. You can click the 'Refresh' button to check the records again:

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 that URL:

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 hours to update their records. Typically, it will be faster than that, but unfortunately the length of time this takes is out of our control. If it's a matter of a DNS propagation delay, the only solution is to wait it out.

That said, if it's been longer than 24 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 24 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 didn't include the 'www' in ConvertKit

When adding your domain or subdomain in ConvertKit from the domains page, make sure you omit the www.

For example, instead of, just add

Double check your DNS records

The values added to your DNS records with your host need to be exactly as they are shown in ConvertKit, and you have to include all three records.

Make sure there are no other records in conflict

In your DNS records, make sure that you have no other A records or AAAA records present. If you do have any other A or AAAA records present, they will need to be removed before you can use your custom domain with ConvertKit.

☝️ 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 before removing them, just in case (or at least make a backup 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 24 hours and your custom domain still isn't verifying, please reach out to us, including a screenshot of your DNS records.

Did this answer your question?