Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Ahrefs
AWS
Bing
BootstrapCDN
Cloudflare CDNJS
Cloudflare Web Analytics
DataTables
Facebook
Font Awesome
GlobalSign
Active incidents
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
Google Translate
jQuery
jsDelivr
Microsoft Clarity
Stripe
Twitter
unpkg
Yahoo
YouTube
Zendesk
Google Cloud
Certificate Information
Subject
CN=*.value-domain.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign GCC R3 DV TLS CA 2020
Valid From
June 03, 2025
Valid Until
July 05, 2026
89 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3F:6C:A8:99:91:05:1A:9F:DA:C0:C3:A7:CE:42:30:A6:EB:FC:B5:E8:BE:B6:01:CC:9A:B8:B6:D2:7C:24:AD:CD
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
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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