Open
Cached
·
4h ago
91/100
SECURITY SCORE
Detected Technologies
Google Trust
YouTube
Adobe Marketo
Ashby
Chili Piper
Contentful
Active incidents
Drift
Eventbrite
G2
GitHub
Google Analytics
Google Fonts
Google Optimize
Google Search
Google Tag Manager
G Workspace
Greenhouse
jQuery
Qualified
SurveyMonkey
Twitter
Vimeo
Visual Website Optimizer
Zoom
Active incidents
Google Cloud Storage
Certificate Information
Subject
CN=www.influxdata.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 27, 2026
Valid Until
July 26, 2026
88 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F8:D9:E9:53:2A:49:8C:D7:BB:E0:35:63:22:F8:B0:7E:0E:88:C6:F6:01:47:4F:DB:CE:61:44:F8:A3:20:5D:53
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
Good
max-age=31536000; includeSubDomains
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
- • Consider adding 'preload' to HSTS for maximum security
- • 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