Open Search or jump to... to find a monitored domain or certificate by name and go straight to its page. Search results show certificate expiry or revocation details, and the menu also includes a shortcut to watch a new domain.

Use the Theme selector in the app to choose Light, Dark, or System. System follows your device's appearance setting, and your choice is saved for future visits.

Hover over an IP address on a monitored domain or in a TLS/SSL Server Test to see its reverse DNS hostname when one is available. The hostname field is also available for domain IP addresses and TLS scan results through the GraphQL API.

On a monitored domain, select edit beside the current HTTP check path to choose which endpoint Cert Chief checks, such as /health. Saving the path starts a new HTTP check.

Certificate checks now support additional services that negotiate TLS after connecting, including supported mail and FTP ports. The domain view identifies connections that used opportunistic TLS so you can distinguish them from services that start with TLS.

A monitored domain's IP addresses now show their autonomous system number and network details. Use this information to distinguish addresses served by different hosting networks when reviewing certificate scans.

Monitored domains now show assessment grades from testssl.sh, and you can receive a notification when a grade changes. Open the associated report to investigate the findings behind the new grade.

Request a new TLS/SSL Server Test when you want to check a configuration change. Previous cached results remain available to review while a fresh assessment runs; request frequency depends on whether you are signed in.

Integrations can retrieve TLS/SSL Server Test reports through the API. Use the report data to inspect assessment results alongside your own monitoring or tooling.

Use the public TLS/SSL Server Test to inspect a server's TLS configuration without signing in. The assessment is powered by testssl.sh and provides a report you can review or share.

HTTP checks now also run for monitored IP addresses. You can inspect the HTTP response alongside certificate information when monitoring a host directly by its IP address.

HTTP checks now show the response status code. You can also choose how responses in the 400–499 range affect monitored health using the HTTP status preferences: HTTP status 4xx as OK or HTTP status 4xx as error.

The domains list now updates as scans progress and results arrive. You can follow monitoring status without repeatedly refreshing the page.

You can now enable Show domain IP's on the index in interface preferences. The domains list then displays the detected IP addresses for each domain, so you can review where your monitored hosts resolve without opening them individually.

You can now retrieve Cert Chief's scanner addresses from public text endpoints: /.well-known/ip-list, /.well-known/ip-list-v4, and /.well-known/ip-list-v6 on https://cert.chief.app. Use these lists when allowing monitoring traffic through your firewall.

Domain scans now check HTTP responses for hostnames monitored on port 443. The GraphQL API exposes the response statusCode and redirectsToHttps result, so integrations can check whether plain HTTP redirects to HTTPS alongside certificate information.

Email notification channels now support sending a test notification. Check that messages reach the configured mailbox before relying on it for monitoring alerts.

You can now sort your domains by Certificate expiration (ascending) or Certificate expiration (descending). Bring the certificates expiring soonest to the top of the list when reviewing renewals.

Certificate-expiration reminders now run four, three, two, and one day before expiration, and on the expiration day. For certificates that remain expired, follow-up reminders run after one, two, three, four, seven, ten, and fourteen days.

Scans you request manually now receive priority over routine queued scans. This applies to domain rescans and requests to refresh SSL Labs or Security Headers results.