Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=community.vtrakit.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
December 01, 2025
Valid Until
March 01, 2026
34 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
45:88:64:F4:A8:BD:C6:B3:36:9B:9A:1D:9D:9E:BF:64:35:E1:FC:2E:65:C6:68:19:7C:36:40:11:07:6C:93:AC
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
Content-Security-Policy
Basic
upgrade-insecure-requests; base-uri; object-src; +4 more
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-S8eYOa0HNmF7G9Fp7PchAI6Qg' 'strict-dynamic' 'report-sample'; report-uri https://community.vtrakit.com/csp_reports; frame-ancestors 'self'; manifest-src 'self'
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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