Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Google Tag Manager
Sectigo
AppNexus (Xandr)
OpenX
Yahoo
Liveramp
Advertising.com
Trustpilot
Google DoubleClick
AdRoll
Google Analytics
Formstack
Outbrain
Twitter
PubMatic
Clicky
LiveChat
Stripe
ShareThis
Google Search
Facebook
TripleLift
Pinterest
Salesforce Pardot
Taboola
Vimeo
ipify
YouTube
The Trade Desk
Google Cloud Storage
Certificate Information
Subject
CN=*.crucial.com.au
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
June 11, 2025
Valid Until
June 11, 2026
40 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
B8:7F:45:67:AB:2E:CA:2E:35:C9:87:2A:E1:4A:35:E9:A1:CF:61:88:2B:13:5D:8B:7E:A1:3E:E0:C3:D2:D5:91
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=15552000;
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
- • Strengthen CSP by removing 'unsafe-eval'
- • 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