Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
AWS
Microsoft Advertising
Cloudsmith
Cookiebot
Datadog
Firebase
Google AdSense
Google Conversion Tracking
Google DoubleClick
Google Maps
Google reCAPTCHA
Google Search
Google Static File Front End
Google Translate
jsDelivr
LinkedIn
Qualified
Sentry
Simple Analytics
Statuspage
Stripe
Vercel
YouTube
Zendesk
Google Cloud
Certificate Information
Subject
CN=app.cloudsmith.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 09, 2026
Valid Until
June 07, 2026
35 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B2:1E:86:B4:1A:07:03:4F:42:C0:EE:F3:9F:FE:99:5E:66:31:8E:47:D1:1F:1F:41:47:02:23:43:25:DD:8D:39
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=63072000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
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
- • Strengthen CSP by removing 'unsafe-eval'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add X-Content-Type-Options: nosniff
- • 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
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance