Socket timeout when test heartbleed

[malaikuangren]

All, I tried to test my site(https://192.168.2.104) if there exist vulnerability of heartbleed but got the socket time out problem. Please help to review below out put.

CHECKING HOST(S) AVAILABILITY

---

192.168.2.104:443 => 192.168.2.104:443

SCAN RESULTS FOR 192.168.2.104:443 - 192.168.2.104:443

---

Unhandled exception when processing --heartbleed:
socket.timeout - timed out

I am sure my site (https://192.168.2.104) can be reached in the network.
Is there any reason cause this exception?

Thanks,
Joe

[nabla-c0d3]

The test for heartbleed is not 100% reliable and may trigger a timeout. The methodology used by SSLyze is described here: https://blog.mozilla.org/security/2014/04/12/testing-for-heartbleed-vulnerability-without-exploiting-the-server/

[six8]

Is the timeout an indication that the server is not vulnerable? This times out every time for me.

[mhuuhka]

im getting the timeout aswell. Would be nice to get an answer to earlier question.

[nabla-c0d3]

This was fixed in #217

[glestel]

With the migration to 1.1.1. I'm getting [u'Unhandled exception while running --heartbleed:', u'timeout - timed out'] on a domain that never triggered error with previous version

[ericrange]

this "exception" is already in 1.0.0
but as @nabla-c0d3 said, you get an exception if u are not vulnerable to heartbleed.

[nabla-c0d3]

@glestel can you post or send me the domain? I am working on a better fix in the raw-tls-parsing branch so I want to try it.

[glestel]

Sent you a mail with domains of interest