Stay updated with new articles.

Enter your email address to subscribe and receive notifications of new articles by email.


The race towards HTTPS secure web browsing

The race towards HTTPS secure web browsing

There’s a lot of movement lately that the next big thing that will come to search engines like, Google and Bing are heading towards websites using a HTTPS secure connection.
If you haven’t noticed. We are quickly heading towards  “secure by default” web browsing.
For instance, early this year. Websites that are in the top quarter percent of Alexa were all forcing the HTTP scheme.
That number has been gradually increasing since then.

Percentage of websites using https connection

Now that is a large increase among the BIG players on the web.
But the trend is clear and increasing rapidly.
It’s clear that HTTPS is being forced at an incredible rate.
Website not secured
The “shaming” of websites serving login or payment forms insecurely began with Chrome the first of the year.
But the reason for this post is because life is going to start getting much harder for websites that don’t use HTTPS.

Look at the example below.
As you can see, that even some of the heavyweights don’t use it yet.
But browsers are letting web surfers know, that the website isn’t secure.

How to secure your website


An insecure form means that the contents of the search may be intercepted and conceivably, that could contain data that the user would prefer didn’t fall into the hands of someone listening in on the connection.
Maybe with a website like ESPN, most surfers wouldn’t be alarmed.
However, if you think about it.  If a website isn’t sure. Maybe they could have fields where you enter information.
It may not be credit card information. But, it could contain forms that have information about you. An insecure connection where someone could be listening in and gathering your info.
Like, name, address, phone number, etc.

Major search engines like Google, Bing and others are recognizing this pattern.

We know secure pages are secure because the browser tells us so. We know non-secure pages are not secure because the browser doesn’t tell us that they’re secure. Make sense?
It’s clear to me. That the internet is quickly moving away from insecure connections.

My suggestion.
It would be painful to wake up one day and see that Google has run an update and your website falls off in the rankings. Only to find that websites with the HTTPS secure connection have risen to the top of the SERPs.
I have no idea when this will happen. But, I see it coming in the near future.

If you’re not on top of it. When it does happen.
You’ll remember reading this.

Jeff Laycock
Kentucky Indiana Web Group



ICANN Verification

 ICANN Verification

I wanted to share a story with you, that happened to me several years ago.

Several years ago. I was notified by Godaddy, my domain provider, that my ICANN Verification was due.
Nothing major, I thought at the time.
It was just wanting me to go in and verify our contact information.

I was a little suspicious of the email.
I have never gotten such an email from Godaddy or ICANN before on the issue.
Especially since all contact info was correct.

As a result, we were on page NUMBER ONE in graphic design and web design, in Google’s search results.
As a result, I didn’t verify, like I should’ve.
My domain was shut down until I verified and just the hour or so, it was off.
Our traffic took a nose dive and lord behold. We weren’t on the very first page.
As a result, we lost about 3,500 visitors a day, to a tenth of that.

So, take it from me.
You get a Verification from your domain provider or ICANN.
Make sure, you verify the information.

It could be costly, putting such a simple, 30-minute task to the side.