Too short -t (timeout) can lead to false positives.

[mitchellkrogza]

@funilrys see - mitchellkrogza/The-Big-List-of-Hacked-Malware-Web-Sites@e0a15f6

[mitchellkrogza]

@funilrys I am not 100% convinced timeout is the cause of this. I think some registries are limiting lookups so on one run I get a positive hit "active" and then then later in the day on same domain I get a negative hit "inactive". I think, not sure of how you've coded this though, that if there is any failure on a whois lookup the nslookup result should be the winner.

[funilrys]

Yes but if we don't pass whois, nslookup is still there to tell us the status

[mitchellkrogza]

👍 ok gotya. Actually this just proves how accurate funceble is and how my brain was not working (lazy) to test why I got one INACTIVE after it was previously ACTIVE.

That's because the site http:https://matchgallery.homeandgardeningarticles.co.uk/6514626a35adfb3fa6f1d3f3c0a10fcf/login.php has been pulled offline 👍 so ...... funceble RULES !!!!

[funilrys]

So this is not an issue anymore 😸

Closing.

[mitchellkrogza]

100% ..... funceble is doing exactly what it was designed to do .... find dead domains and boy oh boy you have done some amazing work on this.