Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
PayPal
YouTube
Adobe Marketo
Adyen
Arcade
Arkose Labs
Beamer
Brightcove
Cloudinary
DigiCert
DocuSign
Embedly
Formstack
Google Cloud Storage
Google Fonts
Google Pay
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Highspot
LinkedIn
Mixpanel
Okta
Pendo
Salesforce Cloud
Salesforce Sites
Stripe
Vidyard
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
C=US, ST=California, L=San Francisco, O=Okta, Inc., CN=support.okta.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
December 15, 2025
Valid Until
January 05, 2027
135 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2D:14:99:DA:44:F4:DD:2F:52:0D:BA:A0:75:3D:FB:89:07:5D:F3:D2:23:97:5E:C0:38:A1:8D:EF:A9:3D:67:A8
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