When you scan TLS-servers, we have to take the TLS-server reliability/stability into account (latency, speed, losses, etc). We can test it manually with tools like ping/curl and so on. But it makes the process much harder (we have to associate domains with their ip-addresses, write scripts...).
Proposal
Let's add options like -test-ping, -test-speed, -test-repeats and calculate min/avg/max/mdev of the repeats. Also we can add options to set bounds/limits of these test results to change feasible status according to them.
Problem
When you scan TLS-servers, we have to take the TLS-server reliability/stability into account (latency, speed, losses, etc). We can test it manually with tools like ping/curl and so on. But it makes the process much harder (we have to associate domains with their ip-addresses, write scripts...).
Proposal
Let's add options like
-test-ping,-test-speed,-test-repeatsand calculate min/avg/max/mdev of the repeats. Also we can add options to set bounds/limits of these test results to change feasible status according to them.