Plausible
What Plausible publishes, measured on their own site. Every result below links the page we found it on, or lists the addresses we checked.
- 40out of 100
- 10/10Criteria measured
- 2026-08-31Checked
Vendor site: plausible.io · category: Web analytics
Data processing agreement
Published and readable without a login.
Source: https://plausible.io/dpa · checked 2026-08-31
Subprocessor list
No subprocessor list found.
Checked 7 addresses on 2026-08-31.
Show the 7 addresses we checked
https://plausible.io/legal/subprocessors– reached, no match (HTTP 404)https://plausible.io/subprocessors– reached, no match (HTTP 404)https://plausible.io/sub-processors– reached, no match (HTTP 404)https://plausible.io/legal/sub-processors– reached, no match (HTTP 404)https://plausible.io/trust/subprocessors– reached, no match (HTTP 404)https://plausible.io/privacy/subprocessors– reached, no match (HTTP 404)https://plausible.io/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
The hosting location is stated on a public page.
Source: https://plausible.io/security · checked 2026-08-31
Status page with history
No public status page found.
Checked 3 addresses on 2026-08-31.
Show the 3 addresses we checked
https://status.plausible.io/– reached, no match (HTTP 200)https://plausible.io/status– reached, no match (HTTP 200)https://plausible.io.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
No public pricing with figures found.
Checked 5 addresses on 2026-08-31.
Show the 5 addresses we checked
https://plausible.io/pricing– reached, no match (HTTP 404)https://plausible.io/pricing/– reached, no match (HTTP 404)https://plausible.io/plans– reached, no match (HTTP 404)https://plausible.io/en/pricing– reached, no match (HTTP 404)https://plausible.io/pricing-plans– reached, no match (HTTP 404)
Certifications named
No named certification found.
Checked 6 addresses on 2026-08-31.
Show the 6 addresses we checked
https://plausible.io/security– reached, no match (HTTP 200)https://plausible.io/trust– reached, no match (HTTP 404)https://plausible.io/trust-center– reached, no match (HTTP 404)https://plausible.io/compliance– reached, no match (HTTP 200)https://plausible.io/legal/security– reached, no match (HTTP 404)https://trust.plausible.io/– The name "trust.plausible.io" could not be resolved.
Uptime SLA with a figure
No uptime figure found.
Checked 6 addresses on 2026-08-31.
Show the 6 addresses we checked
https://plausible.io/legal/sla– reached, no match (HTTP 404)https://plausible.io/sla– reached, no match (HTTP 404)https://plausible.io/legal/service-level-agreement– reached, no match (HTTP 404)https://plausible.io/trust/sla– reached, no match (HTTP 404)https://plausible.io/uptime– reached, no match (HTTP 404)https://plausible.io/legal/uptime-sla– reached, no match (HTTP 404)
HTTPS enforced with HSTS
No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-08-31.
Show the 2 addresses we checked
http://plausible.io/– redirects to https://plausible.io/https://plausible.io/– no HSTS header
No third-party tracking before consent
No third-party requests before any interaction.
Source: https://plausible.io/ · checked 2026-08-31
security.txt (RFC 9116)
No security.txt found.
Checked 1 address on 2026-08-31.
Show the 1 address we checked
https://plausible.io/.well-known/security.txt– reached, no match (HTTP 404)