Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=lowcarbprogram.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 28, 2025
Valid Until
March 28, 2026
71 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
23:B2:C3:99:9C:3F:D0:3B:DA:44:4A:7C:61:C8:9B:D2:AD:28:26:8E:60:61:8C:D3:8C:03:42:D2:1D:AD:F1:B3
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
Basic
default-src; script-src; style-src; +4 more
default-src 'self' *.diabetes.co.uk *.vimeo.com *.akamaized.net; script-src 'self' 'unsafe-inline' 'unsafe-eval' *.statuspage.io *.googletagmanager.com *.facebook.com *.facebook.net *.gstatic.com *.google-analytics.com *.twitter.com *.google.com *.ads-twitter.com *.pusher.com *.amazonaws.com *.google-analytics.com *.googleapis.com *.cloudflareinsights.com *.googleadservices.com *.taboola.com *.stripe.com; style-src 'self' 'unsafe-inline' *.googleapis.com *.amazonaws.com *.gstatic.com; img-src * data:; font-src 'self' *.gstatic.com *.amazonaws.com; frame-src *.vimeocdn.com *.google.com *.statuspage.io *.vimeo.com vimeo.com *.youtube.com *.akamaized.net *.stripe.com; connect-src 'self' *.google.com *.lowcarbprogram.com *.doubleclick.net *.diabetes.co.uk *.pusher.com *.taboola.com ws.pusherapp.com *.google-analytics.com *.googleapis.com *.cloudflareinsights.com *.facebook.com *.facebook.net *.googleadservices.com *.stripe.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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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