3 ms·
Internal domains generally resolve to private IP ranges, so don't do any harm when broadcasted. Besides, many people use Chrome, and who knows what they do by d
by pul 5y ago
Internal domains generally resolve to private IP ranges, so don't do any harm when broadcasted. Besides, many people use Chrome, and who knows what they do by default with browsing history.
- hsbauauvhabzb 5y agoYou’ve obviously never seen orgs with /16 IP ranges, or developers/ops accidentally screw up, for that matter. Chrome don’t actively publish nslookups on public sites. I think you’ve missed the point.
- antonvs 5y agoInformation leakage of any kind potentially gives an attacker something they can use. On its own any given piece of info may seem harmless, but when combined with other info it can start to pose a risk. Leaking internal hostnames could allow an attacker to build a view of an internal network ahead of time, before actual penetration. Once inside a network it's often a race against time, so this can make a difference.