[juxhindb]

Thank you!

> so you'd permutate the input domain and then query DNS?

Correct, we're running on resource-constrained lambdas right now and hoping to have some breathing room to expand on this soon. We want this to be the most accurate, point-in-time analysis of your domain so we want to push for this to run and scale rather than trying to tap into [expensive] data feeds.

> any caching mechanism in place? IMHO it'd be good to add some intro/info on the homepage.

Definitely, we had this prior with Cloudfront. As we're running on HTTP/2 stream, we simply cached the response and replayed it at the edge. We recently added signup/signin which complicated this so we've disabled it for the time. We're going to re-include it using Lambda@Edge shortly.

> Feedback, Make signing more visbile, currently you'd have to click login -> click on sign up

Noted!

> Feedback, I am expecting a paid premium after login but non, WIP?

Right now we're just giving access to more results after signin. We'll include CSV exports, some detailed results for free to help analysts. We're exploring premium features where you pay for recurring alerts about your domain with report history. Happy to hear what you feel are features you'd be happy to have included (and perhaps pay for?).

[ianmuscat]

Another reason it may feel a little bit slow is because the client is completing an invisible CAPTCHA challenge to curb bots/abuse (we may be able to improve this experience for authenticated users eventually)