The website may try to fallback to TLS 1.0 in a way that is no longer allowed in current releases or may be using a deprecated cipher suite. You can open the <b>about:config</b> page via the location/address bar and use its search bar to locate this pref: *security.tls.insecure_fallback_hosts You can double-click the line to modify the pref and add the full domain (rpsconline.rajasthan.gov.in) to the value of this pref. If there are already websites (domains) in this list then add a comma and the new domain (no spaces). There should only be domains separated by a comma in the Value column (example.com,www.example.com). If this helps then you can contact this website and ask them to look into this and update their security. ---- *https://developer.mozilla.org/en-US/Firefox/Releases/36/Site_Compatibility#Security *https://developer.mozilla.org/en-US/Firefox/Releases/37/Site_Compatibility#Security *https://developer.mozilla.org/en-US/Firefox/Releases/38/Site_Compatibility#Security

It's true, that website needs a lot of work on its security configuration. If you look at this analysis, it's pretty bad: https://www.ssllabs.com/ssltest/analyze.html?d=rpsconline.rajasthan.gov.in So is your question "How can I convince the government to fix its server?" or "How can I continue to use this not-so-secure site that maybe I should not trust until they do?"