CommzGate Upcoming API Security Update: TLS 1.2 Support Ending – Action Required by 2025-09-15 09:00 SGT

Monday, 15 September 5 minutes
Scheduled
Scheduled

Dear User,

As part of our continued efforts to maintain the highest standards of security and compliance, we will disable support for TLS 1.2 on our API services by 15 September 2025 09:00 SGT This applies to the end-points https://www.commzgate.net and https://vip.commzgate.net

These API endpoints will require TLS 1.3 for secure communication. TLS 1.2 will no longer be supported.

Our legacy API end-point URLs would also cease to function on this date.

1. TLS 1.3 Verification Please test and verify that your client applications and integration environments support TLS 1.3. by using our sandbox environment at:

https://vip.commzgate.net:448/gateway/SendMessage

This is a dummy end-point to test SSL handshake only, no actual SMS will be sent. We recommend updating your client libraries or runtime environments if TLS 1.3 is not currently supported.

2. Update API end-point URL (if needed) For users of our standard API end-point to send SMS messages, please ensure you are using our latest API end-point URL at

https://www.commzgate.net:443/gateway/SendMessage

If any of your application is still using our legacy API end-points, it would no longer be available.

TLS 1.3 offers stronger encryption, improved performance, and enhanced privacy compared to TLS 1.2. By making this change, we aim to:

  • Eliminate support for outdated cryptographic algorithms
  • Improve overall security posture
  • Ensure compliance with IMDA requirements

If you have questions or need assistance verifying your TLS compatibility, please contact our support team at supportdesk@commzgate.com

Avatar for
Affected components
  • CommzGate Portal
    • Alert12 Emergency Messaging
    • CloudSMS
  • CommzGate API
    • Messaging API general end-point
    • Messaging API reserved end-point
    • Contacts API