Jorge Matricali

Workaround: Adding default response ``` responses: { default: {}, 200: { description: 'This is a success response', bodyType: 'Product', }, }, ```

Related to #20 I haven't had the time to research how to detect SonicWall footprint

@Little-Potato01 can you help me testing against branch `20-detect-sonicwall-ssh`? Thanks in advance

I'm needing more info I've tested against trusted SSH servers and got correct results both for correct and invalid credentials

Working on this

> Hello. Is this issue fixed yet? Partially, you can test the branch `20-detect-sonicwall-ssh`

One way to avoid this could be to use the --check-http flag to do an additional check and discard false positives.