Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=dev.doorjames.app
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
November 03, 2025
Valid Until
February 01, 2026
81 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F0:84:E4:9C:B8:FD:3B:D7:D0:CF:1B:D6:BB:96:7A:8E:F0:E3:DB:99:2D:42:A4:AA:BE:CF:BF:AE:F3:8C:AA:17
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Good
frame-src; frame-ancestors; default-src; +5 more
X-Frame-Options
Present
ALLOW-FROM https://teams.microsoft.com/
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
vibrate=(self "https://doorjames.dev")
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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