That leaves you with no way to check to make sure you entered the right term, other than typing it again. If you are typing it right but auto-correct is kicking in when you hit enter, even trying again might fail because your site responds fast enough that you might not have time to notice the change before the results page comes up.
Also, it might be helpful when someone searches for a domain at a TLD that you do not support to say on the results page that the TLD is not supported.
Another feature request: When entering an IP, there's very little information available on it (only the hosting provider). Would be nice to get latlong, country etc (a la https://www.iplocation.net/).
Because seriously, that is an insanely cool database. I can even find all the sites that share my domain's Cloudflare IPs.
Privately registered eu domains are quite nice. I couldn't even find two of such that I own in your database and whois only reveals email (which I made sure from the beginning to be of the same domain that I just registered, so that's useless for anything). People can probably pay for more info though.
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.
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.
But perhaps there should be a possibility to remain anonymous (and the browser informing the user that this is the case).
Making it available to everybody just sheds light on the problem, it doesn't create the problem.
It's my understanding that the registrars are the ones with the burden here. They need to inform everyone of the data erasure and/or data updates on private information.
Fun times when you have public information for anyone to gather on the internet. It could be that there are exemptions for these kind of services, I do not know, but would the exemption not also include the services that aggregate/collect historic information as well?
Disclaimer; I am not a lawyer. I am not well versed in GDPR.
Anyone finding this interesting should go read up on GDPR.
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.
Under GDPR, Security trails (company or person that operates it) could be classified as a "Data controller"  and then would of course be liable to delete information gathered about a person upon request and when the data is deemed to be "inadequate, irrelevant or no longer relevant or excessive".
So for example, John Doe wants to remove the historic information that he used to own porn.com which he doesn't anymore.
However, I do not think it's clear that you have to delete the data for the current owner of porn.com due to his or hers need for privacy as long as they have collect the information lawfully.
As an actual advice to the people at security trails I would recommend they put up clear instructions on how to request a data erasure from their database. Like "Email firstname.lastname@example.org to request removal of your personal information" and what information they need to delete 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...
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.
On a more serious note - I'm very curious how you get such a long history of domains. i.e. I can see every DNS change and ownership for any domain - I didnt realise that was always available?
The thesis we have is that if you get hacked, it often times is through an old server or satellite domain. We're building tools to help you find the extended surface area where you can be hacked or have downtime. The example of you finding an old domain is a prefect use case.
More info in Dutch: https://blog.iusmentis.com/2017/11/08/internationale-domeinb...
kuschku.de has, for the past 2 years, always pointed at 126.96.36.199 or 188.8.131.52, never at 184.108.40.206. Funnily, for other domains pointed at the same IPs, it has correct data – e.g. quasseldroid.info correctly shows the IP history.
The datasets used here seem of questionable quality, souring the taste of this awesome feature.
.DE is particularly hard because they lock down the zone file. GTLDs like .INFO are easier to get because the zone files are open. We have 9 years daily granularity for the gTLDs.
Would love to clean up the U/X so it's clear what we have data for and what we don't to be completely transparent.
Thanks for the note.
For example, WHOIS info https://i.imgur.com/WNpyvcl.png should maybe show something like "none available", or "no WHOIS info is available for .de", or "go to denic.de to see WHOIS info" (DENIC offers the WHOIS info, if you enter the captcha). On the other hand, http://whois.domaintools.com/kuschku.de (a competitor) correctly shows the WHOIS.
Second, with the domain – I have no idea how the wrong value ended up on there.
The UI enhancements you mention are excellent - we will implement this shortly (not only for .de but for any case where we can not output any values).
Feel free to contact us at the e-mail address given at the bottom on every dnstrails page!
I 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.
Check out section 3.3.6
I own a domain I registered way back when you would send an email to InterNIC and registration was free. The WHOIS data returned for the domain only starts in 2008 and skips about 12-14 years.
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.
We'll do a technical blog post soon - good idea.
That being said, cool tool!
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.
But a question: why is one website I know of (and that resolves, and that has valid DNS entries) comes up blank?
2. For the whois registrant search, it's around 90 days old right now, but we're working on techniques to make it more current.
Living here, I know that their whois server rate limits heavily and the ccTLD zonefile is not available, so I'm guessing those are probably contributing reasons. Do you guys do any crawling at all?
I think this is a fantastic concept though. Knowing that whois database and zonefile access is often protected for commercial motivations, it really irks me. Open it all up.
DNS queries, if you have access to recursive resolvers.
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!