Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
PayPal
Adyen
BootstrapCDN
Crazy Egg
Font Awesome
GlobalSign
Google Analytics
Google DoubleClick
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
jQuery
jsDelivr
OneTrust
OptinMonster
Salesforce Cloud
Salesforce Sites
Sitefinity
6sense
Stripe
unpkg
YouTube
Google Cloud
Certificate Information
Subject
C=US, ST=Massachusetts, L=Burlington, O=Progress Software Corporation, CN=*.smartlogic.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign RSA OV SSL CA 2018
Valid From
August 12, 2025
Valid Until
September 13, 2026
114 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
18:12:43:96:88:1E:89:5F:02:8B:3A:76:A1:71:9D:4E:63:1D:BB:EF:C8:4F:52:01:A9:17:DC:34:DB:FD:BE:CA
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=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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