Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Trust
AWS
Amazon S3
Bugsnag
Cloudflare
Active incidents
Cloudflare CDN
Cloudflare CDNJS
Cloudflare Web Analytics
Cloudinary
Datadog
Facebook
GitHub
Google Analytics
Google API JS Client
Google Cloud Storage
Google Fonts
Google Maps
Google Search
Google Static File Front End
G Workspace
Grafana
Active incidents
LaunchDarkly
LiveChat
Pendo
Plaid
Report URI
Salesforce Cloud
Salesforce Sites
Statuspage
Zendesk
Google Cloud
Certificate Information
Subject
CN=callpotential.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 19, 2026
Valid Until
June 17, 2026
46 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
AF:B9:1C:56:5A:37:1B:07:12:52:D5:A6:EE:88:39:55:EF:DF:CF:55:EC:45:11:05:A0:93:6C:94:ED:C0:07:7C
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=15552000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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