"Not Secure" warnings

  • Profile Image
    Asked on August 20, 2017 at 10:24 AM

    I found this post, so will have some great things to research and impliment.


    My question though: is having all of my forms built through JotForm enough to satisfy the requirements in this recent article? 


    It states: ... Chrome (version 62) will show a “NOT SECURE” warning. In short, in October 2017, Google Chrome will start labeling any site that asks for you to input anything into a form while on HTTP as not secure. This can be a login form, a email form, or really any type of form.

    I'm not wanting to go in and change all of the code on the sites I have built, and can be pretty sure my clients wouldn't pay for a SSL certificate...


    And an upcoming event usually has 100-200 registrations/payments made [through Paypal] and I need to know how to prevent issues before they happen. The form is presently not live on the page, but is linked below. [http://nwodga.org/annual_dairy_goat_conference.html]


  • Profile Image
    Answered on August 20, 2017 at 10:53 AM


    The article you shared states that the warning will show up if the website is NOT on HTTPS. 

    Please note that all forms and embed codes hosted in JotForm are by default set to HTTPS. If you open your form's direct link, you can see it uses SSL. 


    I checked the link of your website but I can't open it. 


    Please note that if your website is NOT in HTTPS, then it is possible that the warning message you are referring to on the article may display. The form itself and the embed code is in HTTPS/SSL, however, if you embed it on a website that is NOT HTTPS, then I am not sure how Google will handle your website. It's best to have your website SSL enabled, or you can just share the form's direct link to your users if you want them to view it in HTTPS. 

    I hope that helps. 

  • Profile Image
    Answered on August 20, 2017 at 01:29 PM

    Thanks! (Not sure why the site won't display.)
    That clarifies things a bit, so will check on the https issue with the site as well.