Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
SurveyMonkey
Gravatar
AWS CloudFront
Google AdSense
Google Tag Manager
G2
Google Hosted Libraries
AppNexus (Xandr)
Yahoo
Liveramp
Advertising.com
Google DoubleClick
AdRoll
Google Analytics
Google Conversion Tracking
ClearBit
Pusher
Segment
Google Static File Front End
LaunchDarkly
Outbrain
Google Fonts
LinkedIn
PubMatic
Google Search
Facebook
Amazon S3
TripleLift
Taboola
AWS Certificate Manager
Rubicon Project
MNTN
Vimeo
HubSpot
Intercom
Paddle
Font Awesome
Google Cloud
Certificate Information
Subject
CN=api.tenet.textexpander.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
September 03, 2025
Valid Until
October 01, 2026
151 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F8:6C:DF:AD:58:D4:CA:BA:C0:30:B4:0A:30:46:42:EF:04:09:DB:16:FA:F7:95:90:9F:57:9A:E1:5D:60:3C:95
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), autoplay=(); +15 more
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