Open
Cached
·
55m ago
88/100
SECURITY SCORE
Certificate Information
Subject
CN=namebright.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 26, 2025
Valid Until
March 26, 2026
72 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
49:A7:3A:06:1E:DB:0A:D6:5E:59:81:43:79:0F:CD:BC:32:65:D4:5A:76:21:2A:D6:56:A4:90:42:71:64:6D:D5
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; includeSubDomains; preload
Content-Security-Policy
Good
default-src; img-src; object-src; +9 more
default-src 'none'; img-src 'self' * data:; object-src 'none'; font-src 'self' fonts.gstatic.com data:; script-src 'self' https://*.gstatic.com https://*.google.com https://*.getsitecontrol.com https://*.googletagmanager.com https://*.google-analytics.com https://*.doubleclick.net https://*.adroll.com https://*.statcounter.com https://*.facebook.net 'unsafe-inline'; style-src 'self' 'unsafe-inline' fonts.googleapis.com https://*.googletagmanager.com; base-uri 'self'; form-action 'self'; connect-src 'self' https://*.getsitecontrol.com https://*.getsitectrl.com https://*.google.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://client.namebright.com https://logging.namebright.com https://*.statcounter.com https://*.launchdarkly.com; frame-src https://*.google.com www.youtube.com https://client.namebright.com https://www.namebright.com/assets/refresh-token.html; frame-ancestors https://client.namebright.com; media-src https://www.sitecdn.com
X-Frame-Options
Good
SAMEORIGIN
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
- • Strengthen CSP by removing 'unsafe-eval'
- • 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