Open
Cached
·
just now
76/100
SECURITY SCORE
Detected Technologies
Adobe Target
AWS CloudFront
PayPal
Adobe Audience Manager
Adobe Dynamic Tag Management
Adobe Experience Manager
Adyen
Microsoft Advertising
Cloudinary
DigiCert
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
jQuery
LinkedIn
Okta
Salesforce Cloud
Salesforce Sites
SendGrid
Slack
Statuspage
TrustArc
Twitter
Vimeo
YouTube
Google Cloud
Certificate Information
Subject
C=US, ST=California, L=Redwood City, O=Informatica LLC, CN=mysupport.informatica.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
May 20, 2025
Valid Until
June 03, 2026
24 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
24:3A:7B:6F:A2:F9:78:51:5D:F8:C8:8C:F4:1D:24:92:E8:32:F0:EC:C1:00:E0:E8:50:55:00:2B:5E:16:C8:DB
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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