Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Gravatar
Amazon S3
Bing
Clickagy
Google Analytics
Google DoubleClick
Google Fonts
Google Search
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot CMS
HubSpot Forms
HubSpot Live Chat
jQuery
jsDelivr
LinkedIn
Microsoft Clarity
NitroPack
OneTrust
unpkg
Vimeo
Yoast
YouTube
ZoomInfo
Certificate Information
Subject
CN=valueblue.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 23, 2026
Valid Until
July 22, 2026
45 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
A0:B3:6A:1B:6A:70:E8:45:78:D6:08:69:10:D6:EA:40:A2:95:B1:4E:35:B9:39:35:09:42:95:28:1E:96:58:9F
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(), midi=(), sync-xhr=(); +6 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