Open
Cached
·
just now
84/100
SECURITY SCORE
Detected Technologies
Google Trust
Gravatar
YouTube
AdRoll
Cloudflare CDNJS
Cloudflare Web Analytics
Datadog
Facebook
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
SoundCloud
Spotify
TikTok Analytics
Twitter
Zoho Mail
Google Cloud
Certificate Information
Subject
CN=ultrashanghai.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 12, 2026
Valid Until
July 11, 2026
89 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
C5:70:E1:F1:75:85:4D:05:41:C4:4B:C0:79:9E:3F:4C:80:66:CB:AC:A1:FB:56:AB:A8:32:F1:D1:5B:3A:E7:7D
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
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Consider adding Permissions-Policy to control browser features
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