Open
Cached
·
just now
79/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 68, 69>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 19, 78, 111, 114, 100, 114, 104, 101, 105, 110, 45, 87, 101, 115, 116, 102, 97, 108, 101, 110>>}, UNKNOWN={:asn1_OPENTYPE, "\f\vDüsseldorf"}, UNKNOWN={:asn1_OPENTYPE, <<12, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN=HRB 97562, C=DE, ST=Nordrhein-Westfalen, L=Düsseldorf, O=HSBC Trinkaus & Burkhardt GmbH, CN=signpost.hsbc.de
Issuer
C=US, O=DigiCert Inc, CN=DigiCert EV RSA CA G2
Valid From
September 07, 2026
Valid Until
March 24, 2027
160 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A4:79:BB:62:03:96:E1:F3:47:7C:35:C6:76:93:04:7E:52:75:5F:9F:B2:24:87:25:E4:7D:D8:22:89:9E:42:CF
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports