GoDaddy is now masking _all_ DNS info whether you pay for their "privacy" service or not, so thats making a substantial black hole in this data
Find every domain someone owns automatically
101–110 of 110 posts
Re: Find every domain someone owns automatically
#102Earlier quoted context omitted.
Why do you think privacy should be easier for domain owners? Shouldn't it instead be easy for a visitor to find out who owns the domain and is responsible (content, technical or legal) for a certain site?
Not everyone needs to know my home address. Especially not for a domain I use for emails. Way too many weird people out there.
This is why I lie in my whois data, to the horror of the goody two-shoes on HN I'm sure.
The whois data is a great place to start a social engineering hack. The address or any past address is often used for identity.
Re: Find every domain someone owns automatically
#103Re: Find every domain someone owns automatically
#104Earlier quoted context omitted.
>one could argue that they (security trails) don't have to remove the data. It doesn't work that way. The "right to be forgotten" can be used to remove search results from Google, even if the original content stays up.
Interesting! From a quick google the following wikipedia citation seems to what you are referring to: Grounds for removal include cases where the search result(s) "appear to be inadequate, irrelevant or no longer relevant or excessive in the light of the time that had elapsed."[1] Under GDPR, Security trails (company or person that operates it) could be classified as a "Data controller" [2] and then would of course b…
Re: Find every domain someone owns automatically
#105Is this just a reverse indexed WHOIS database? If so, it's no surprise that my domains don't appear in yhe results: I signed up for Whois anonymization through my DNS provider. I was recently considering unsubscribing, so thank you to the creators of this for reminding me that my privacy is under attack at all times and I should do whatever I can to protect it.
Be careful about trusting privacy protection plans. A spam email came to me recently showing the unmasked info and I still have no idea how it acquired its data... https://www.thejach.com/view/2017/10/google_whois_protection...
Re: Find every domain someone owns automatically
#106I have a very common english name.
Annoyingly, some of the domains it inaccurately says I own are NSFW. They need to put a big disclaimer on the results page pointing out that the results aren't necessarily accurate.
Re: Find every domain someone owns automatically
#107What’s interesting is that it correctly finds Namecheap whois-guarded domains too. If I search for the guarded domain directly it shows the correct record as the owner’s address/etc being WhoisGuard, but then if I search for a non-guarded domain and click through from the identified name, it does list the guarded domains as well (!)
Re: Find every domain someone owns automatically
#108I didn't look into what this is doing but it's not finding 1/2 of my domains (they are not private). I'm guessing it's not "Find every domain someone owns" it's "Find every domain that meets X criteria" which may more may not be every domain someone owns.
Re: Find every domain someone owns automatically
#109More info in Dutch: https://blog.iusmentis.com/2017/11/08/internationale-domeinb...
Re: Find every domain someone owns automatically
#110Must say, I'm not a fan of yours or similar services, or whois databases for that matter. Privacy should be easier on the internet for people owning domain names.
Why do you think privacy should be easier for domain owners? Shouldn't it instead be easy for a visitor to find out who owns the domain and is responsible (content, technical or legal) for a certain site?
Also your question may apply to the other end too. Shouldn't it be easy for an owner of the server to find out who is behind an IP address that is connecting to his server - and I mean easy access to his/her phone number, home address and a complete history of those, too?
It's easy to concot legal, technical and content reasons why this should be.