Privacy
Submitted reports are public. This page explains what is hidden before publishing, and what the site does and does not store.
Redaction: what gets hidden
The text you paste is sent to this site's server, which redacts and parses it for the preview and saves nothing. When you publish, the server applies the same rules again and uses that result. The database and object storage hold only the redacted text; no copy of the original output is kept. You cannot choose to keep an item.
| Content | Handling | Example |
|---|---|---|
| IPv4 address | The first two octets are kept; the last two become *. | 203.0.113.45 → 203.0.*.* |
| IPv6 address | The first two groups are kept; the rest becomes *. | 2001:db8:abcd::1 → 2001:db8:*:* |
| Hostname | Found on the Hostname line and in shell prompts (including terminal window titles), then replaced everywhere it appears as a whole word in the text. | root@web-01:~# → root@[hostname]:~# |
| Email address | The whole address is replaced. | [email protected] → [email] |
| Secrets | Values of fields such as token, api_key, secret, password, passphrase, access_key, private_key and authorization (including a credential after Bearer), and strings starting with sk-, ghp_, github_pat_, xox, glpat-, AKIA or AIza, become [secret]. | api_key = abcd1234efgh → api_key = [secret] |
What is left unchanged
- Route hop addresses and carrier test-node addresses. The hops of a return-route trace, the target in a trace header, and the addresses of carrier test nodes are public network infrastructure, not yours, and a route is unreadable without them. Exception: if the same address also appears elsewhere in the output as an ordinary address, it is treated as yours and masked throughout.
- Private addresses. 10.x, 172.16–31.x, 192.168.x, 100.64–127.x, 127.x, 169.254.x, and IPv6
::1, fc00::/7, fe80::/10 and other reserved ranges cannot locate anyone on the public internet and are not touched. - ASN (autonomous system number) is not redacted. An ASN identifies the operator of a network, that is the provider, not you, and thousands of machines share one. The submit page uses it to recognise the provider automatically.
Redaction is automatic and covers only the types in the table. Other things such as user names, MAC addresses or serial numbers are not recognised, so check the preview on the submit page. The provider, plan and location names you type are published as typed; do not put personal information in them.
What the site stores
- The redacted raw text and the results parsed from it.
- The provider, plan and location names you typed.
- The script name and version, the test time the script recorded, and the submission time.
All of the above is public and visible to anyone. Separately, the site keeps an internal hash of the redacted text, used only to spot duplicate submissions and never shown.
- Submitter IP addresses are not stored. Not in the report and not in the database.
- Rate-limit counters are not stored. Limits on previews (30 per minute per IPv4 address or IPv6 /64), submissions (5 per minute) and flags (10 per minute) are counted only in the server process's memory, never in the database, and reset when it restarts.
- Flags store only a daily-rotating hash. A flag records the report, a reason and an optional note, plus a hash of the IP, the UTC date and a server-side secret. It only stops one person flagging the same report twice in a day. The hash changes the next day and cannot be reversed to an IP without the server's secret key.
- The site runs on its own server behind Cloudflare's proxy. Cloudflare's request logs may include visitor IP addresses; Cloudflare keeps them for a limited time and uses them only for debugging and abuse handling. The site's own services use the IP only in memory for rate limiting and flag de-duplication and never write it to the database or to logs.
Cookies and third parties
- The site sets one cookie,
lang(zhoren), written when you use the language switch to remember your choice for 1 year. There are no advertising or other tracking scripts. - Public pages load the catcounter (catcounter.pidan.dev) visitor counter script, used only to count visits; your browser sends it the address of the page you visit along with ordinary request details and your IP. That service handles it under its own policy. The admin backend does not load it.
- When bot verification is turned on, the submit page and the flag form once opened load Cloudflare Turnstile bot verification; the result and your IP are sent to Cloudflare to be checked. Cloudflare handles that under its own policy.
Editing and removal
Submitters cannot edit or delete reports. If a report contains personal information or breaks the rules, use the Flag button on the report page and pick the matching reason; administrators handle violations and personal data on request, including hiding a report. See also the guide.
Once a report is hidden, the page and its raw text immediately answer "not found" to new requests, but copies that were already cached expire with a delay: browsers may keep one for up to 60 seconds and shared caches such as a CDN for up to 5 minutes. After that the report is no longer served to anyone.