Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
33Across
AdRoll
AWS Certificate Manager
Microsoft Advertising
BootstrapCDN
Cloudflare CDNJS
Facebook
Fullstory
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Sign-In
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
Intercom
jsDelivr
LinkedIn
Microsoft Clarity
PostHog
Reddit
Scalar
Segment
unpkg
Zendesk
ZoomInfo
Certificate Information
Subject
CN=app.edgedelta.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
November 17, 2025
Valid Until
December 16, 2026
218 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BE:7A:E0:9B:8E:70:AB:1C:C8:10:3E:A9:8C:26:10:34:98:6D:13:AD:C3:68:DE:E7:41:BA:8F:9A:2B:B5:31:84
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
Present
max-age=63072000; includeSubdomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), microphone=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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