Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
C=DE, ST=Rheinland-Pfalz, L=Montabaur, O=1&1 Mail & Media GmbH, CN=*.gmx.de
Issuer
C=DE, O=Deutsche Telekom Security GmbH, UNKNOWN={:asn1_OPENTYPE, <<12, 22, 78, 84, 82, 68, 69, 45, 68, 69, 82, 51, 50, 48, 49, 46, 72, 82, 66, 49, 53, 50, 52, 49>>}, CN=Telekom Security OV RSA CA 26A
Valid From
August 17, 2026
Valid Until
March 02, 2027
195 days
Public Key
RSA
3072 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
63:F8:69:15:7C:72:83:5C:29:C1:4E:6C:4E:AC:E0:8D:BC:33:20:98:98:7B:22:0E:7C:EE:5E:B9:FF:22:86:E6
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000; includeSubdomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
microphone=(), camera=(), geolocation=(); +1 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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