Xolphin News RSS

Google will label HTTP sites as non-secure from January

9 September 2016

Google has announced that it will be marking websites that process sensitive information without HTTPS as “non-secure” in Chrome from January 2017. This is part of Google’s goal to adopt HTTPS as the new standard. What will change, exactly? The security indicators have already been updated in the current version of Chrome, version 53, in order to more ...

Read more

Google changes icons in Chrome

7 September 2016

Research has shown that the current security indicators used by browsers to warn visitors against non-secure websites are not clear enough. Google will therefore introduce new icons for its Chrome browser. Chrome user statistics revealed that visitors did not respond (enough) to warnings. Warning the visitor against unreliable or non-secure websites is pointless if visitors do not understand ...

Read more

WHMCS module now available

29 August 2016

The Xolphin SSL Module for WHMCS makes it easy to sell, request and manage all types and brands of SSL certificates directly from WHMCS. The module is now available free of charge to all Xolphin resellers! What is WHMCS? WHMCS is a commonly used all-in-one tool for client management, invoicing and support for online organisations. WHMCS allows you ...

Read more

Xolphin SOAP API moved and expanded with REST and Comodo API

15 January 2016

To easily request and manage SSL certificates, you can use an API. In addition to the existing SOAP API, we now also offer a REST API and a Comodo API. You can also use webhooks to automatically report application status updates. Advantages of an API The major advantage of an API is that you can use it to order certificates ...

Read more

Browsers impose transition to SHA-2

14 January 2016

Google Chrome has announced that it will stop supporting the hashing algorithm SHA-1. SHA-2 is the follow-up to SHA-1 and set to become the new standard, since SHA-1 certificates are no longer considered to be secure. Google, Microsoft and Mozilla want to block SHA-1 from January 2017 at the latest, although they are considering ...

Read more

point up