Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN=34128261, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 78, 76>>}, 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>>}, C=NL, ST=Overijssel, O=Your Hosting B.V., CN=yourhosting.nl
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA EV R36
Valid From
April 24, 2025
Valid Until
May 18, 2026
117 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
E5:D6:D7:60:8E:82:45:C9:ED:E9:F5:6A:29:E9:22:B1:B8:59:2F:4F:17:DA:36:D2:CD:F3:0A:AB:9F:CB:82:0D
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=63072000; preload;
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(self)
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
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