You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I configured the API keys for the dehashed.com service, and it all works well, but each time I make a query(any, email or domain) it returns a bunch of junk data(1000+) along with some valid results at the beginning.
The text was updated successfully, but these errors were encountered:
Same here. The output shows every e-mail address from dehashed which contains the word "email".
fyi:
When you search for a domain on the dehashed website like they suggest (email:"*@domain.com"), you also receive over a million results (junk) which seems to be the same output like in h8mail. But when you search for *domain.com the results are correct.
Yes the Dehashed API returns quite a lot of data. h8mail already does a first pass of cleaning blank results, but some results do still have a very verbose structure.
I had contacted the support while developing this version to mention the blank fields, and they answered the following:
The reason we keep the structure intact is because some people can't parse them in/out. We've had them removed before but people requested we keep the structure there so we decided to serve it even if it's blank/null.
I am not sure if this also applies to the junk data but it might. Going to notify support about this issue, will update.
@kkris9 noted for the globing, I'll check if it applies to the API too.
In the meantime, you can check the raw data returned by the API using --debug.
Description
I configured the API keys for the dehashed.com service, and it all works well, but each time I make a query(any, email or domain) it returns a bunch of junk data(1000+) along with some valid results at the beginning.
The text was updated successfully, but these errors were encountered: