Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
PayPal
Adobe Fonts (Typekit)
Amazon S3
Cloudflare
Cloudflare CDN
Facebook
Font Awesome
Forethought
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
LinkedIn
New Relic
Termly
Twitter
Vimeo
YouTube
Zendesk
Google Cloud
Certificate Information
Subject
CN=cofsab.ca
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
August 26, 2026
Valid Until
November 24, 2026
89 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FE:E1:26:ED:0D:73:84:AB:13:5E:AC:CA:06:67:BB:A2:74:14:9F:F2:A5:F2:F5:3F:C3:24:9A:FC:22:C5:65:77
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=31536000
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