Namecheap.com enjoyed a rare opportunity to chat with Symantec VP Rob Hoblit and hear his thoughts on the new report's outcomes.
The world of computer viruses has changed drastically over the last 25 or so years. In the early days, internet users were very naïve towards email attachments, contributing to the alarming speed that viruses could spread across the globe.
These days, viruses very rarely land in our inboxes due to preconfigured firewalls and strict measures from the likes of Gmail and Outlook.
Questions and concerns often arise during the validation of SSL certificates. Each SSL type requires a different level of authentication.
In this post, we’ll share detailed authentication and verification guidelines regarding Symantec Extended Validation (EV) SSL certificates, to help you understand and appreciate them better.
We believe that most companies who do business online have been attacked by hackers at least once. Starting April 15, we were faced with a massive Distributed Denial of Service (DDoS) attack.
We discovered the attack when the SSLs Site Seal checking system notified us that it was unable to ping SSLs.com.
We feel immensely proud when we consider all the wonderful sites out there that are protected by our SSL certificates, but obviously SSL certificates are just one part of the cyber security puzzle.
So we thought we’d try and give our customers a helpful overview of the wider picture. There’s some great in-depth guides out there already, but we wanted to create something slightly different.
Since Google announced that using HTTPS encryption for all website pages is an important factor in SEO ranking, demand for SSL certificates to enable website security has increased even more.
Many webmasters and website owners remain confused about what actions are required to move their websites from HTTP to HTTPS without difficulty.
In a previous blog post we reported that Google and Microsoft are encouraging Certification Authorities (CAs) to depreciate the vulnerable and outdated SHA-1 cryptographic algorithm and move to the stronger SHA-2.
Starting January 1, 2016, CAs must not issue any new SSL certificates using the SHA-1 hash algorithm. CAs may continue to sign certificates to verify OCSP responses using SHA-1 until January 1, 2017. This year also began with an important update.