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

Its 2017 for Gods sake, why is our http://www website showing up as not secure??? Who cares, why are you slandering us and blocking access?

  • 4 replies
  • 2 have this problem
  • 1 view
  • Last reply by cor-el

more options

http:// websites are blocked for not having security certificate.

http:// websites are blocked for not having security certificate.

Chosen solution

HTTP websites aren't blocked in any way. They are merely flagged especially in case there is a login form to an insecure URL, but you should still be able to visit such a website without any problems.

The page links you posted have a meta refresh tag that redirects to a server that doesn't have a certificate installed. view-source:http://shirtsquirts.com/

<meta HTTP-EQUIV="REFRESH" content="5; url=https://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs">
<link rel="stylesheet" href="style.css" type="text/css" media="screen" />

The HTTP version redirects as well and ends up with domainspricedright.

So in this case there is a lot wrong that needs to be fixed.

Read this answer in context 👍 0

All Replies (4)

more options
more options

Chosen Solution

HTTP websites aren't blocked in any way. They are merely flagged especially in case there is a login form to an insecure URL, but you should still be able to visit such a website without any problems.

The page links you posted have a meta refresh tag that redirects to a server that doesn't have a certificate installed. view-source:http://shirtsquirts.com/

<meta HTTP-EQUIV="REFRESH" content="5; url=https://www.securepaynet.net/default.aspx?prog%5Fid=inmarvs">
<link rel="stylesheet" href="style.css" type="text/css" media="screen" />

The HTTP version redirects as well and ends up with domainspricedright.

So in this case there is a lot wrong that needs to be fixed.

more options

OMG I am so sorry. Long day(s). Just removed the redirect I had forgotten about and everything is normal. Thank You for your time. :-)

more options

You're welcome and thanks for reporting that you fixed this.