Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=docs.onepipe.io
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
January 26, 2026
Valid Until
August 12, 2026
188 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F7:43:89:FD:4C:08:30:1A:21:5B:16:93:91:BD:35:62:71:4B:B1:F0:E6:3C:6F:A7:4A:EF:43:0D:35:7C:37:E1
Alternative Names
Security Configuration
TLS Protocols
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Basic
base-uri; object-src; script-src; +2 more
base-uri 'self'; object-src 'self' blob:; script-src 'report-sample' 'nonce-4b600affb466493ba588e38a18d3d180' 'unsafe-eval' 'unsafe-inline' 'strict-dynamic' https:; frame-ancestors 'self'; report-uri https://web-security-reports.services.atlassian.com/csp-report/confluence-frontend
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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