Open
Cached
·
just now
84/100
SECURITY SCORE
Detected Technologies
Gravatar
Let's Encrypt
AppNexus (Xandr)
Bing
Microsoft Advertising
BootstrapCDN
Facebook
Google Analytics
Google API JS Client
Google DoubleClick
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
hCaptcha
Hotjar
jQuery
LinkedIn
OpenX
Pingdom
PubMatic
Qualtrics
Trustpilot
Twitter
Typeform
Visual Website Optimizer
Yahoo
Zoho Mail
Google Cloud
Certificate Information
Subject
CN=console.vps.net
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
February 05, 2026
Valid Until
May 06, 2026
33 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DC:12:53:DF:FD:76:77:AA:AF:5D:38:F9:6E:88:3B:2C:96:B1:36:E7:F7:45:F2:DB:28:3B:C4:C0:7F:5F:68:F5
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
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 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