You should assume that an attacker can observe traffic. This may happen at your network endpoint, at the client's end, or somewhere in between.
On the client side, the attacker will see DNS resolution for random.example.com if he is observing your users, and he may also discover this domain name if he attempts to access to site directly (this second method ...
But don't you own all the subdomains of a given domain you bought?
Sure. If you own the domain you control also subdomains. If you have control over applications that use your subdomains, then you can do whatever you want.
But there are hosting providers, that give users subdomains like user-123.provider.com below their own domain. In particular, users don'...
The q45vzle is the randomly named subdomain. Does having such a
subdomain name really help in preventing it from getting discovered?
If yes, then how strong the random subdomain name needs to be? If no,
what could be the security method which I can use for this situation?
In short no.Even if you were to create random subdomain names which are hard to ...
There might be a Web Application Firewall with different profiles for different domains. So they might share the same ip address but every domain serves a different purpose and so different ports are allowed.
A WAF is able to "unterstandt" the http packets, that way it is able to determine the domain you try to connect to.