Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
YouTube
Google Tag Manager
Bing
OptinMonster
DigiCert
Google DoubleClick
Google Analytics
Google Conversion Tracking
Firebase
Albacross
Google Static File Front End
Calendly
Google API JS Client
Google Fonts
Cloudflare Web Analytics
Hotjar
Stripe
Google Search
BootstrapCDN
Yandex
Facebook
Amazon S3
Syncfusion
Crisp
Adobe Fonts (Typekit)
Moz
CookieYes
Cloudflare CDNJS
BoldDesk
Tawk.to
Microsoft Clarity
Font Awesome
GeoTrust
jsDelivr
Google Cloud
Certificate Information
Subject
C=US, ST=North Carolina, L=Morrisville, O=Syncfusion, Inc., CN=*.syncfusion.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
July 22, 2025
Valid Until
August 22, 2026
131 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
76:AE:8E:BE:39:0B:90:FD:8E:0D:22:71:7E:9D:14:5A:E0:3B:59:D8:EC:F0:29:A3:E1:6C:8C:4C:A0:7C:4B: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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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