Search results

sslyze --tlsv1_2 10.47.8.50 doesn't discover any cipher suite

Status: Open.

#698 In nabla-c0d3/sslyze;

· jmls22 opened on Apr 24, 2025

Failing SSL2.0 test when using client credentials

Status: Open.

#693 In nabla-c0d3/sslyze;

· spyroskousidis opened on Mar 5, 2025

Scan with no SNI

Status: Open.

#690 In nabla-c0d3/sslyze;

· nettnikl opened on Jan 19, 2025

scan discarded with tls1_3 only website

Status: Open.

#689 In nabla-c0d3/sslyze;

· blshkv opened on Jan 15, 2025

Different results with sslyze 6.1.0

Status: Open.

#688 In nabla-c0d3/sslyze;

· friedelwolff opened on Jan 8, 2025

Ability to use a custom TLS configuration profile instead of Mozilla's

Status: Open.

#686 In nabla-c0d3/sslyze;

· nabla-c0d3 opened on Jan 2, 2025

Check for the signature algorithms supported by the server

new-check

Status: Open.

#685 In nabla-c0d3/sslyze;

· nabla-c0d3 opened on Dec 27, 2024

"CryptographyDeprecationWarning: Parsed a negative serial number, which is disallowed by RFC 5280"

blocked

Status: Open.

#656 In nabla-c0d3/sslyze;

· thbar opened on Jul 13, 2024

Memory Leak still seems to be present when running in Python

Status: Open.

#603 In nabla-c0d3/sslyze;

· lcurtis-datto opened on May 31, 2023

Integrate badkeys to check public keys from TLS certificates

Status: Open.

#567 In nabla-c0d3/sslyze;

· nabla-c0d3 opened on May 14, 2022

Implement GitHub Action on marketplace for running SSLyze from CI/CD

Status: Open.

#539 In nabla-c0d3/sslyze;

· nabla-c0d3 opened on Nov 26, 2021

Re-enable unit tests for Mozilla config on badssl.com

Status: Open.

#537 In nabla-c0d3/sslyze;

· nabla-c0d3 opened on Nov 26, 2021