You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Key features
18
18
* Focus on speed and reliability: SSLyze is a battle-tested tool that is used to reliably scan **hundreds of thousands**
19
19
of servers every day.
20
20
* Easy to operationalize: SSLyze can be directly run from CI/CD, in order to continuously check a server against
21
-
Mozilla's recommended TLS configuration.
21
+
Mozilla's recommended TLS configurations.
22
22
* Fully documented [Python API](https://nabla-c0d3.github.io/sslyze/documentation/) to run scans directly from any
23
23
Python application, such as a function deployed to AWS Lambda.
24
24
* Support for scanning non-HTTP servers including SMTP, XMPP, LDAP, POP, IMAP, RDP, Postgres and FTP servers.
@@ -82,7 +82,20 @@ mozilla.com:443: FAILED - Not compliant.
82
82
* ciphers: Cipher suites {'TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384', 'TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256', 'TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256'} are supported, but should be rejected.
83
83
```
84
84
85
-
This can be used to easily run an SSLyze scan as a CI/CD step.
85
+
Alternatively, you can check against your own custom TLS configuration by providing a JSON file that follows Mozilla's TLS configuration format:
0 commit comments