HTTPS is the secured variant of HTTP.

HTTPS uses TLS instead of TCP as its transport mechanism.

Most WebRTC services end up using HTTPS and not HTTP because of the way permissions are handled by web browsers: When a service asks for access to the camera or microphone of the user with WebRTC, the web browser asks the user for permission. This request will occur each time the service is loaded (or the page is refreshed) if the page was loaded using HTTP, but will happen only once and the user’s permissions will be remembered by the web browser if the page was loaded using HTTPS.