Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Google AdSense
Google Tag Manager
Bing
AppNexus (Xandr)
Midbound Cloud
Liveramp
SoundCloud
Megaphone
Google DoubleClick
Google Analytics
Google Conversion Tracking
6sense
Greenhouse
Google Static File Front End
Google Fonts
Twitter
LinkedIn
ZoomInfo
Influ2
Google Search
Adobe Marketo
Qualified
Facebook
AWS
Active incidents
Vimeo
TrustArc
YouTube
The Trade Desk
Microsoft Clarity
Font Awesome
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=trust.reltio.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
April 29, 2026
Valid Until
July 28, 2026
42 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
AC:B6:C3:8B:EF:16:9E:70:43:1C:AB:59:3D:2E:23:F7:3D:02:A9:0F:65:FC:78:20:09:9D:CE:A8:BD:7B:C5:2B
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
no-referrer-when-downgrade
Permissions-Policy
Present
microphone=(self "https://app.qualified.com")
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