Wildcard SSL Certificate detection #56
Labels
Priority: Low
This issue can probably be picked up by anyone looking to contribute to the project, as an entry fix
Status: Completed
Nothing further to be done with this issue. Awaiting to be closed.
Type: Enhancement
Most issues will probably ask for additions or changes.
Please describe your feature request:
This is more of a feature for data analysis; currently two types of wildcard certificate are issuesd:
*.cn
)*.san
)CLI Option:
-wc, -wildcard-cert display wildcard certificate
Example run with JSON output:
{ "timestamp": "2022-07-19T16:24:59.085676+05:30", "host": "expired.badssl.com", "ip": "104.154.89.105", "port": "443", "probe_status": true, + "wildcard_certificate": true, "tls_version": "tls12", "cipher": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256", "expired": true, "not_before": "2015-04-09T00:00:00Z", "not_after": "2015-04-12T23:59:59Z", "subject_dn": "CN=*.badssl.com, OU=PositiveSSL Wildcard, OU=Domain Control Validated", "subject_cn": "*.badssl.com", "subject_an": [ "*.badssl.com", "badssl.com" ], "issuer_dn": "CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, ST=Greater Manchester, C=GB", "issuer_cn": "COMODO RSA Domain Validation Secure Server CA", "issuer_org": [ "COMODO CA Limited" ], "fingerprint_hash": { "md5": "67344e61c0431cf1f7257c1d6de7a785", "sha1": "404bbd2f1f4cc2fdeef13aabdd523ef61f1c71f3", "sha256": "ba105ce02bac76888ecee47cd4eb7941653e9ac993b61b2eb3dcc82014d21b4f" }, "tls_connection": "ctls", "sni": "expired.badssl.com" }
Example run with CLI output:
Detection logic:
if
subject_cn || subject_an
contains*.
,wildcard_certificate == true
The text was updated successfully, but these errors were encountered: