Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
UNKNOWN={:asn1_OPENTYPE, <<19, 2, 78, 76>>}, 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=24283498, C=NL, ST=Zuid-Holland, L=Spijkenisse, O=Tintel B.V., CN=pay.nl
Issuer
C=NL, O=PerfectSSL, CN=PerfectSSL
Valid From
January 15, 2025
Valid Until
February 15, 2026
47 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
49:22:E8:ED:76:B4:5A:57:B5:E2:5B:4E:E9:98:5B:F4:7A:07:AE:81:72:EC:8A:AB:AC:E0:D6:46:29:4B:1B:4C
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000
Content-Security-Policy
Weak
upgrade-insecure-requests
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Not Authorized
(Potential misconfiguration)
Authorized CAs
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
sectigo.com
visa.com
digicert.com
; cansignhttpexchanges=yes
geotrust.com
Incident Reporting
mailto:[email protected]
CAA Issues
- • CRITICAL: Current certificate issuer 'C=NL, O=PerfectSSL, CN=PerfectSSL' is NOT authorized by CAA records. Authorized CAs: letsencrypt.org, pki.goog; cansignhttpexchanges=yes, sectigo.com, visa.com, digicert.com; cansignhttpexchanges=yes, geotrust.com
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 6 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'issuewild' records to control wildcard certificate issuance