Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS API Gateway
AWS CloudFront
YouTube
Adobe Fonts (Typekit)
AWS
AWS Certificate Manager
Bing
Calendly
Google AdSense
Google Analytics
Google API JS Client
Google Cloud Run
Google DoubleClick
Google Maps
Google Search
Google Tag Manager
Intercom
IP-API
jsDelivr
LinkedIn
Microsoft Clarity
Reddit
Sentry
Stripe
Twitter
Certificate Information
Subject
CN=getunblocked.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
January 08, 2026
Valid Until
February 06, 2027
279 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A7:E6:88:4A:98:FD:26:F7:E2:B8:AA:5A:E8:6E:1F:67:36:7F:18:A7:02:F0:FB:67:0B:79:1D:23:8F:11:BC:E0
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=15724800; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
fullscreen=(self), camera=(), microphone=(); +2 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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