Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Active incidents
Akamai
Active incidents
Brightcove
Font Awesome
Google AdSense
Google Analytics
Google Cloud Storage
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Maxio
OneTrust
Pendo
Salesforce Cloud
SoundCloud
Twitter
YouTube
Google Cloud
Certificate Information
Subject
CN=info.joc.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
May 04, 2026
Valid Until
August 02, 2026
81 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
42:4A:44:8A:D9:24:F5:ED:4C:4F:D3:1C:B2:74:C7:15:CB:99:71:41:4A:93:A7:CD:E8:59:EB:4D:E4:D2:59:D9
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
letsencrypt.org
; validationmethods=http-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/23216805
awstrust.com
digicert.com
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance