Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
Adobe Marketo
Amplitude
Amazon S3
Beamer
Cloudflare CDNJS
Crazy Egg
Google Analytics
Google DoubleClick
Google Fonts
Google Maps
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
Heap
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
LaunchDarkly
Active incidents
LinkedIn
Pusher
Segment
Sentry
Stripe
Wistia
YouTube
Google Cloud
Certificate Information
Subject
CN=ionic.io
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 19, 2026
Valid Until
June 17, 2026
43 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
37:0E:00:06:19:F6:B3:4E:7A:7A:C8:90:E5:9B:D7:6E:F7:A6:2A:99:C6:4A:3C:8E:AC:01:15:2A:0B:35:1B:7A
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=15552000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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