Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=California, L=San Francisco, O=Salesforce, Inc., CN=salesforce-sites.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1
Valid From
September 16, 2025
Valid Until
September 14, 2026
312 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
30:80:71:46:A0:CE:E1:77:5C:5E:B3:1D:05:29:1F:E6:03:BD:61:B8:9D:24:D2:8C:FE:B9:EF:FB:E4:76:36:E2
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=86400
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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
Subject Alternative Names
19 domains
salesforce-communities.com
cloudforce.com
database.com
documentforce.com
force-user-content.com
forceusercontent.com
lightning.com
salesforce-experience.com
salesforce-hub.com
salesforce-scrt.com
salesforce-setup.com
salesforce-sites.com
salesforceliveagent.com
salesforcescrt.com
sfdcopens.com
site.com
siteforce.com
www.siteforce.com
visualforce.com
Other domains in certificate