J
Public preliminary profile
jasper.ai
Jasper: public signals observed without founder access.
Preliminary scan — not founder-verified
This profile uses only publicly reachable signals. It does not verify internal settings, source code, data handling, provider accounts, or founder declarations, and it does not qualify for the TrustData Verified badge.
- Profile status
- Preliminary
- Last public scan
- Aug 1, 2026
- Credentials used
- None
Public scan observations
Seven public checks, with explicit limitations.
“Not available” means the signal could not be proven from public access. It is never replaced by a guessed value and does not imply that the underlying practice is absent.
| Check | Status | Public evidence | Observed |
|---|---|---|---|
| Homepage security headers | Fail | One or more requested security headers were absent from the homepage response.
| Aug 1, 2026 |
| TLS certificate | Pass | The public TLS endpoint presented a current authorized certificate.
| Aug 1, 2026 |
| Email DNS records | Pass | SPF, DMARC, and a public DKIM selector were observed.
| Aug 1, 2026 |
| Conventional public files | Fail | At least one conventional public file returned a definitive not-found response.
| Aug 1, 2026 |
| Public GitHub repository | Not available | No attributable public GitHub organization repository was confirmed.Not finding a repository does not prove that the company has no public repository. | Aug 1, 2026 |
| Client-visible trackers and cookies | Pass | Only non-advertising analytics signatures were observed.
| Aug 1, 2026 |
| Privacy policy URL | Pass | A linked privacy policy URL was reachable.
| Aug 1, 2026 |
Are you the founder of Jasper? Claim this profile and start the full verification.
Full verification remains separate from this scan and starts with the existing founder flow.
Claim this profile