From 0b186333e135246d3601949c3347e40bd7e4cf5a Mon Sep 17 00:00:00 2001 From: Eduard Tolosa Date: Mon, 5 Oct 2020 15:32:13 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index b4ac782..eccc32a 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ FHC try to resolve https first, if this fails then fallback to http, in that way FHC is **very** resource friendly, you can use up to 1000 threads in an single core machine and this will work without any problem, the bottleneck for this tool is your network speed. By default, FHC is able to perform HTTP check for ~76 hosts per second in good network conditions (tested in an Google Cloud machine). Depending on how much host have only http (not https) and/or are alive the number of host resolved in average can be higher as the tool doesn't have to perform an double check. In our demo we used an real-world scenario performing resolution for all the `facebook.com` subdomains. ## Demo -[![asciicast](https://asciinema.org/a/363351.svg)](https://asciinema.org/a/363351) +[![asciicast](https://asciinema.org/a/363640.svg)](https://asciinema.org/a/363640) # Installation