Are you not concerned that you are leaking exactly what domains people are looking up in realtime?
If I used a service like that I would expect some degree of privacy that goes beyond this. It's crazy to me that you're doing this to be honest
If I used a service like that I would expect some degree of privacy that goes beyond this. It's crazy to me that you're doing this to be honest
They're just domain names which are effectively public records. And even if you thought you registered a super secret domain name (no such thing), maybe the registrar looked it up, or some bot found it through brute force (if nslookup.io is open to bots).
Chrome don’t actively publish nslookups on public sites.
I think you’ve missed the point.
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.
You know the Qualsys SSL Tester tool? That has a checkbox about making the result public or not and that is because by default people wouldn't expect the domain to be leaked (even though it's already public information that doesn't really matter)