If you use online banking for example. Go to the bank site log in page and see if you get the 'This site is not secure' warning.
If you don't then all is well. Read the posts above for a little more detail. It's not a BT problem.
I think there's a misconception here ... the website isn't any more or less secure because is uses https or http.
What is being flagged up by the browsers is that your connection to the site (through the internet) isn't secure.
So, if your browser is communicating with a website which uses the http protocol, there is the potential for someone to intercept that communication and read its content - this is why online banking, shopping carts and payment portals have been using the https protocol for some time.
If your browser is communicating with a site using https, your communication with the site is encrypted ... so if intercepted, it can't be decyphered.
None of this is new ... it's just that Google (followed by the others) has decided to push for fully secure communications with websites.
If you land on a website which has been hacked and is delivering malware, https won't save you.
As an earlier poster stated, it doesn't actually matter until you log in to a website or service and start to pass private information.
One issue for owners of websites ... implementing https and getting it to work properly can sometimes be tricky. Additionally, some hosting providers charge for the security certificates ... anything from £30 per year to many hundreds.
“What is being flagged up by the browsers is that your connection to the site (through the internet) isn't secure.”
If this is the cause of the problem how do we explain that I can open up all my banking and finance sites (albeit with some of them initially showing the insecure message but then quickly opening the page) while The National Lottery site (also https prefixed) shows the message but refuses point blank to open on Chrome, Firefox and Safari. So far it is the only site I have found affected but then it only came to light a couple of hours ago
The Talk Talk forums are full of posts with similar problems and with many more sites affected than me. Much was made of resetting the router as a cure and was successful for some, with me it at first appeared to have done the trick as the page opened, but inside a minute closed again. A second reset of the router had no effect.
There seems to be no one option to solve the problem coming to light on other forums. At the moment my workaround is to connect via my mobile … but then I’m only fighting one site.
For the record, MacBook Pro, Sierra, BT smart Hub, FTTP … browsers as above.
I'm not sure about it being specifically a BT network issue. I have never come across this problem personally and asking friends who are with BT neither have they. I suppose it might be an idiosyncrasy of the Hub(s), can't say for sure though as I never used them. Always used my own kit and strictly control browser scripts, cookies etc.
Oh dear. This is very simple really.
First, read this article on The Register (a UK IT news site). It says Chrome will start to flag sites using a particular SSL certificate ... so even if they show as https, Chrome will flag them (you can always bypass). In his artical Kieran references a list of sites which will be affected - and the UK National Lottery is on it. They have since fixed the problem - they have changed their certificate provider to DigiCert.
Why are you being told to restart your router? This clears the cache, so visits to sites actually go and get the information from the site's server, rather than using a copy in the cache. If the problem is with the cache, the restart will fix it. Most of these problems have nothiong to do with the cache or the router - it's just the tech support people either don't know enough (most are just call centre staff, not technicians), or they hope you'll go away so they can close the call and log a sucess.
The difference betwen phone and PC behavior is down to the applications being different on the two devices.
So, to summarise ... https is just the secure connection between your browser and a website. For this to work, the website owner must install and configure an SSL Certificate.
The warnings are generated entirely by the browser, regardless of your broadband provider.
If you are not transfering confidential information, you can ignore the warning - all browsers (including Chrome) can be set to allow specific sites.
The reference to lots of threads on forums shows this change is being poorly communicated, and lots of call centre staff are no better informed than their clients.
As a side issue, if you want decent service and support, don't use one of the large broadband providers. They build their offering based on cost ... they can afford all the cheap offers only by providing cheap support. **Edited by Mod**