Chat with us, powered by LiveChat Being Secure | WRIS Web Services

Being Secure


Being Secure


You've probably heard of SSL. It stands for "Secure Sockets Layer." By definition, SSL is "a secure protocol developed for sending information securely over the Internet." Think of it this way...without SSL in place on a website, it's like having a private conversation with someone in the middle of Progressive Field. During an Indians game. Meaning anyone could hear it. But with SSL, that conversation takes place in a locked room with just you and the person you are talking to...much more private.

In the past, SSL was mainly used for websites with ecommerce functionality. Customers aren't going to provide credit card and payment information online without the assurance that their information is going to be protected and only used for the intended purpose. Flash forward to today, though, and SSL is needed for much more than that. 

Actually, since 2014, Google has been giving sites with an SSL in place a ranking boost. Not necessarily a huge one, but hey...a boost is a boost. Then things got serious when they started actually flagging websites without SSL as being 'not secure' with the use of an exclamation point icon. Go to your site right now and see how it displays. Do you see this icon?

Then Google is flagging your site as not being secure.

Next up? The Scarlet A of website identifiers, the actual words "Not Secure" clearly placed before your website URL. Nobody wants that. And this will start occurring in July 2018. (Yes, that's next month!)

While it's true that this is a Google mandate (so it will only take affect in Chrome), Chrome currently accounts for more than 50% of browser use worldwide. You don't want to mess around with that.

So even if you don't think you need SSL, here are the benefits:

  • Assurance to your site visitors that their information is protected.
  • Possibly a little boost in ranking from Google.
  • No angry messages next to your website address.

Have questions? There's additional information here. Ready to move forward? Give us a call at 440.600.2495 or use our online form to get in touch and we'll help you navigate the process so that you can feel secure in your decision.

Related Blogs


When No Framework is Somehow Better Than YOUR Framework
Part 3: When No Framework is Somehow Better Than YOUR Framework - a reality check for every ego-fueled “framework” cobbled together in 2014. From thousand-line utility files to hardcoded business logic, these aren’t frameworks—they’re landmines. Here’s how we untangle the spaghetti and give ColdFusion apps the structure they should’ve had all along.
When No Framework is Somehow Better Than YOUR Framework
It's Not Me, It's You: Breaking Up with Bad ColdFusion Code
Next up: It’s Not Me, It’s You: Breaking Up with Bad ColdFusion Code — a brutally honest breakup letter to the spaghetti logic, inline SQL, and 2010-era sins that haunt your .cfm pages. When “just upgrading ColdFusion” turns into a full-blown intervention, we bring the tough love (and cfqueryparams) needed to modernize your stack—and reclaim your sanity.
It's Not Me, It's You: Breaking Up with Bad ColdFusion Code
From the Desk of your Grumpy Dev: Cleaning Up After a One-Man Wrecking Crew
A blog series from the trenches of legacy CFML, written by grumpy ColdFusion devs armed with debugger wands, Diet Coke, and decades of battle scars. We dive into the messes—so you don’t have to. First up: From the Desk of Your Grumpy Dev: Cleaning Up After a One-Man Wrecking Crew — a tale of duct tape code, missing documentation, and the digital equivalent of a trail of breadcrumbs leading into chaos.
From the Desk of your Grumpy Dev: Cleaning Up After a One-Man Wrecking Crew

Let's get to work on something great!


Get in Touch