Couldn’t get it to work with .rs domains.
That being said, cool tool!
Find every domain someone owns automatically
31–40 of 110 posts
Re: Find every domain someone owns automatically
#32How do you plan on handling the EU’s “right to be forgotten” (it’s pretty straightforward to make the argument you’re a search engine) and other components of the GDPR?
Re: Find every domain someone owns automatically
#33Couldn’t get it to work with .rs domains. That being said, cool tool!
these country code domains. LOL. We bought and built up http://www.domainlists.io so we can add some more stuff like this in. I'll make sure we add .RS to the action items. Thanks for the feedback and enjoy!
Re: Find every domain someone owns automatically
#34How do you plan on handling the EU’s “right to be forgotten” (it’s pretty straightforward to make the argument you’re a search engine) and other components of the GDPR?
Haven't really explored this. Any feedback or ideas is appreciated!
Re: Find every domain someone owns automatically
#35Earlier quoted context omitted.
right now we're getting .au domains from Open Crawl. It's tricky because the zone file is not available like you mentioned. If anyone has any ideas on how to get more .au domains, we'll gladly implement.
CT logs come to mind, if you aren't using them already. DNS queries, if you have access to recursive resolvers.
we're using CT logs for getting hostnames (you can see it at the top of the page of any domain).
We have a great recursive resolver source but haven't been able to integrate it into the data pipeline yet.
thanks for the note and ideas!
Re: Find every domain someone owns automatically
#36Hmm is there a technical write up of how you are pulling this data?
I tried one of our companies for fun and it’s only pulling 1.4million records in one place and then 65,000 in another. Doesn’t seem to have all our nameservers or relays either.
Re: Find every domain someone owns automatically
#37Hmm is there a technical write up of how you are pulling this data? I tried one of our companies for fun and it’s only pulling 1.4million records in one place and then 65,000 in another. Doesn’t seem to have all our nameservers or relays either.
Would love to hear more so we can debug. chris at securitytrails.com if you have a few mins so we can chase things down.
We'll do a technical blog post soon - good idea.
Re: Find every domain someone owns automatically
#38I'm finding that sometimes it'll turn up the data correctly and other times it won't match what I can find by manually typing in addresses into domains.google
As in this service will claim all data is private when google is able to return the actual registrant email address and/or name. As well as valid phone numbers which don't match what dnstrails is outputting.
Re: Find every domain someone owns automatically
#39I'm finding that sometimes it'll turn up the data correctly and other times it won't match what I can find by manually typing in addresses into domains.google As in this service will claim all data is private when google is able to return the actual registrant email address and/or name. As well as valid phone numbers which don't match what dnstrails is outputting.
thanks for the note and testing. Would love to dig into any specific use cases so we can see whats going on. chris at securitytrails.com
Re: Find every domain someone owns automatically
#40Earlier quoted context omitted.
Can you give a gist of your findings? I'll take a guess : customers are given unique whois protected email addresses allowing you to find all the domains owned by the person. Eg- If I own abc.com and xyz.com, both have the same public email address. The problem with such bugs is that there's no way to undo the damage since historical whois records are archived.
you nailed it. It goes a little further with what you can see and how easy it is but right on point! If you notice anything else people would find interesting, feel free to post it or email me (in profile).
[deleted]