Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
YouTube
Microsoft Advertising
ClearBit
Cloudflare CDNJS
Active incidents
Cookiebot
Facebook
G2
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
jsDelivr
Libsyn
LinkedIn
LiveChat
Reddit
Storylane
Tapad
Typeform
Yoast
Google Cloud
Certificate Information
Subject
CN=zerospam.ca
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 30, 2026
Valid Until
June 28, 2026
60 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
13:9B:20:3E:03:A1:DF:70:D5:2B:F9:0C:0B:0F:5C:01:A5:2E:87:E2:BF:5D:0A:D8:57:3D:6B:F3:65:07:62: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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(), camera=(), microphone=(); +2 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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