Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
PayPal
Google Trust
Google Maps
Google Tag Manager
Bing
Google Hosted Libraries
XING
Reddit
Capterra
OptinMonster
DigiCert
Google DoubleClick
Google Analytics
Firebase
Albacross
Google Cloud Storage
Google Static File Front End
Google API JS Client
RawGit
Twitter
Authorize.net
Cloudflare Web Analytics
Hotjar
LinkedIn
SVGator
Stripe
Google Search
BootstrapCDN
Yandex
Facebook
Syncfusion
Crisp
Adobe Fonts (Typekit)
CookieYes
Cloudflare CDNJS
AWS
Visual Website Optimizer
BoldDesk
Tawk.to
YouTube
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
CN=syncfusioninternal.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 24, 2026
Valid Until
June 22, 2026
69 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
87:D1:73:D9:24:B5:83:97:06:64:49:75:C8:48:52:B4:31:BD:8B:45:58:BB:E3:96:44:03:6B:E5:54:9B:8E:A0
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
No-referrer-when-downgrade
Permissions-Policy
Present
microphone=(self)
Recommendations
- • 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