Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Adobe Target
Let's Encrypt
PayPal
YouTube
Adobe Audience Manager
Adobe Dynamic Tag Management
Adobe Experience Cloud
Adobe Fonts (Typekit)
Adobe Helix RUM
Braintree
Font Awesome
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
Microsoft Clarity
New Relic
Sentry
Active incidents
ShareThis
Vimeo
Google Cloud
Certificate Information
Subject
CN=myscsolutions.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
June 29, 2026
Valid Until
September 27, 2026
51 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C6:B5:35:89:11:2A:7E:16:5C:29:77:94:3C:C2:5F:4B:5A:48:5D:A9:4B:A3:C6:B1:D9:28:B8:6C:9D:F2:CA:BC
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=31557600
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
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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