Open
Cached
·
just now
84/100
SECURITY SCORE
Certificate Information
Subject
CN=documentation.mobileforcesoftware.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 31, 2025
Valid Until
March 31, 2026
78 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
D5:56:B0:88:60:4A:DC:7E:6E:AE:DA:D8:B5:4F:42:62:E8:99:1B:DF:B4:97:65:02:E3:01:DA:F6:DA:E0:23:20
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), autoplay=(*), camera=(*), clipboard-write=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(*), midi=(), payment=(), usb=(), fullscreen=(*)
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
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