Why use certificates for email encryption?
SecureLineTM PKI supports both PGP and S/MIME for message encrypting and decryption and can determine what to use on a per-recipient basis. E.g., you can easily send one message to multiple recipients and have some use PGP, others use S/MIME, and others use other encryption modes, automatically.
Feature | |
---|---|
Meets HIPAA Requirements | ![]() |
S/MIME uses 256-bit AES encryption and SHA-256 hashes | ![]() |
Message encrypted during transmission | ![]() |
TLS: Message delivery uses Opportunistic TLS in addition to PGP or S/MIME encryption | ![]() |
Message encrypted at rest | ![]() |
Message content delivered to recipient INBOX | ![]() |
Encrypt messages in LuxSci WebMail | ![]() |
LuxSci WebMail decrypts and/or verifies signed-only, encrypted-only, and signed and encrypted messages. | ![]() |
Auto-Encrypt all messages sent via SMTP (Encryption Gateway) | ![]() |
Auto-Encrypt selected outbound email based on content | ![]() |
Decrypt messages in LuxSci WebMail | ![]() |
Auto-Decrypt inbound messages (with saved certificate password) | ![]() |
Import externally-generated PGP and S/MIME certificates | ![]() |
Export your PGP and S/MIME certificates | ![]() |
Create new PGP and S/MIME certificates | ![]() |
Securely store the passwords to your Certificates for recovery in case they are forgotten (optional) | ![]() |
Add recipient PGP and S/MIME public keys to your Address Books for use in sending and signature verification | ![]() |
Support both PGP/MIME and PGP/Inline encodings | ![]() |
Add digital signatures for encrypted messages sent via WebMail | ![]() |
Verify digital signatures on inbound email | ![]() |
Compatible with Email Archival | ![]() |
Key Distribution: All users automatically have access to the public S/MIME and PGP keys for all other SecureLineTM users across LuxSci -- no special configuration or sharing is needed. | ![]() |
Import/Export Recipient Public Keys in Bulk or using our API | ![]() |