Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=mcp.dub.sh
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
November 08, 2025
Valid Until
February 06, 2026
51 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
69:37:09:A8:46:CC:EC:46:36:7F:18:4F:EF:BD:03:EF:4A:BA:2D:00:B1:CB:53:8C:A8:30:D8:79:3F:36:FB:78
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
base-uri; connect-src; default-src; +10 more
base-uri 'none'; connect-src 'self' https://metrics.speakeasy.com https://browser-intake-datadoghq.com https://*.usepylon.com wss://*.pusher.com https://*.pusher.com https://*.posthog.com; default-src 'self'; font-src 'self' https://fonts.googleapis.com https://fonts.gstatic.com https://*.usepylon.com https://*.posthog.com; frame-ancestors 'self'; frame-src 'self' https://polar.sh https://*.polar.sh; img-src 'self' blob: https: android-webview-video-poster: data:; media-src 'self' https://*.posthog.com; object-src 'none'; script-src 'self' 'wasm-unsafe-eval' https://www.datadoghq-browser-agent.com https://metrics.speakeasy.com https://widget.usepylon.com https://*.posthog.com https://*.getgram.ai; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://*.usepylon.com https://*.posthog.com; worker-src 'self' blob:; report-to browser-intake-datadoghq
X-Frame-Options
Excellent
deny
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
fullscreen=(), compute-pressure=(), camera=(), microphone=(), geolocation=(), accelerometer=(), bluetooth=(), gyroscope=(), payment=(), usb=(), midi=(), magnetometer=()
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