This skips loading sslyze data when the result is {"invalid": true} (which will inevitably happen on some % of scans during a large run), and don't count them towards a %.
Without this, this was causing Pulse to incorrectly assume/display that domains were using SSLv2, SSLv3, and RC4.
This skips loading
sslyzedata when the result is{"invalid": true}(which will inevitably happen on some % of scans during a large run), and don't count them towards a %.Without this, this was causing Pulse to incorrectly assume/display that domains were using SSLv2, SSLv3, and RC4.