Maybe you should play around a bit with the information you got. I would assume, that it is self-explanatory...
curl -vkI https://192.168.10.15:5442/status/health
Just add the port to the IP address or hostname. If you call the server via https:// but the server only speaks http:// (and vice versa), you usally receive 400 Bad request as response. That's not always the case. But you should always receive a certificate, when calling via https://. Otherwise curl will complain, that no certificate was received.
You are wrong about the argument regarding -k. This option just helps you to establish an SSL handshake, even if the server certificate is not trustworthy. You will receive the required information in each case. If you have to validate the trustworthiness of the remote certificate, you please checkout https://curl.se/docs/sslcerts.html. This should help to understand how it works. They also reference the openssl s_client tool, which helps for deeper investigations. curl is not made for this.