Open
Cached
·
just now
93/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 80, 76>>}, UNKNOWN={:asn1_OPENTYPE, "\f\rwielkopolskie"}, UNKNOWN={:asn1_OPENTYPE, "\f\aPoznań"}, UNKNOWN=0000352235, C=PL, L=Poznań, O=PSP Polska Sp. z o.o., CN=secure.espago.com
Issuer
C=PL, O=Asseco Data Systems S.A., CN=Certum EV TLS G2 R39 CA
Valid From
January 26, 2026
Valid Until
January 23, 2027
330 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
36:2F:8E:20:E5:29:9D:04:67:00:E9:7D:4B:01:2E:D2:52:AD:B0:91:96:6D:FF:D8:90:B0:40:B2:8E:DF:85:1B
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Consider adding Permissions-Policy to control browser features
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