Website SSL

To have your entire website Secured you need to buy an SSL. Comodo is an inexpensive provider of SSLs. Click here to buy your SSL.

You're fine to buy the cheapest SSL for between $3 to $4 a year:  PositiveSSL:  1 domain / Domain Validation / Basic HTTPS / Comodo SSL

We use Net3000.ca to attach the SSLs to  IA websites.

There is a $50 charge, but your welcome to get your own webmaster to attach it for you too.
Contact Wael Hallag at Info@Net3000.ca, Tel 416 8754044.


SSL For Payment Pages

Your Income Activator website platform includes an SSL security certificate from GoDaddy that you can use on any of your forms where credit card or password information is asked for.

You simply go to any one of your pages in your content editor and click on the advanced settings tab and click on the box beside SSL,  and your page will be secured.





You May Want More Security

Google's Chrome browser is cracking down on websites that collect personal information and do not use what's known as a "secure connection".

Starting now (with the release of Chrome 56) they are going to get even tougher with their warning messages to website visitors.

And they eventually plan on showing a huge red warning message to all website visitors when they detect a "not secure" connection, which could really freak your visitors out and cause your conversion rates to plunge.

Note: A "secure" connection is usually denoted with one of those little green locks that you see next to the URL in the browser, and the URL itself starts with https:// instead of http://.

So, if you are collecting any kind of personal information on your website (including email addresses on your opt-in pages)…
You should seriously consider switching your website over to a secure connection so your visitors aren't potentially freaked out by a warning message from Google Chrome.

Several fairly recent SEO studies have found that websites that use a secure connection actually tend to have higher search engine rankings than websites that don't use a secure connection.

In order to enable a secure connection on your website you'll need to get a special certificate that is issued by a Certificate Authority (CA).

There are dozens of Certificate Authorities that will charge you hundreds, even thousands of dollars for a "secure connection" certificate.

However, last year a non-profit group started a "Let's Encrypt" project where they offer "free, automated, and open Certificate Authority" for your website… and we've started using them on a few of our websites.

So, you may want to check out the free "Let's Encrypt" before you fork over hundreds of dollars for a certificate from someone else.



To help users browse the web safely, Chrome indicates connection security with an icon in the address bar.

Historically, Chrome has not explicitly labeled HTTP connections as non-secure. Beginning in January 2017 (Chrome 56), we’ll mark HTTP pages that collect passwords or credit cards as non-secure, as part of a long-term plan to mark all HTTP sites as non-secure.









Chrome currently indicates HTTP connections with a neutral indicator. This doesn’t reflect the true lack of security for HTTP connections. When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you.

A substantial portion of web traffic has transitioned to HTTPS so far, and HTTPS usage is consistently increasing. We recently hit a milestone with more than half of Chrome desktop page loads now served over HTTPS. In addition, since the time we released our HTTPS report in February, 12 more of the top 100 websites have changed their serving default from HTTP to HTTPS.

Studies show that users do not perceive the lack of a “secure” icon as a warning, but also that users become blind to warnings that occur too frequently. Our plan to label HTTP sites more clearly and accurately as non-secure will take place in gradual steps, based on increasingly stringent criteria. Starting January 2017, Chrome 56 will label HTTP pages with password or credit card form fields as "not secure," given their particularly sensitive nature.

In following releases, we will continue to extend HTTP warnings, for example, by labeling HTTP pages as “not secure” in Incognito mode, where users may have higher expectations of privacy. Eventually, we plan to label all HTTP pages as non-secure, and change the HTTP security indicator to the red triangle that we use for broken HTTPS.

Powered by IncomeActivator.com