pingu

Privacy

In short: we do not record the query, the target or the result. We build no user profiles and keep no history.

What happens and what does not

  • The target you type and the measurement result are not written to a database or a file.
  • A result is kept in the tab that opened it and in server memory for a few minutes at most, then deleted.
  • Application logs never contain the target, the resolved IP or a result. The web server may keep ordinary access records (IP address, time, requested page); the content of a measurement request, i.e. the target, is not part of them.
  • The PDF report is generated in your browser; it is not sent to the server.

Temporary counters against abuse

To protect the service, the number of requests per IP and the number of concurrent jobs are kept in memory only, and deleted when their time runs out. These counters are never used as analytics or history. To stop many queries hitting one target in a short time, the target is counted briefly as an unreadable digest (keyed with a random key per process).

How is a measurement made?

Measurements are made by probe servers in several locations. Your browser never connects to a probe; it only talks to pingu.tr.

Fonts and third parties

Fonts are served from our own server. No third-party scripts or trackers are loaded.

IP locations

Results show the city, country and network provider of the target and of every hop on the path. For this, only IP addresses (not domain names) are sent from our server to the GetDNS IP location service (getdns.com.tr); your browser never connects to it. The locations of hops (routers) are cached on the server. The IP of the target you measure is never written to disk; it is kept in memory only, briefly.