SiteLock is the app that BlueHost basically insists you buy—and which you should buy. It will protect your website from bad people. Once you assent to purchasing SiteLock, the program does some automatic setup. But this is not all you have to do. You will get an email asking you to finish the SiteLock setup. It looks something like this:
I followed these instructions and did all they asked but when I went to the SiteLock site, I was still getting this notice: “Your website is not fully protected. Click here to complete your setup.”
SiteLock: Your Website Is Not Fully Protected
So I clicked on the “here” and tried to work my way through the items listed as needing set up.
Step 1: Verify your domain
This is only required if you use an SSL certificate, which I do not have right now.
Step 2: Change you’re A Record(s) and CNAME in your DNS records
SiteLock could tell that my domain is hosted by BlueHost and gave me instructions specific to BlueHost. Unfortunately, the link to the instructions was broken. I contacted SiteLock and Dexter from SiteLock got back to me quickly and promised to fix the broken link, which was done. Dexter also offered to set up my site for me, but I declined as I wanted to try it for myself so I would know what was going on.
The instructions SiteLock provided were still a little unclear, but I managed to do it right. I know this because Dexter had to check for me and fix a bug on their end (something got hung up somewhere and I was still getting the “website not fully protected” message).
The instructions SiteLock give you begin with this:
1. Log in to your cPanel.
2. Under the Domains section, click “DNS Zone Editor.”
When you click DNS Zone Editor, you get this screen (with the real data blotted out or changed):
To help you understand what information from your SiteLock site goes in the DNS Zone editor, I have created some infographics which follow
In the SiteLock site, you will see the following information. I have labeled the pieces of information with alphabetic markers.
Steps 3 and 4 in the SiteLock instructions say:
3. Under Zone File Records select the appropriate domain form the dropdown list.
4. Click edit to the right of the root A record (indicated by the @ symbol) and input the first TrueShield IP provided.
So the following infographic shows you where to put the information you saw in the Figure 7 for Steps 3 and 4.
Then SiteLock instruction Step 5 says:
5. For the second TrueShield IP, use the “Add DNS Record” section to add an A record with the ‘Host Record’ field set to “@” and the ‘Points To’ field set to the second TrueShield IP then hit ‘Add Record.’
This infographic shows you where to put the information from Figure 7 into the DNS editor.
Finally SiteLock Instructions Step 6 says:
6. Locate the ‘www’ CNAME record (NOTE: this may be set as an A record. If so, edit the record to be a CNAME) and edit ‘Points To’ to input the TrueShield CNAME (i.e: xxxxxx.sitelockcdn.net) then save.
This infogaphic shows you where to put the SiteLock information from Figure 7 into the DNS editor.
Then when you click save in the DNS Zone Editor, this should link up SiteLock with your site and protect your site.
As I said, this did not actually work for me. I was still getting the error in Figure 2. This is when Dexter had to do some behind the scenes work at SiteLock.
Step 3: Install the SiteLock Trust Seal
The final SiteLock step is to install the SiteLock Trust Seal. I went through this process, but I still for some reason do not have the trust seal. I have informed SiteLock and will update this when they get back to me.