Episode Two is all about getting your website to be secure using HTTPS, why this is now a thing, and what you need to know to make sure you get your site changed over, and take care of all the bloody business behind the scenes to make sure it's done properly.

Resources for this Episode

Checklist for http -> https migration by Aleyda Solis READ IT

Darryl: Welcome to my bloody website, the show where we talk all things online. The small and medium businesses owners or executives who still refer to their bloody website. I'm your co-host, Darryl King.

Edmund: And I'm Edmund Pelgen.

Darryl: Okay, welcome to the podcast, welcome out Ed, good to see you. This is episode 2, and we're talking about your site, must be HTTPS and Why.

Edmund:  Now mate, you need to tell me, the average punters not gonna know what the heck is HTTPS, I still have this conversation today and I say HTTPS and say, "what's that?", and I say, " secure certificate do you know what that is?". So why don't you explain it to me? What is it?

Darryl: Okay and I got to be careful we don't go too technical because we don't want to ... the easiest way I explain it to people is when you got to a website and there the little green padlock up in the top of your browser or whatever color padlock it might be for what browser you use. You know that the sites secure and you trust it. It's secure if it's done properly using a secure socket layer or a security certificate. An SSL certificate that is installed for your website and that uses the HTTPS protocol. So websites used to be HTTP, now there's an S on the end of them and that indicates that it's secure, if it's done correctly, so if you see the padlock and it says the word secure, then we know that the site is secure, so that's the basic terms of what it is.

Edmund: Now I actually said that to someone and they said, "well what does that mean?", and so what does that really mean when it's secure?

Darryl: Okay, the data that's ... okay, let's get back and do a 101 website kinda basic things. When you visit a website and you interact with the website, between your computer and where the website lives on the hosted server, there is a transmission of data that things go round, so data could be an image, the logo on a website, and that image is sent to you and it's broken up into things called packets, and there's all sorts of stuff about it ... it's very clever. The browser that you're looking in or the device that you're looking on knows that it should receive this. It's broken up into little packets and it re-compiles them again so that everything looks right when it gets to your machine. That's done or was done for many years over HTTP, which is general protocol. Now the data that's being transmitted is wide open, it's not encrypted, it's visible. Now does that really matter? Well on my webpage where I wax on about we're a wonderful service provider and we do this and we do that, no it doesn't really matter whether that's secure or not. Where it matters of course and where it always mattered was when you were selling stuff.

Edmund: Like in eCommerce?

Darryl:  Yeah eCommerce shop, cause when I put I'm putting in my credit card data right, then I don't want it being transmitted as all the numbers and my expiry date, because then someone could see that, so if it's sent over HTTP, if it's not secure, that data is technically visible. Now, not to the average person, I can't see it, its gone through the ether, but if someone was able to hack into that data stream between you and that connection, and we won't talk about how they might do that, but it's very possible they could do it. They can then take that data out and they can see it and it's in plain text,