Hi everyone,
As part of Zoho's ongoing security hardening, Zoho CRM is ending support for weak Transport Layer Security (TLS) cipher suites. Enforcement is rolling out in phases across Zoho data centers, and some have already switched over. The change will be complete across all data centers by Dec 31, 2026.

Effective date: Dec 31, 2026
Zoho CRM will only accept connections that use the strong cipher suites listed below. If your browsers and API clients already use them, nothing changes and you don't need to do anything. Recent versions of most browsers already support these cipher suites.
Any browser or API client still using a weak cipher will lose access once the change reaches your data center. You may notice failed API calls, integrations that stop syncing, or pages that don't load.
What are API clients?
API clients are tools that connect to Zoho CRM through our APIs instead of a browser, such as:
- Postman and similar testing tools
- Custom scripts and applications built by your team
- Third-party integrations and connectors
- Automation and middleware platforms
These tools depend on the software they run on, such as Java, .NET, Python, or OpenSSL. That's why an integration can stop working even when Zoho CRM opens fine in your browser.
Supported TLS cipher suites
From Dec 31, 2026, Zoho CRM accepts connections only over these cipher suites:
TLS 1.2
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
TLS 1.3
- TLS_AES_128_GCM_SHA256
- TLS_AES_256_GCM_SHA384
- TLS_CHACHA20_POLY1305_SHA256
Connections that use any other cipher suite will be rejected.
How to check and what to do
Open
tlstest.zoho.com/api from the browser or API client you want to test. For an API client, send a GET request from the client itself, on the server it runs on, so the test uses the same runtime as your integration.
- Strong cipher (status 200): Your client uses a supported cipher suite. No action is needed.
- Weak cipher (status 400): Your client uses a cipher suite that will stop working. Upgrade it before Dec 31, 2026.
To fix a weak cipher, upgrade the browser or API client to its latest version. For custom scripts and applications, update the runtime and TLS libraries they're built on, since outdated versions cause most of these issues. If you use a third-party integration, check with its provider that it supports the cipher suites listed above.
If you're a Zoho partner, please share this update with your customers so they can check their setups before the deadline.
Data center status
We're retiring weak TLS cipher suites across all Zoho data centers in two phases. We'll keep this section updated as enforcement rolls out.
- Phase I (completed): Japan (JP), Australia (AU), United Kingdom (UK), Saudi Arabia (SA), and China (CN)
- Phase II (pending): United States (US), India (IN), Europe (EU), and Canada (CA)

Learn more

Need help?
If you have questions or run into connection issues after the change, reach out to our support team at
support@zohocrm.com. We'll be glad to help.
Thanks,
Nizamuddin