Open
Cached
·
just now
95/100
SECURITY SCORE
Certificate Information
Subject
CN=dcatz.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
December 03, 2025
Valid Until
March 03, 2026
44 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BF:19:EE:52:CA:E6:74:EF:E6:B7:87:49:09:6F:08:98:45:3C:76:BC:7A:39:6C:FF:FE:F4:7C:F5:FC:22:79:86
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=63072000; includeSubDomains; preload
Content-Security-Policy
Good
default-src; base-uri; font-src; +8 more
default-src 'self'; base-uri 'self'; font-src 'self' data:; img-src 'self' https: data: blob:; object-src 'none'; script-src 'self' 'unsafe-inline' https://*.clerk.com https://*.clerk.services https://*.clerk.accounts.dev https://clerk.dcatz.com https://dcatz-a4569-default-rtdb.asia-southeast1.firebasedatabase.app; style-src 'self' 'unsafe-inline'; worker-src 'self' blob:; connect-src 'self' https://*.openai.azure.com https://api.exa.ai https://*.firebaseio.com wss://*.firebaseio.com https://*.firebasedatabase.app wss://*.firebasedatabase.app https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://www.googleapis.com https://apis.google.com https://*.clerk.com https://*.clerk.services https://*.clerk.accounts.dev wss://*.clerk.accounts.dev wss://*.clerk.services https://clerk.dcatz.com wss://clerk.dcatz.com https://clerk-telemetry.com; frame-src 'self' https://*.clerk.com https://*.clerk.services https://*.clerk.accounts.dev https://clerk.dcatz.com; frame-ancestors 'none'
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), camera=(), geolocation=(), microphone=(), usb=()
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