Encryption is three locks, not one checkbox.
Most mail is already encrypted somewhere. The question is where it stops being encrypted — and who can read it there.
Email crosses at least three places where it can be read: the wire between mail servers, the message sitting in mailboxes, archives and forwards, and the key that unlocks it. TLS protects only the first, and only if both servers agree to use it. Message encryption — S/MIME, Microsoft Purview Message Encryption, Gmail's encryption or a secure portal — protects the content wherever it travels. Key management decides who can unlock it, including your provider.
XcellHost picks the right lock for each kind of mail and sets it up on the platform you already run — Microsoft 365, Google Workspace or any SMTP server. Policies decide what gets encrypted, customers on Gmail or Yahoo can still read what you send, and keys can live in an HSM partition in Mumbai. Licences, certificates and service come on one INR invoice with GST.
Seven encryption methods. We set up the ones you need.
Pick a method to see what it protects, what the recipient has to do and where it falls short. Facts checked against Microsoft and Google documentation, October 2026.
One outbound message, four decisions.
Every message leaving your organisation passes the same checkpoints. Policies make the decisions, so people don't have to.
DLP or mail-flow rules look for PAN, Aadhaar, account numbers, sensitivity labels, keywords like "confidential" and recipient domains.
Purview DLP · Gmail DLP · Vortex SEG DLPInternal or a partner with S/MIME? Sign and encrypt. A customer on Gmail? Send through the portal. Everyone else? Enforced TLS at minimum.
Policy decides, not the senderThe connection uses TLS 1.2 or later; to domains that publish MTA-STS or that you list, delivery fails rather than drop to plain text.
MTA-STS · DANE · forced TLSWho sent what, encrypted how, opened when — logged for audits, with revocation and expiry where the method supports it.
Audit log · TLS-RPT reportsEncrypt if the other side agrees.
Exchange Online and Gmail both try TLS on every connection by default — and both still send the message unencrypted if the receiving server doesn't support it. Microsoft and Google say so in their documentation.
Partner A: TLS 1.3 · old server: plain textEncrypt, or don't send at all.
Forced-TLS connectors in Exchange Online, Gmail's secure-transport compliance setting for chosen domains, and an MTA-STS policy plus TLS-RPT reports on your own domains so senders must use TLS to reach you.
Old server: bounced, sender told — never plain textWhere Indian businesses need encrypted mail.
Account statements and KYC packs go to customers on any inbox through the portal; internal credit files move with S/MIME.
Auto-encrypt on PAN / account numbersBulk HR mail that carries PAN and salary data, encrypted by rule and readable on a phone.
Portal with one-time codePatient documents to patients and referring doctors, with expiry so links don't live forever.
Expiry & revocation*Signed, encrypted mail that proves which partner sent it and that nothing changed.
S/MIME sign + encryptSupplier mail over enforced TLS; commercial attachments encrypted to named partners.
Forced TLS per partnerMessage encryption with do-not-forward rights, and keys your organisation holds.
Customer-held keysDesigned, switched on and kept working.
Encryption that users bypass or recipients can't open is worse than none. We plan for both.
Which mail carries personal or financial data, who receives it and on which platforms.
01MTA-STS, TLS-RPT and forced-TLS connectors for banks, insurers and key partners.
02Purview Message Encryption templates and branding, or Gmail S/MIME and CSE, configured and tested.
03DLP and mail-flow rules for India data types, tuned in audit mode before they act.
04S/MIME issued, installed and renewed; customer-managed keys in an HSM with a recorded ceremony.
0524×7 NOC and SOC, recipient help in English and Hindi, monthly report of what was encrypted.
06Encryption helps you meet what Indian law and regulators expect.
Encryption is a safeguard, not a certificate of compliance. Here is where it fits.
The Act requires reasonable security safeguards against personal-data breaches. The Rules, notified on 13 November 2025, list encryption, obfuscation, masking or tokenisation among those safeguards, along with access control and logs kept for at least a year. Most of these obligations apply 18 months after notification.
RBI's IT governance and cyber-security directions expect customer data protected in storage and in transit. Encrypted statements and enforced TLS to partners are evidence you can show.
The Cybersecurity and Cyber Resilience Framework covers data protection and encryption for market intermediaries, scaled by category.
Incidents reported within 6 hours and ICT logs kept for 180 days in India — including the mail and encryption logs we retain for you.
Regulators increasingly ask where keys live. A Cloud HSM partition in Mumbai gives you a named Indian facility and your own quorum.
For orientation only, checked October 2026 — not legal advice. Your organisation stays responsible for compliance; confirm current requirements with your counsel, RBI, SEBI, CERT-In or the Data Protection Board.
Three ways in. Mix them as your mail needs.
S/MIME prices are the same as our Email Signing Certificates page; HSM prices match Cloud HSM. New items are indicative.
Turn on what your licence already includes
- Purview Message Encryption templates & branding, or Gmail S/MIME
- Up to 5 DLP / mail-flow rules that encrypt
- Forced-TLS connectors for key partners
- Pilot group, user guide and test report
Any platform, any recipient
- Branded portal — customers open mail with a one-time code
- Auto-encrypt on PAN, Aadhaar, account numbers
- Microsoft 365, Google, Zoho, Zimbra or SMTP
- Vortex SEG secure messaging by Cyberstanc*
- Run 24×7 by XcellHost
Sign and encrypt from Outlook, Apple Mail or Gmail
- Sectigo Basic ₹1,099 · DigiCert Individuals ₹1,199
- DigiCert Business (company in cert) ₹3,299
- Issued, installed and renewed for you
- Same prices as our signing-certificates page
* Indicative — confirm with XcellHost. INR, excluding 18% GST. Microsoft 365 and Google Workspace licences are separate; see Microsoft 365 or Google Workspace. Larger estates: see Email Security Enterprise (on quote).
Build your encryption bundle. See the rupee total.
Monthly, yearly and one-time items are added separately and shown as your first invoice.
Email Encryption · Microsoft 365
Four questions. The right lock for your mail.
Answers stay in your browser. The result names a main method and the one to pair it with.
—
Answer the questions
Your answers are scored against five methods.
Does your edition include it? Check before you buy.
From Microsoft's Purview service description and OME FAQ, and Google's Workspace admin help, checked October 2026. "—" means not included or not confirmed in the vendor's documentation.
—
TLS only, do-it-yourself, or XcellHost?
From first call to encrypted mail in about two weeks*.
- 01Discovery callPlatforms, licences, regulators and who you mail sensitive data to.Day 1*
- 02Design & quoteMethods per mail type, policies, recipient experience and keys agreed.Days 2–4*
- 03Transport firstMTA-STS in testing mode, TLS-RPT reports, forced TLS to listed partners.Week 1*
- 04PilotEncryption templates or portal and DLP rules in audit mode for one team.Week 1–2*
- 05EnforceRules switched to encrypt, S/MIME issued, MTA-STS moved to enforce.Week 2*
- 06Run24×7 support, certificate renewals, monthly encryption report.Ongoing