4 ms·
hey- would love it if you can drop me an email (in profile) so we can debug/improve. .DE is particularly hard because they lock down the zone file. GTLDs like
by mxpxrocks10 9y ago
hey- would love it if you can drop me an email (in profile) so we can debug/improve.
.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.
- kuschku 9y agoYour profile doesn’t have any email address in it, but you can just check https://dnstrails.com/#/domain/domain/kuschku.de https://dnstrails.com/#/domain/domain/kuschku.de vs. https://dnstrails.com/#/domain/domain/quasseldroid.info https://dnstrails.com/#/domain/domain/quasseldroid.info For example, WHOIS info https://i.imgur.com/WNpyvcl.png 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 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.
- computer22 9y agoHi kuschku, thanks for providing us with the samples with the outdated/missing data. We will definitely look into the case and continue to enhance the data we collect. 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!