Yeah this is a surprisingly little known fact- all certs being logged means all subdomain names get logged.
Wildcard certs can hide the subdomains, but then your cert works on all subdomains. This could be an issue if the certs get compromised.
Usually there isn’t sensitive information in subdomain names, but i suspect it often accidentally leaks information about infrastructure setups. "vaultwarden.example.com" existing tells you someone is probably running a vaultwarden instance, even if it’s not publicly accessible.
The same kind of info can leak via dns records too, I think?
Automated agents can tail the certificate log to discover new domains as the certs are issued. But if you want to explore subdomains manually, https://crt.sh/ is a nice tool.
govideo|1 year ago
snailmailman|1 year ago
Wildcard certs can hide the subdomains, but then your cert works on all subdomains. This could be an issue if the certs get compromised.
Usually there isn’t sensitive information in subdomain names, but i suspect it often accidentally leaks information about infrastructure setups. "vaultwarden.example.com" existing tells you someone is probably running a vaultwarden instance, even if it’s not publicly accessible.
The same kind of info can leak via dns records too, I think?
thisisgvrt|1 year ago
yatralalala|1 year ago
This way, you will force everyone to go through Cloudflare and utilize all those fancy bot blocking features they have.
system2|1 year ago
daneel_w|1 year ago
Kikawala|1 year ago
Eikon|1 year ago