Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=www.reforge.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 22, 2025
Valid Until
March 22, 2026
48 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
BB:C1:88:46:24:47:D2:93:F4:4E:42:F5:57:3B:B1:5F:20:5D:14:9E:B9:4B:61:92:0D:21:32:74:AF:33:9F:7B
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
Weak
max-age=0; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Present
ALLOW-FROM https://edu.reforge.com https://reforge.docebosaas.com https://reforgesandbox.docebosaas.com
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
- • Significantly strengthen CSP directives
- • 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