If we have something like this url:
https://www.example.com/Some/Page/index.html?id=15
I know that example.com
will be sent as plain text, but /Some/Page/index.html?id=15
is sending securely.
Now, my question is, if we have something like this:
https://somesubdomain.example.com/Some/Page/index.html?id=15
May attackers know that I'm visiting somesubdomain.example.com
? or they just can know I'm visiting example.com
?
In other words, is subdomain part of url sending securely?
In addition to DNS misconfigurations, subdomains can be exploitable if they are assigned to untrustworthy users, the paper says. “Dangling DNS records”--that is, records pointing to expired resources--can be vulnerable to being taken over by unauthorized parties.
If you are asking whether you need SSL for a subdomain, the answer is yes. An SSL certificate authenticates your identity and establishes a secure communication channel between the client and the website.
The Wildcard SSL certificate covers all subdomains on a single root domain. However, it does not cover completely different domain names. For example, a Wildcard SSL certificate will cover the following: www.yourdomain.net.
A secure URL should begin with “https” rather than “http.” The “s” in “https” stands for secure, which indicates that the site is using a Secure Sockets Layer (SSL) Certificate. This lets you know that all your communication and data is encrypted as it passes from your browser to the website's server.
If the client is using Server Name Indication (most modern web browsers/platforms do), the host name (not the rest of the URL) will be visible in clear in the handshake in the server name indication extension, so both www.example.com
and somesubdomain.example.com
will be visible.
If the client isn't using SNI, an eavesdropper would still see the server certificates and the target IP address(es). Some certificates can be valid for multiple host names, so there may be some ambiguity, but this should give a fairly strong clue to the eavesdropper.
In addition, the same eavesdropper might be in a position to see the DNS requests (unless you've configured the hosts explicitly in your hosts
file perhaps).
In general, you shouldn't assume that the host name you're trying to contact is going to be hidden. Whether it's a subdomain isn't relevant, it's the full host name as it's requested by the client that matters.
When using https all traffic between http client and server is encrypted. That does not mean it is safe, but it is encrypted according to what you refer here. Something a network sniffer can see is the ip address you communicate with. That is regardless of what network name had been resolved to that address.
Simply try yourself and use a network sniffer. I recommend wireshark
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With