Printable View
H,
I notice that there is a "Not secure" warning when I publish a site to Google, does not appear in Firefox, or Edge. How can I avoid this (or make my sites more secure).
I have tried FTPS and SFTP in the "Other web hostings" dialogue, I think it was the SFTP that worked OK.
Is this a Xara issue, or do I have to talk to myhosting company 1&1?
Kind regards
Martin
Is your site using SSL (i.e, its address has https://, indicating a secure protocol)?
Acorn
An SSL certificate is something you will have to take care of with your hosting service. This will change your URL to be "https" rather than "http", and make your site "secure". If you don't have credit card information being entered literally on your site, and don't have a "login" area like this site, you generally don't need an SSL certificate. The one exception is that the BBB require you to IF you have a contact form, so if you want BBB accreditation, you'll either need to get rid of any contact forms, or get an SSL Certificate. They can run up to about $60.00 a year depending on the hosting provider.
Many thanks for your advice. I tend to just produce simple sites advertising our dance club and fishing club etc. I am concerned that someone using Google will contact me to ask why my site is advertised as insecure.
Regards
Martin
I am with 1&1 and found I had to purchase SSL certificates through them, for my sites to recognise any SSL certificate: https://www.ionos.co.uk/security/ssl...s3vhnrv9tagyw2. You can buy an unlimited number for around £100. Regards Gary
It seems an exploitation of us where those who do not understand what to do get conned into paying.
My service provider automatically add SSL certificates; one can try https://www.sslforfree.com/ or https://www.cloudflare.com/en-gb/ssl/, both are free.
Acorn
Many thanks for all your kind replies,
As there are no transactions on my personal sites (mainy info about several clubs and bloggy sorts of stuff) I will leave it as it is.
I agree it is an exploitation, I notice that 1&1 are quite good at this, for example, slipping in additional costs to support older versions of PHP!
Regards
Martin