T
Public preliminary profile
topo.io
topo: 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
- Sep 23, 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 | Not available | Homepage security headers could not be evaluated.Response exceeds the 1000000-byte scan limit. | Sep 23, 2026 |
| TLS certificate | Pass | The public TLS endpoint presented a current authorized certificate.
| Sep 23, 2026 |
| Email DNS records | Pass | SPF, DMARC, and a public DKIM selector were observed.
| Sep 23, 2026 |
| Conventional public files | Fail | At least one conventional public file returned a definitive not-found response.
| Sep 23, 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. | Sep 23, 2026 |
| Client-visible trackers and cookies | Not available | Client-visible trackers could not be evaluated.Response exceeds the 1000000-byte scan limit. | Sep 23, 2026 |
| Privacy policy URL | Not available | A privacy policy URL could not be evaluated.Response exceeds the 1000000-byte scan limit. | Sep 23, 2026 |
Are you the founder of topo? 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