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

    Can a password box condition be found in the source code if I restrict it from sending notificaiton emails?

    Asked by Deiopei on June 12, 2012 at 12:21 PM

    Hi. I know the question about passowrd protection has been asked many times over. My question is slightly different. And it's not too urgent. I just would like some verification.


    Example - I added a passoword to my form and added a condition of if "Password" does not equal "123456" then email will not be sent.


    It looks as if that condition doesn't show up in the source code so it may be a bit safer. Can you verify?


  • Profile Image

    Answered by jeanettebmz on June 12, 2012 at 02:00 PM

    Actually conditions should work if you dowload the source code.

    At any rate, please check this thread that I just answered regarding to password forms



  • Profile Image

    Answered by Deiopei on June 12, 2012 at 02:55 PM

    Ok. I was looking at this thread


    It seems that a form that tries to create a username and password to "register" people is considered phishing. I'm not trying to register people. I'm trying to prevent random third-party scammers from using the form. Captcha features only prevent bots from auto-filling the form.

    I am just trying to prevent a password from showing up in the source code like so many have considered. That should be fine to do, right?

  • Profile Image

    Answered by jeanettebmz on June 12, 2012 at 04:01 PM

    A form can be considered suspicious of phishing whenever contains a password field that would be used as identity theft. However,  no matter if it is inttended to register people or prevent scammers, this practice is not allowed by our Terms of Use

    We know most of our users don't do phishing, however, there are many ones that actually do. That is why we apply that general rule.

    Like I said, you can embed the source code of your form instead.

    In order for you to prevent people to see the password in the source code, you can disable the right click of your page. Of course, this is a workaround and talented users might find the way to see it anyways.

    Best regards



  • Profile Image

    Answered by Deiopei on June 12, 2012 at 04:11 PM

    Thank you for your response. I think a single code I make for everyone to use could not be consideredidentity theft. That's what everyone else seems to have to use.  Maybe you should look at my form and tell me if it's ok.


    Also, I can't embed the source code because I'm made the site on google sites. Sorry if I'm being persistant, but I'm just trying to make sure my form doesn't get blacklisted.

    Thank again, for all your help.

  • Profile Image

    Answered by jeanettebmz on June 12, 2012 at 04:59 PM

    You are correct. A single code is not considered phishing.

    However, I just took a look into your site, and in order to prevent your form being suspended by automated system (remember it is automated) I would strongly recommend you to change the text "access code" to something like  "Enter the code provided to you" or something similar . This is to give the impression the code is not actually a password, but something you provide to prevent scammers.