What can a network owner see for google searches on an iPhone connected to their WiFi network? [closed]
Curious to see what a network (WiFi owner) can see for google searches on an iPhone connected to their network (a network that is protected by a password).
encryption
closed as off-topic by fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik Feb 27 at 1:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
Curious to see what a network (WiFi owner) can see for google searches on an iPhone connected to their network (a network that is protected by a password).
encryption
closed as off-topic by fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik Feb 27 at 1:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik
If this question can be reworded to fit the rules in the help center, please edit the question.
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21
add a comment |
Curious to see what a network (WiFi owner) can see for google searches on an iPhone connected to their network (a network that is protected by a password).
encryption
Curious to see what a network (WiFi owner) can see for google searches on an iPhone connected to their network (a network that is protected by a password).
encryption
encryption
asked Feb 16 at 1:44
MicahMicah
1
1
closed as off-topic by fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik Feb 27 at 1:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik Feb 27 at 1:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – fixer1234, Debra, music2myear, BillP3rd, DrMoishe Pippik
If this question can be reworded to fit the rules in the help center, please edit the question.
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21
add a comment |
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21
add a comment |
1 Answer
1
active
oldest
votes
If you're using TLS (HTTPS), then all they can see is that you're going to google.com; the search string and Google's responses are protected by TLS encryption.
When you click on a link in the search results, your computer may do a DNS lookup for that domain name, and then the TLS handshake as you connect to that site will leak the hostname (FQDN) of that site via the TLS SNI.
The IETF is working on ways to encrypt DNS lookup and fix the TLS SNI hostname leak, but those new privacy mechanisms have not been fully standardized and are still a ways from being deployed as of this writing (early 2019).
(I've edited this answer to incorporate good feedback from the comments below.)
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you're using TLS (HTTPS), then all they can see is that you're going to google.com; the search string and Google's responses are protected by TLS encryption.
When you click on a link in the search results, your computer may do a DNS lookup for that domain name, and then the TLS handshake as you connect to that site will leak the hostname (FQDN) of that site via the TLS SNI.
The IETF is working on ways to encrypt DNS lookup and fix the TLS SNI hostname leak, but those new privacy mechanisms have not been fully standardized and are still a ways from being deployed as of this writing (early 2019).
(I've edited this answer to incorporate good feedback from the comments below.)
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
add a comment |
If you're using TLS (HTTPS), then all they can see is that you're going to google.com; the search string and Google's responses are protected by TLS encryption.
When you click on a link in the search results, your computer may do a DNS lookup for that domain name, and then the TLS handshake as you connect to that site will leak the hostname (FQDN) of that site via the TLS SNI.
The IETF is working on ways to encrypt DNS lookup and fix the TLS SNI hostname leak, but those new privacy mechanisms have not been fully standardized and are still a ways from being deployed as of this writing (early 2019).
(I've edited this answer to incorporate good feedback from the comments below.)
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
add a comment |
If you're using TLS (HTTPS), then all they can see is that you're going to google.com; the search string and Google's responses are protected by TLS encryption.
When you click on a link in the search results, your computer may do a DNS lookup for that domain name, and then the TLS handshake as you connect to that site will leak the hostname (FQDN) of that site via the TLS SNI.
The IETF is working on ways to encrypt DNS lookup and fix the TLS SNI hostname leak, but those new privacy mechanisms have not been fully standardized and are still a ways from being deployed as of this writing (early 2019).
(I've edited this answer to incorporate good feedback from the comments below.)
If you're using TLS (HTTPS), then all they can see is that you're going to google.com; the search string and Google's responses are protected by TLS encryption.
When you click on a link in the search results, your computer may do a DNS lookup for that domain name, and then the TLS handshake as you connect to that site will leak the hostname (FQDN) of that site via the TLS SNI.
The IETF is working on ways to encrypt DNS lookup and fix the TLS SNI hostname leak, but those new privacy mechanisms have not been fully standardized and are still a ways from being deployed as of this writing (early 2019).
(I've edited this answer to incorporate good feedback from the comments below.)
edited Feb 22 at 22:05
answered Feb 16 at 2:04
SpiffSpiff
78.2k10119163
78.2k10119163
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
add a comment |
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
1
1
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
And the second sentence should be something like, “But the data being transmitted to Google—such as the actual search string and response—will be encrypted.”
– JakeGould
Feb 16 at 4:51
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
Does the default web browser / google search on an iPhone always use TLS?
– Xen2050
Feb 16 at 5:02
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
If a link is clicked on, it is most likely possible to additionally see the domain name associated with the link if DNS is being sniffed.
– davidgo
Feb 16 at 9:07
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@davidgo DNS sniffing isn't even necessary to see what site you're going to over a TLS connection, due to the TLS SNI. The IETF is working on ways to keep the SNI private, but for now, the TLS handshake leaks the hostname (FQDN) of the server you're connecting to.
– Spiff
Feb 22 at 21:57
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
@spiff interesting, and makes sense.
– davidgo
Feb 22 at 22:02
add a comment |
Is the iPhone yours, or is it theirs or is it managed in anyway?
– Appleoddity
Feb 16 at 2:21