Open
Cached
·
just now
94/100
SECURITY SCORE
Detected Technologies
AWS Certificate Manager
Cloudflare CDNJS
Datadog
Figma
Google Analytics
Google Cloud Storage
Google reCAPTCHA
Google Search
Google Static File Front End
G Workspace
Heap
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
LaunchDarkly
Miro
Mux
Segment
Sentry
Microsoft SharePoint
Sprig
unpkg
Webflow
Google Cloud
Certificate Information
Subject
CN=api.sprig.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
June 15, 2025
Valid Until
July 13, 2026
138 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
00:4B:60:0A:B9:B9:09:98:06:A0:5B:43:8C:6A:37:0E:E9:7E:9E:56:70:B5:52:4F:96:64:94:D7:34:19:86:35
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
Present
fullscreen=(), geolocation=()
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
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