Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox saying bing is not secure

  • 4 replies
  • 4 have this problem
  • 22 views
  • Last reply by cor-el

more options

just recently (about an hour before this post) firefox started saying that "An error occurred during a connection to www.bing.com. Invalid OCSP signing certificate in OCSP response" even though it was working perfectly fine before that.

i have tested this on multiple computers some without anti-virus, and of different OS (windows 7, 10, mac snow leopard), and on multiple networks ( comcast, AT&T, including a mobile hotspot) and none of them work.

i have been getting the same error message on every thing i try and really have no idea with it and if its a problem with bing, or firefox.

just recently (about an hour before this post) firefox started saying that "An error occurred during a connection to www.bing.com. Invalid OCSP signing certificate in OCSP response" even though it was working perfectly fine before that. i have tested this on multiple computers some without anti-virus, and of different OS (windows 7, 10, mac snow leopard), and on multiple networks ( comcast, AT&T, including a mobile hotspot) and none of them work. i have been getting the same error message on every thing i try and really have no idea with it and if its a problem with bing, or firefox.

All Replies (4)

more options

screen shot didnt upload for some reason

more options

I am intermittently having the same problem in the past hour not only with Bing but several others such as Flickr. What I do is either click try again on the error page which then loads the website or home or click on the bookmark again.

Modified by new_aged2perfection

more options

My error is the same as the screenshot above.

Modified by new_aged2perfection

more options

If you get the SEC_ERROR_OCSP_INVALID_SIGNING_CERT error message then this is a problem with Microsoft servers that are sending a cached OCSP Staplingresponse that is signed with an expired certificate.

Microsoft needs to reboot/repair the servers that have cached this expired certificate that is used to sign the OCSP Stapling response. You should no longer experience this issue once the server that you access has been fixed. Hopefully they will fix this quickly on affected servers.


As a workaround you can temporarily toggle this pref to false on the about:config page to see if disabling OCSP Stapling works for you.

  • security.ssl.enable_ocsp_stapling = false

You can open the about:config page: via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

It is best to reset this pref via the right-click context menu to true once you are done with accessing an affected website since this is a security feature.

See also: