Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
AWS
Active incidents
Bugsnag
Dropbox
Facebook
Font Awesome
Fullstory
GitHub
Google Analytics
Google Cloud Storage
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
Intercom
jQuery
jsDelivr
New Relic
Pusher
Sentry
Vimeo
YouTube
Google Cloud
Certificate Information
Subject
CN=figured.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 23, 2026
Valid Until
July 22, 2026
73 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
5F:EF:4A:AA:92:B9:2F:73:16:14:44:4D:FC:A9:14:25:84:C9:F2:6C:09:E7:4E:01:63:B9:07:1A:63:66:8B:BF
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
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
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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