Open
Cached
·
just now
78/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
Google Maps
Criteo
Google Tag Manager
Bing
Sovrn
Google reCAPTCHA
ShareThrough
RudderStack
Amazon Advertising
AppNexus (Xandr)
OpenX
Yahoo
Tapad
Liveramp
Tumblr
Advertising.com
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Cloudflare CDN
Basis Technologies
Google Static File Front End
Outbrain
Google API JS Client
RawGit
Google Fonts
Hotjar
PubMatic
GumGum
HubSpot Analytics
Teads
Yieldmo
Fastly
Google Search
Cloudflare
Active incidents
Facebook
StackAdapt
Snapchat
TripleLift
AWS
Active incidents
Taboola
Rubicon Project
Primis
Visual Website Optimizer
ipify
Google Optimize
N.Rich
HubSpot
Quora
YouTube
The Trade Desk
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
CN=*.livspace.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
April 06, 2026
Valid Until
July 05, 2026
56 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DC:99:B8:52:D3:46:74:6D:C9:62:5E:F5:B4:29:24:90:9E:2A:C7:24:4E:49:A0:5A:39:72:BE:BF:9A:CE:51:08
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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