Open
Cached
·
just now
85/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Google AdSense
Chili Piper
Dreamdata
Google Tag Manager
WP Engine
Bugsnag
G2
Spotify
SalesLoft
AppNexus (Xandr)
OpenX
Yahoo
Liveramp
HubSpot Forms
Capterra
JotForm
Advertising.com
Google DoubleClick
AdRoll
Google Analytics
ClearBit
Yoast
6sense
Active incidents
Basis Technologies
Google Static File Front End
Outbrain
Google Fonts
Vidyard
Clickagy
Twitter
Hotjar
LinkedIn
PubMatic
HubSpot CMS
ZoomInfo
HubSpot Analytics
TrustRadius
Google Search
Adobe Marketo
Demandbase
Facebook
Amazon S3
bunny.net
Active incidents
AddEvent
TripleLift
DigitalOcean Spaces
Influitive
Taboola
Google Optimize
HubSpot
Intercom
Font Awesome
HubSpot Live Chat
jsDelivr
Google Cloud
Google App Engine
Certificate Information
Subject
CN=www.influitive.com
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid From
July 18, 2026
Valid Until
October 16, 2026
79 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
EC:74:7F:E8:66:20:06:D9:05:92:63:5A:F7:5F:FF:BE:CC:A0:1B:D3:45:3E:56:82:5D:3B:CB:66:EA:59:BB:E0
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=63072000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
private-state-token-redemption=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com"), private-state-token-issuance=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com")
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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