Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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

Is it safe to send credit card information over a page which has mixed content, with the mixed content blocked?

  • 3 replies
  • 2 have this problem
  • 1 view
  • Last reply by MSi007

more options

I would be making a credit card payment over a web page that has the "mixed content blocked" warning on (the little padlock with a yellow triangle ontop of it). Is it safe to do so?

I would be making a credit card payment over a web page that has the "mixed content blocked" warning on (the little padlock with a yellow triangle ontop of it). Is it safe to do so?

All Replies (3)

more options

No, that would not be safe. An attacker can replace the HTTP content on the page you're visiting in order to steal your credentials, take over your account, acquire sensitive data about you, or attempt to install malware on your computer.

Please, take a look at this article : https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox

more options

You can try whether Tracking Protection can block this unsafe content. Tracking Protection is enabled by default in a Private Browsing mode window.

Is this error present on the pages where you login and where you enter your credit card number?

If that is the case then you should contact the website and ask them to look into this matter.

Modified by cor-el

more options

Thanks cor-el, I took a look at the page you suggested, https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content and studied this interesting topic a bit deeper. I displayed the Firefox console on the page that seemed suspicious, and there were lots of warnings about passive mixed content, like this:

Loading mixed (insecure) display content "https://www.xxxx.com/images/xxx/yyyy/zzz.png" on a secure page

I wonder why it warns about https content on an https page - but anyway, all warnings were about images, no active mixed content. What do you think, is it still a good idea not to send sensitive information over this page?