Who When Where

Hello,

Not sure if its my settings or if something has changed but the website is today flagging up as "Not secure".

Don't know if this will cause issues with some folks and their internet protection or if its just me.

Just wanted to mention it in case it was something else that may need attention.

Cheers

Dan

Mines got the little padlock. Using Chrome.

Cheers Templ4r, might be something in my settings in that case or the virus software I'm using. I'm getting the same on my phone and laptop.

Not to worry, I'll have a fiddle with my settings.

Cheers

Dan

Thanks for alerting us to this.

On Firefox mine is showing with a padlock but on Chrome is telling me it's not secure.

We'll investigate.

My Firefox was showing insecure, then I changed URL from HTTP to HTTPS and it fixed it. Perhaps you are using wrong protocol.
I also get Unsecure in Safari on my iPad, I'll try same trick and report back, see if it cures it. Safari doesn't show whether it is HTTP or HTTPS, it is hidden!

NB I thought a site should be either HTTP or HTTPS, not both!

Hi Mick,

I have now just done he same as you. I have manually typed the addess with https instead of http and it is showing as secure.

I now have 2 links saved, one for each, one secure and one non-secure.

I am the same as you and did not think a site could have both as its the security certificate of the site that sends the secure message out.

I am using Chrome btw.

Cheers

Dan

We think we have fixed this now, and having tested it ourselves it seems to redirect to the secure site automatically - in other words, if you type in "http://www.whowhenwheregenealogy.org.uk" you will be taken automatically to the https site.

Well done to all involved for fixing this.

I have checked on my phone and laptop and it is coming up as secure.

Cheers

Dan

Thanks Peter,
It does work! My iPad Safari no longer showing ‘not secure’

PS Just seen your message, and yes, HTTP now redirects to HTTPS on Firfox

I found the same with Safari highlighting Not Secure. Changing to https has sorted it. Thanks.