As a Systems Engineer monitoring secure enterprise services, I want built-in HTTP/HTTPS sensors to support client certificate authentication (mutual TLS), so that I can monitor certificate-protected administrative interfaces, APIs, and customer portals without having to create and maintain custom scripts for each endpoint.

In secure environments, many web-based services—especially administrative interfaces, APIs, and customer portals—are only accessible via HTTPS with client certificate authentication. These URLs cannot be accessed using standard HTTP/HTTPS sensors in PRTG, as there is currently no way to specify a client certificate and private key.

Currently, the only workaround is to use custom scripts (e.g., PowerShell or curl) and integrate them into PRTG via EXE/Script Advanced Sensors.

We suggest built-in sensors in PRTG to support:
Client certificates
Optional passphrase support
Certificate validation options
GUI-based configuration of client certificates per sensor