yeah. Oh, this is not my main domain. So if you put in a billing information, you can turn on this certificate manager. You don't have to the basic the basic certificate is fine. But basically what this total TLS is going to do is it's a better approach to make sure that all the things in your website are appropriately covered by SSL certificates, whether it's, you know, different subdomains or whatnot. You do have to set up a billing, putting your card for that so you can buy the free product to turn on Advanced Certificate manager. Then you can add this. It looks like Deb's cat stepped on the keyboard and entered about 18,000 threes in the chat which is awesome. Okay, so always use HTTPS that needs to be on like I want to always make sure all the traffic is coming at my website and HTTPS. So for some reason, there's a link out there that's just HTTP. It's going to fix that so that it comes in at HTTPS. The next thing we're going to turn on here is this HS T S, the HTTP Strict Transport Security. Essentially what this does is it helps to protect from a kind of attack called a man in the middle attack. And we're just going to click Enable here. You have to read and acknowledge that bad things can happen if you use this and essentially it boils down to this. If at some point in the future, your site stops having an SSL certificate for some reason then nobody is gonna be able to view your site at all because this particular feature stops any traffic from going to your website that's not protected under an SSL certificate. So I understand that and I hit Next. And basically, like I say, in the things here, toggle on all options, and select the six month recommended option for here. We just toggle all of these things on and we are protected from that man in the middle attack. Done. We're going to set leave the default setting here for TLS 1.0. There are others but some older browsers might not support the older versions of TLS. We'll leave it at one that's the default app and the rest of the settings we just turn on these are other. You can get really technical, you can read the help docs basically they prevent you from they prevent various types of attacks, or hacks. from happening to your website. You can make TLS 1.3 available for those browsers that support it. It's going to automatically rewrite your HTTPS for you. And you can turn on this is a you know this is kind of a you probably want to do this. If some if if somehow a certificate gets issued for this domain controller under Cloudflare. By some other certificate authority, you get an email about that. So maybe somebody is trying to spoof for some reason your domain name and they're trying to register a certificate. This would let you know that's going to happen. Monitor you're asking if you can't get to the site. How would you fix it? You just go in here and turn this off in Cloudflare. But if you're using Cloudflare for SSL, you're not gonna have a problem there. They just want you to realize that if for some reason you stop using Cloudflare SSL and your own self generated whatever SSL certificates stops working, nobody's gonna be able to get to your site with this setting enabled. And ultimately, it's a good thing because it's going to keep your site protected from a an attack that could be used. Okay, so that covers basically everything. There's, there are other options here where you can create certificates, you can set up origin. So these are all very advanced things, setting up custom host names. We're not going to deal with any of that today. We're just locking down our client website with the free SSL and TLS features of Cloudflare. Okay, let's move down to the next section. This is a big portion of the Cloudflare settings. And it has to do with security. So this is really where a lot of the questions and interest comes around Cloudflare or some of these web application firewall rules. And what I'll tell you is this is one of those things that if you don't know what you're doing, you can mess some stuff up. And we actually with some of the rules that I'd given in the past, we realized that it was conflicting with some things like Stripe and a gravity form callback. And you need to understand how this works enough in order to troubleshoot those things. I'm going to step you through a little bit of that here, but this is one of those areas where you know proceed at your own risk. Because within with a web application firewall rule, you are telling certain kinds of traffic, how it's going to behave when it tries to get to your site. So you could break for example, uptime monitors or stripe connections or things like that. That need to just have a clear path to the site. But if you put a firewall rule in place, you're preventing it from doing that. So you just have to know what you're doing in this case. So I'm gonna explain as best I can here, but there's no way in a webinar like this I can exhaustively explain all these things, nor probably could I at all, but here we go. So Cloudflare gives you five for at the free level five WAF rules that you can use for each domain. Unfortunately, they have to be applied for each domain. So you have all these settings you have to do individually for every domain. Once you get used to adding in the domain it goes pretty quickly but all these things have to be done per domain. There's not a way to like multiple select everything and check them all, unfortunately, but basically what you do you create a firewall rule you paste these rules in the Edit expression box, and magical things happen. Now, there are some things here that I'll get to in a minute called these a s NS these as numbers. And like these numbers represent certain internet properties like Google Microsoft, I think this one is up. Yeah, Google Bing. And this one is something I will look these up in a minute, but their numbers so rather than having to know the range of IP addresses that a Google bot uses to scan your into index your site, you can use this ASN which says all of Google that identifies itself, this ASN can pass through to the site. So let's get one of these in and I'll show you how to check what these numbers are and what they mean. So what we're gonna do is we're gonna go under security and WAF or the web application firewall, and we're going to create a firewall rule now if this is what we call for you, if for you this is what we call it. iThemes Training a duct tape moment, meaning I need to wrap my head and duct tape so it doesn't explode. Just don't do this. Like you don't have to add these. This is an extra level of protection that, you know, it certainly helps, but there's plenty you know, just adding Cloudflare is going to filter out a lot of malicious traffic as it is. This takes it to the next level. But you need to know what you're doing. Okay, is that fair? Okay, so, the way I've got the setup, this is the name. I'm calling it of the rule, and this is the action the rule is going to accomplish. This is the content of the rule itself. Okay, so we're going to create a new rule. We're going to call this good bots. So these are bots that we want to go through our site to pass through Cloudflare to our site with no problems like my like Google and Bing and things like that. So these are good bots. And we're gonna copy this expression. And I'm gonna go down now, it has an Expression Builder where you can build these out a little wizard and do ands and ors and stack up your own rules. But you can add this whole thing right here by simply clicking Edit expression and pasting that in. And then what is the action allow? So we're going to let any traffic that meets the criteria of this rule through to our site with no problem whatsoever. And I'm going to hit Deploy firewall rule and this one is now working so allow good bots and you'll start to see as this rule is in place, you'll start to see some traffic happening and how many times this rule was accessed. Now Sue's asking if you don't add any rules will Google get through? Yes. Because you're there's nothing you're doing to prevent it. Yeah. But you know, if you for example, instead of having this allow you put block or give it a manage challenge, then the Googlebot won't pass that. So you have to specifically in my in this case, I'm saying specifically, allow the these are the bots that I want to get through to my site. But if you don't have this rule in place, the traffic passes through because there's no rule to prevent it. Does that make sense? You're not doing anything. Okay. So what do these numbers mean? There's a couple of them. Well, this is a great resource site called IP info.io. It gives you a lock, you can type in an IP address here. Oh, look, there's me. Et cetera. Okay. So you can also there's a tool here. So if we want to know what the A at this ASN is, I can go straight to that page. And let's just look up this first. 115169 Let's just change this. If we went to ASL 15169 Who is that? Oh, that's Google. This is the primary Google bot. And that's how we can we can look this up. So I've got a bunch of things here. So what is at 75? Oops, I did something wrong. Microsoft that's being how about 714?