4 ms·
Eh, pretty minimal risk unless you use a guessable hostname and/or the URL gets published somewhere. If the install is under "eixk3.somedomain.com/ladderforfri
by KennyBlanken 2y ago
Eh, pretty minimal risk unless you use a guessable hostname and/or the URL gets published somewhere.
If the install is under "eixk3.somedomain.com/ladderforfriends" and it sits behind a reverse proxy, it might as well be invisible to the internet, unless your DNS provider is an idiot and allows zone transfers, or you are on a network where someone is snarfing up DNS requests and then distributing that info to third parties. If you restrict it to TLS 1.3, even someone sniffing traffic from one of your friends won't be able to glean anything useful, because the requested hostname is never sent in plaintext.
Rotate the hostname if/when it becomes necessary...
- WayToDoor 2y agoYour certificate will however show up in public certificate transparency lists. You could mitigate that with a wildcard cert, but still..
- paulddraper 2y agoThose are all very plausible
- cortesoft 2y agoAs soon as you get a cert for that domain, you will start getting requests to it because of certificate transparency reports. Everyone will know immediately the site exists.