Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google AdSense
Chili Piper
Pingdom
Google Tag Manager
Reprise
Google Hosted Libraries
AppNexus (Xandr)
Reddit
Midbound Cloud
Google DoubleClick
Google Analytics
Microsoft Advertising
Google Conversion Tracking
6sense
Datadog
Google Fonts
Wistia
Twitter
Hotjar
LinkedIn
Contentful
Influ2
Stripe
unpkg
Google Search
BootstrapCDN
Adobe Marketo
Facebook
Amazon S3
StackAdapt
OneTrust
AWS Certificate Manager
Akamai
Smartling
Intercom
Quora
YouTube
The Trade Desk
Sentry
jsDelivr
Certificate Information
Subject
CN=intr.cm
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
January 12, 2026
Valid Until
February 10, 2027
353 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
74:4A:D6:3F:75:32:E3:B8:65:EC:02:10:D5:7C:30:A2:0F:B4:73:AA:DC:4D:89:4C:49:9C:7D:5E:2D:B4:8E:14
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; 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
- • 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