Skip to content

// free tool, no account

SIP TLS certificate check.

Enter the SBC or SIP server your devices connect to. We open a TLS connection with that name as SNI, read the certificate it presents, and tell you whether clients will accept it and for how long.

one TCP connection and a TLS handshake, no SIP · from a tools-only address, not our monitoring probes

Find out 30 days early, not at 9 AM on the day

SIP/SENTRY checks the certificate on every SIP TLS endpoint you add, warns at 30, 14 and 7 days, and keeps checking OPTIONS and registration on the same SBC. Three monitors are free.

SIP over TLS, briefly

Which port does SIP over TLS use?

The default is 5061, the port RFC 3261 assigns to SIPS. Many SBCs use another one, for example 443 to get through restrictive firewalls, or a separate port per customer or trunk. The _sips._tcp SRV record for a SIP domain says which host and port clients should use, and the SIP SRV lookup tool on this site reads it for you.

What happens when a SIP TLS certificate expires?

Every client that verifies the certificate refuses the TLS handshake, so phones and softphones configured for SIP over TLS drop their registration and calls over TLS trunks fail. The port still accepts TCP connections, so ping and port checks stay green while the service is down. That is why certificate expiry needs its own check with an early warning, not a check that only notices once the handshake fails.

Why does the name I enter matter, and not just the address?

The checker sends the host name you enter as SNI in the TLS handshake. An SBC that serves several domains, or a carrier platform behind one address, picks the certificate to present by that name. Checking by IP address alone usually returns a default certificate that no client would ever be shown, and the name match tells you whether the certificate is issued for the name your devices are configured with.

Is a self-signed certificate on an SBC a problem?

It depends on who connects. Phones that were provisioned to trust your own certificate authority are fine with it. Anything that verifies against public roots is not: carriers that require TLS, Microsoft Teams Direct Routing, which requires a certificate from a public certification authority with the SBC name on it, and most softphones on personal devices. The checker reports the expiry either way, because a self-signed certificate expires too.

What does this checker send to my server?

One TCP connection and a TLS handshake, the same as a browser opening a page, and then it disconnects. It sends no SIP at all. It connects from a dedicated address that serves only these public tools and is not one of the SIP/SENTRY monitoring probes, so nothing you see from it should be allowlisted.