Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=chat.uclone.net
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
October 22, 2025
Valid Until
January 20, 2026
59 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BD:D0:80:73:63:E7:4B:2E:50:1C:87:A5:C2:E7:F7:8E:7B:28:2D:80:40:E2:B7:5C:CC:97:72:1F:DE:B7:25:16
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Basic
script-src; style-src; img-src; +2 more
script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net/ www.googletagmanager.com/ tagmanager.google.com/ tagassistant.google.com/ www.google.com/ www.googleadservices.com/ googleads.g.doubleclick.net/ pagead2.googlesyndication.com/ cdn.rudderlabs.com/ fundingchoicesmessages.google.com/ ep2.adtrafficquality.google/ www.clarity.ms/ *.clarity.ms/ js.stripe.com/v3; style-src 'self' 'unsafe-inline' cdn.jsdelivr.net/ fonts.googleapis.com/; img-src 'self' data: https:; font-src 'self' data: fonts.gstatic.com/; connect-src 'self' cdn.jsdelivr.net/ www.google.com/ www.googletagmanager.com/ www.googleadservices.com/ googleads.g.doubleclick.net/ pagead2.googlesyndication.com/ cdn.rudderlabs.com/ www.google-analytics.com/ region1.google-analytics.com/ region1.analytics.google.com/ www.clarity.ms/ *.clarity.ms/ stats.g.doubleclick.net/;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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