Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Bing
BootstrapCDN
Capterra
Cloudflare
Active incidents
Cloudflare CDN
Cookiebot
Crisp
Disqus
Facebook
GitHub
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
Instagram
jQuery
jsDelivr
Microsoft Clarity
New Relic
RawGit
TikTok
Twitter
unpkg
Google Cloud
Certificate Information
Subject
CN=sendpulse.ua
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 24, 2026
Valid Until
July 23, 2026
79 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
6A:94:1F:0B:55:DE:D1:9A:22:2A:94:D4:DB:B5:28:B2:C5:50:65:1A:3E:C9:D9:28:39:3E:8E:C5:57:5E:35:59
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
Missing
Not configured
Permissions-Policy
Present
interest-cohort=()
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'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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