Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
AppNexus (Xandr)
Bing
BootstrapCDN
Cloudflare Turnstile
Cloudflare Web Analytics
DigiCert
Facebook
Google AdSense
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
jQuery
Microsoft Clarity
OneTrust
Thawte
Uberall
Yoast
YouTube
Google Cloud
Certificate Information
Subject
C=ES, L=Alcobendas, O=Acens Technologies SL, CN=acens.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Thawte TLS RSA CA G1
Valid From
October 15, 2025
Valid Until
November 15, 2026
196 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BC:CC:72:04:2A:3D:58:BC:6E:DF:0D:C3:F5:B9:7E:D2:72:07:CB:04:C5:5B:EF:96:30:6B:BC:04:0C:70:A0:1B
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=31536000
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
- • 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