Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=*.mobilecommons.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
October 12, 2025
Valid Until
November 10, 2026
281 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
02:74:44:8C:CB:92:83:86:7A:64:68:4B:1C:D9:C5:08:C7:B8:F3:CF:85:55:F9:EE:82:98:BF:B9:46:82:AD:4B
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=31536000; includeSubDomains
Content-Security-Policy
Basic
frame-src; font-src; manifest-src; +8 more
frame-src 'none';font-src 'self';manifest-src 'self';connect-src 'self' sso.mobilecommons.com;img-src 'self' sso.mobilecommons.com blob:;media-src 'none';frame-ancestors 'none';default-src 'none';script-src 'self' 'unsafe-eval';object-src 'none';style-src 'self' 'unsafe-inline'
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
payment=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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