Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
Brightcove
Google reCAPTCHA
Guideflow
Google DoubleClick
Arcade
Google Analytics
Typeform
Google Fonts
Vidyard
Wistia
Twitter
G Workspace
Loom
Entri
Stripe
Mapbox
Google Search
BootstrapCDN
Adobe Marketo
Microsoft SharePoint
Facebook
Amazon S3
OneTrust
Okta
Zuora
AWS Certificate Manager
Vimeo
JW Player
Intercom
The Trade Desk
Sentry
Certificate Information
Subject
CN=*.intercom.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
November 06, 2025
Valid Until
December 05, 2026
286 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8E:D1:45:4B:08:33:B9:D5:AF:2D:5D:FC:B4:AF:04:FF:B0:02:0C:29:B3:8D:D9:A5:91:38:A0:C4:51:C6:08:C3
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=31556952; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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
Subject Alternative Names
9 domains
intercom.com
*.intercom.com
fin.ai
*.fin.ai
intercom.io
*.intercom.io
intercom.news
*.intercom.news
intr.cm
Other domains in certificate