What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.

  • Profile Image

    Why does Chrome show a non-secure alert when redirecting to my thank-you page after form submission?

    Asked by LeslieDee on July 25, 2016 at 12:56 PM

    I received an alert from a customer who submitted this form: https://form.jotform.com/61035144538148 saying that he got a "non-secure" alert from Chrome when he clicked submit. 

    I was able to recreate the same alert in a private window: 

    It looks as though the thank you page URL is what is showing as non-secure, and Chrome doesn't even enable the visitor to override and go to the page anyway. I don't know why this is since the external page URL have embedded in the Thank You preferences for all my forms have the  https:// prefix the pages on my site are definitely secure. 

    Can you please look into this? I am concerned we may lose business as a result of this issue. 

    Page URL:

  • Profile Image
    JotForm Support

    Answered by david on July 25, 2016 at 01:16 PM

    As far as I can tell, your page does not have an SSL certificate.  When you attempt to load your page from an https:// link, the security error shows that you do not have a current SSL certificate.  This is true when loading your thank you page.

    For example, if you load your page from this URL, you will get the same error:


    However, if you load it from the non-https link, you will not:


    This is the same for your thank you page.  Change the URL from https to http and the error should no longer be present.