Can my ISP see the URLs I visit when using HTTPS://

Can my ISP see the URLs I visit when using HTTPS://

Attached: questionfrogs.jpg (640x560, 57K)

Other urls found in this thread:

upturn.org/reports/2016/what-isps-can-see/
weirdporn
eff.org/pages/tor-and-https
tools.ietf.org/html/rfc8446
1.1.1.1/
twitter.com/SFWRedditVideos

yes

no

Sources, both of you.

Please repeat the question

Can my ISP see the URLs I visit when using HTTPS:// ?

Yes. How else would it know what site to take you? They just can't see the data.

the URLs yes, the contents of the request no.

read the HTTP reference

Sort of. You need to send a DNS request, which is unencrypted, to even resolve the FQDN portion of the URL.

Yes they can because DNS resolution happens via port 53 UDP (the DNS protocol). Unless you are using DNSSEC, then they don't know.

Any content, headers, or the exact page you visit they won't know.

Well fuck.

No they can't see the full address or the content of the page and information that you send but they can see the domain address/ip address "Even with HTTPS, ISPs can still see the domains that their subscribers visit."
upturn.org/reports/2016/what-isps-can-see/

SSL protects the contents of the pages you request. Someone watching network activity can still see what IPs you request traffic from. Use a trusted VPN for what you want.

So they know if I visit weirdporn dot com?

I dun goofed.

it's depreciated use SHTTP:// now

>Unless you are using DNSSEC, then they don't know.
DNSSEC doesn't encrypt DNS request. And even if it did that isn't going to help you if you're using your ISP's DNS server.

They can see the hostname of the server you're connecting to because of SNI and possibly DNS. They cannot see the HTTP request nor the response, so the path you're requesting and the contents of the page are encrypted.

They don't care about weirdporn dot com

The care about illegalstuff dot com

Not if the owner of your small ISP knows you.

Yes, they can very easily tell what website you are going to regardless of whether you use HTTP or HTTPS. The IP is not magically encrypted in route and magically makes it there without anyone knowing where it's going.

Only if you're not using incognito mode.

>trolling on Jow Forums in 2018

they can see the dns requests you send out. On https they can't see what page on pornhub you have just loaded but they know that milliseconds before your computer attempted to resolve the ip for pornhub.com.


You will have to use a vpn or some sort of dnscrypt solution to combat this.

They know the domain, not the page or contents.

>making a joke is now trolling

it's in the TLS headers

eff.org/pages/tor-and-https

What a stupid question. Use a fucking search engine.

if you want to sound like you know what youre talking about then start reading into the ACTUAL STANDARD. google rfc http or http over TLS.

using the rfc, you can refer to the actual standard way of implementation.

tools.ietf.org/html/rfc8446

>small ISP
they exist?

>>trolling on Jow Forums in 2018

>>>not trolling on Jow Forums in 2018

you need to use cloudflare's dns to encrypt all url request, just use it!
we are good guys!
1.1.1.1/

Yes. But supposedly not what you send/receive, aka passwords/users/requests.

I doubt its secure given that its an old standard.

Your ISP can see what domain (in some cases) and ip you initiate a tcp socket with, nothing else.

yes
they know you all the shemaleidol and similar sites you visit. Think twice before you threaten them about throttling next time.

your ISP can see the cute girl (boy) you are jerking off to, yes.

this is correct, mostly

it's encrypted but they know it's an HTTPS request, they know who sent it, and they know where it's going, they just don't know what's in the packet

t. part of the way through Tannenbaum's Computer Networks and I think I'm getting a hang of it

Attached: tumblr_pcne6yybjR1sl0uxfo1_400.gif (256x218, 76K)