Filter Blogs expand_more
Blog add
Authors add
Solutions add
4 Results for '.com'
Blog

Entrust Takes Top Honors amongst Information Security Magazine and SearchSecurity.com Readers

By Entrust Datacard
December 02, 2014
Entrust IdentityGuard, was recently named an Information Security Magazine and SearchSecurity.com 2014 Readers’ Choice Award winner for Best Authentication. SearchSecurity.com said Entrust IdentityGuard is a truly converged solution for multifactor authentication deployment and makes the authentication experience seamless for organizations.
Blog

How Browser Security Indicators Can Protect You from Phishing

By Kirk Hall
June 08, 2017
Using an EV certificate to encrypt and identity a website like paypal.com prevents scammers from duplicating the PayPal site for a different domain and making it all look the same - the real and the fake login pages will have different UIs.
Blog

Welcome To The New Entrust Datacard

By Entrust Datacard
November 04, 2014
Welcome to the new Entrust Datacard. Entrust and Datacard Group are combining decades of experience to provide trusted identities and secure transactions under one brand and debuted a new company name, logo and corporate brand identity. “The world is changing — it’s more connected, more mobile and more empowered than ever,” said Entrust Datacard CEO Todd Wilkinson. “Our new brand and corporate identity is a reflection of this evolution and the changing markets we serve. Visit the new www.entrustdatacard.comnt
Blog

SSL Certificates without Non-FQDNs

By Bruce Morton
February 21, 2013
Over the years, publicly-trusted CAs have issued SSL certificates with domain names of different types. The most common is the Fully Qualified Domain Name (FQDN). This is a certificate that has been issued with a name registered with an entity that manages a top-level domain (TLD), for example server1.domain.com. The differentiating characteristic about an FQDN is that it is unique. There is one controller of domain.com and that controller determines who can have any name under that root, such as server1.domain.com
Page 1 of 1