Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Bing
Microsoft Advertising
Cloudflare Turnstile
Cloudflare Web Analytics
DigiCert
Facebook
Fullstory
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Maps
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
LinkedIn
Microsoft Clarity
OneTrust
Thawte
Twitter
Uberall
YouTube
Google Cloud
Certificate Information
Subject
C=ES, L=Alcobendas, O=Acens Technologies SL, CN=*.hostalia.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=Thawte TLS RSA CA G1
Valid From
December 22, 2025
Valid Until
January 19, 2027
150 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
6F:67:A5:21:EB:DA:ED:D8:89:85:EE:7B:AF:A4:AF:3F:6B:EE:31:55:C6:D1:67:29:1F:A1:FC:42:E6:CD:6E:9B
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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