Mzack9999

Considering the implementation complexity, I'm closing this as not planned for the time being

Usually, this is related to network stability. I'm unable to reproduce the issue against `google.com`. Would it be possible to share one of the domains generating different results each time...

Closing as not reproducible - The workaround is generally generating certificates with certbot and then just using them in interactsh

Marking as complete - It seems like there isn't a lot we can do as the verification mechanism requires the external verifier to query the interactsh server

@dependabot rebase

Please provide the steps to reproduce the behavior, at minimum the full command line and give an idea of how many targets you are scanning

I think this might be mostly related to the way `nuxt.js` renders the page (ref. https://stackoverflow.com/questions/48577766/nuxt-sites-not-getting-crawled) as apparently the DOM is not fully generated but only upon UI interactions (such...

With this feature you really risk to lose a lot of results that might be in the upper range of the threshold. Have you tried playing with the depth parameter?...

@dogancanbakir I believe the helper function was implemented in a few places to avoid using the go default user agent, which is filtered out in many cases

@crigger61 Thanks for opening this issue. Would it be possible to provide an example of the page which is not correctly parsed? Generally headless should be able to render all...