Open
Cached
·
just now
83/100
SECURITY SCORE
Certificate Information
Subject
CN=republic.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 11, 2026
Valid Until
April 11, 2026
84 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
1E:3B:E4:71:31:0A:63:BC:68:5A:36:FE:07:A7:F5:4F:B1:9B:87:DD:D3:50:0D:06:1F:8A:32:3C:C8:55:31:E1
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=15552000; preload
Content-Security-Policy
Basic
default-src; font-src; img-src; +9 more
default-src 'self' https:; font-src 'self' https: data: 'unsafe-inline'; img-src 'self' https: http: data: blob:; object-src 'none'; worker-src 'self' blob: data: https:; style-src 'self' https: 'unsafe-inline' 'unsafe-eval' data: fast.fonts.net; child-src 'self' blob: data: https:; media-src 'self' blob: data: https:; base-uri 'self'; connect-src 'self' https: data:; report-uri https://csp-report.browser-intake-datadoghq.com/api/v2/logs?dd-api-key=pub467dca44a41d8d41082204dce8e56cbe&dd-evp-origin=content-security-policy&ddsource=csp-report&ddtags=r-client%2Cenv-production; script-src 'strict-dynamic' 'unsafe-inline' https: http: blob: 'unsafe-hashes' 'nonce-DhcnhD3khTMePgXw' 'sha256-rRMdkshZyJlCmDX27XnL7g3zXaxv7ei6Sg+yt4R3svU=' 'sha256-lo7ZdP6kFds+wf1WMWvn7MhcFVFJV44kAXODRevzRZ8='
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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