Quick Validation SSL certificates ensure that information is encrypted between parties. The owner of the certificate is verified via an email to a contact listed in the domain’s WHOIS information. This helps ensure that the certificate is valid.

A Quick Validation certificate ensures that your data is transferred with the secure encryption technology.

Full Validation SSL certificates also encrypt data sent between two parties with the same encryption technology.
In addition to verifying an email to the WHOIS contacts, Full Validation certificates verify that the certificate owner is a legal entity. Verifiable legal entities can be either a business or an individual. Full validation certificates therefore help ensure that data is securely sent over the Internet to a trusted entity.

The Secure Sockets Layer (SSL) protocol has become the universal standard on the Web for authenticating sites and for encrypting communications between users and Web servers. Because SSL is built into all major browsers and Web server s, simply installing a digital certificate or Server ID enables SSL capabilities.

SSL server authentication allows users to confirm a Web server's identity. SSL-enabled client software, such as a Web browser, can automatically check that a server's certificate and public ID are valid and have been issued by a certificate authority (CA) — such as VeriSign — listed in the client software's list of trusted CAs. SSL server authentication is vital for secure e-commerce transactions.

An encrypted SSL connection requires all information sent between a client and a server to be encrypted by the sending software and decrypted by the receiving software, protecting private information from interception over the Internet. In addition, all data sent over an encrypted SSL connection is protected with a mechanism for detecting tampering — that is, for automatically determining whether the data has been altered in transit. This means that users can confidently send private data, such as credit card numbers, to a website, trusting that SSL keeps it private and confidential.

A customer contacts your site and accesses a secured URL: a page secured by a Server ID (indicated by a URL that begins with "https:" instead of just "http:" or by a message from the browser).

Your server responds, automatically sending the customer your site's digital certificate, which authenticates your site.

Your customer's Web browser generates a unique "session key" (like a code) to encrypt all communications with the site.

The user's browser encrypts the session key with your site's public key so only your site can read the session key.
Depending on the browser, the user may see a key icon becoming whole or a padlock closing, indicating that the session is secure.

A secure session is now established--all communications will be encrypted and can only be decrypted by the two parties in the session. It all takes only seconds and requires no action by the user.