In situations where the consumer doesn't trust/control the workstation and the network, can consumer safely do potentially sensitive activities (like making a payment or transferring confidential documents) over the internet when HTTPS is used?

For instance: when I use my employer's computer and am on the company network, or I am in an airport and use a public kiosk there there.

Naturally, IT administrators in these circumstances are in full control of CA management, and could potentially use a proxy and load the proxy's certificate into the trusted root list, so my browser would show everything being fine.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA, I can be assured that there's no one eavesdropping on the traffic.

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but are there any extra steps I can take? For instance, could I somehow export the cert I'm receiving from the HTTPS site and submit it to some service for verification?

In situations where the consumer doesn't trust/control the workstation and the network, can consumer safely do potentially sensitive activities (like making a payment or transferring confidential documents) over the internet when HTTPS is used?

For instance: when I use my employer's computer and am on the company network, or I am in an airport and use a public kiosk there, is there a way to keep them from spying on me?

Naturally, IT administrators in these circumstances are in full control of CA management, and could potentially use a proxy and load the proxy's certificate into the trusted root list, so my browser would show everything being fine.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA, I can be assured that there's no one eavesdropping on the traffic.

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but are there any extra steps I can take? For instance, could I somehow export the cert I'm receiving from the HTTPS site and submit it to some service for verification?

In situations where the consumer doesn't trust/control the workstation and the network, can consumer safely do potentially sensitive activities (making a payment or transferring confidential documents) over the internet when https is used?

An example use case might be when I use my employer's computer and am in a network controlled by my employer or I am in an airport and use publicly available desktop there.

Naturally IT administrators in these circumstances are in full control of CA management and could potentially use a proxy and sign the traffic between the proxy and me and in that case the browser will think it's all safe and show green.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA rather than my company or some unknown authority, I can be assured that there's a real TLS channel established between me and service provider and I can be sure that there's no one eves-dropping on that traffic?

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but is there any extra steps I can take like export the cert I'm receiving from the https site and submit it to some service for verification?

In situations where the consumer doesn't trust/control the workstation and the network, can consumer safely do potentially sensitive activities (like making a payment or transferring confidential documents) over the internet when HTTPS is used?

For instance: when I use my employer's computer and am on the company network, or I am in an airport and use a public kiosk there there.

Naturally, IT administrators in these circumstances are in full control of CA management, and could potentially use a proxy and load the proxy's certificate into the trusted root list, so my browser would show everything being fine.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA, I can be assured that there's no one eavesdropping on the traffic.

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but are there any extra steps I can take? For instance, could I somehow export the cert I'm receiving from the HTTPS site and submit it to some service for verification?

In situations where - consumer doesn't trust\control workstation and the network, can consumer safely do a potentially sensitive activities over the internet when https is used? Say make a payment or transfer confidential documents?

Example use case might be - when I use my employer's computer and am in a network controlled by my employer or I am in an airport and use publicly available desktop there.

Naturally IT administrators in these circumstances are in full control of CA management and could potentially use a proxy and sign the traffic between the proxy and me and in that case the browser will think it's all safe and show green.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA rather than my company or some unknown authority, I can be assured that there's a real TLS channel established between me and service provider and I can be sure that there's one eves-dropping on that traffic?

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but is there any extra steps I can take like export the cert I'm receiving from the https site and submit it to some service for verification?

In situations where the consumer doesn't trust/control the workstation and the network, can consumer safely do potentially sensitive activities (making a payment or transferring confidential documents) over the internet when https is used?

An example use case might be when I use my employer's computer and am in a network controlled by my employer or I am in an airport and use publicly available desktop there.

Naturally IT administrators in these circumstances are in full control of CA management and could potentially use a proxy and sign the traffic between the proxy and me and in that case the browser will think it's all safe and show green.

My current understanding is that as long as I can verify that the cert isn't spoofed and is signed by a well known CA rather than my company or some unknown authority, I can be assured that there's a real TLS channel established between me and service provider and I can be sure that there's no one eves-dropping on that traffic?

Now if my previous statement is correct what is the best way to verify that cert? I understand that I can just open it up and inspect the CA's name, but is there any extra steps I can take like export the cert I'm receiving from the https site and submit it to some service for verification?