Enabling SSL or HTTPS on your landing pages

Does Instapage Support SSL?

Yes! All our users can take advantage of our SSL certification for all of their domains and pages. You don't need to buy an SSL certificate - we will generate and install one for you.

SSL/HTTPS checklist

Secure pages are not allowed to contain insecure content. Because of this, it is necessary to go through these steps to ensure that your page is fully secured and that browsers will not prevent users from accessing your page:

1. All links on your page point to https URLs (https://) or schemaless URLs (//), including your redirect links on your forms or buttons.

2. Any custom code under Settings - JavaScript, Settings - HTML/CSS, or in HTML widget boxes on your page only point to https URLs (https://) or schemaless URLs (//).

3. You must have at least one page published on the target subdomain before the SSL certificate can be enabled. Please note that there may be a small delay between publishing the page and the certificate being activated. If It is not active a couple of hours later, please reach out to customer support. 

Based on the selected plan, customers are subject to different limitations on the number of subdomains available for publishing. These limits can be checked in My Account Admin >> Subscription section.

What do I need to do to have SSL on my landing pages?

A. If you are publishing to a custom domain that you haven't used with Instapage before - simply follow the publishing process and make sure your CNAME record is pointing to secure.pageserve.co. To learn more about how to publish your page, follow this article: https://d.pr/1HkNRR

B. If you are publishing to a custom domain that is already connected to your Instapage account, you will have to go into your registrar and edit your CNAME record to reflect the secure Page Server. This means that your old CNAME record needs to point now to secure.pageserve.co. After you do this, you will have to send our support team a quick email at help@instapage.com so they can enable SSL for you. This is not needed if you are adding a new domain to Instapage, only if you are editing an existing CNAME record.

C. Free SSL only applies for pages published through CNAME. If the page is published with WordPress or Drupal, the SSL must be sourced from their end.

D.  If you have a CAA record added to your domain, you will need to add an additional CAA record for letsencrypt.org in order for us to be able to apply an SSL certificate to your newly created subdomain. This is not necessary if you don't have an existing CAA record already. After you do this, you will have to send our support team a quick email at help@instapage.com so they can enable SSL for you. That's it!

Note that the SSL certificate cannot be activated for more than 50 subdomains of the same domain in a 7-day time frame.

NOTE: The SSL certificates do not renew automatically if the backend owner of the domain does not have a paid subscription anymore. Even if there are other users with paid subscriptions that have access to the domain, the SSL certificate will not renew automatically. For security purposes, a domain can only be owned by one Instapage account at a time, even if access was granted to other accounts. To request an ownership change, please follow the steps here: https://d.pr/X0VvkY.

NOTE: The certificate can take up to 48 hours to activate. If you see a message saying "Pending..." note that it is not an error, you just need to wait for the certificate to be active.
NOTE: Our SSL provider does not allow more than 64 character long domain names. If your domain name is longer than 64 characters, SSL will not be applied and your pages will not work. 
NOTE: In the case that the subdomain is first added to the Subdomains dashboard, and the CNAME record is added to the DNS settings second, the SSL certificate may not activate automatically. This is because our system will immediately start looking for a CNAME record upon adding it to the Subdomain dashboard. If it doesn't find one after a few tries, activation will fail. In that case, we need to activate an SSL certificate manually upon request.