Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Gravatar
Let's Encrypt
YouTube
AddToAny
ClearBit
Cloudflare CDNJS
Demandbase
Facebook
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
hCaptcha
Hotjar
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot Forms
Active incidents
LinkedIn
Microsoft Clarity
Navattic
ZoomInfo
Google Cloud
Certificate Information
Subject
CN=sphereboard.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 04, 2026
Valid Until
July 03, 2026
61 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
09:20:84:5A:EC:5B:23:F6:07:C1:54:21:92:FF:51:FF:2C:17:20:64:7B:44:09:4C:84:EB:BD:74:A5:D9:74:61
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 env=HTTPS
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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