Discord 1.0.162 — the first minute without a single click
How we tested: a clean Debian 13 in a disposable container; source — official file https://discord.com/api/download?platform=linux&format=deb (discord 1.0.162). Run as a regular user on a virtual screen, 60 seconds, nothing clicked. 16.10.2026. Every network request and every file written was recorded; the code was not decompiled. The container was deleted afterwards.
Package SHA-256: e7f346569784ef47eaa530c058d810bef686c7c063efcee6493d56d138f139cc
Summary
| What we checked | Result |
|---|---|
| Built-in telemetry, crash reporting, analytics, ad SDKs | none |
| Network requests in the first minute | 5 server names, plus 5 unnamed |
| Known trackers among the servers | none |
| Files written in the first minute | 172 |
| The program ran the whole time | yes — process alive at the end |
What is built in
10 files (4 MB) were checked.
No code of known telemetry, crash reporting, analytics or ad SDKs was found.
Where it connected
| Server | How | From second | Times | Known tracker |
|---|---|---|---|---|
idt-iyk4en-mvb6cw86.loc-en-us-posix.chk-webapp.res-err.err-403-status-403.dur-0.v1.dc-telemetry.net | DNS lookup only | 29.4 | 2 | — |
redirector.gvt1.com | connection | 28.3 | 1 | — |
rr3---sn-oj1gi5-5b.gvt1.com | connection | 28.9 | 1 | — |
stable.dl2.discordapp.net | DNS lookup only | 3.3 | 8 | — |
updates.discord.com | DNS lookup only | 0.2 | 4 | — |
162.159.136.232:443 | connection without a name (TCP) | 0.4 | 2 | — |
34.126.226.51:443 | connection without a name (TCP) | 3.5 | 4 | — |
162.159.137.232:443 | connection without a name (UDP) | 29.1 | 1 | — |
[2001:4860:4860::8888]:443 | connection without a name (UDP) | 29.2 | 1 | — |
162.159.129.232:443 | connection without a name (UDP) | 29.6 | 1 | — |
A DNS lookup is not yet a connection: the program looked up the server’s address. But the lookup itself is visible to the ISP and the DNS server.
What it wrote to disk
Folders the program wrote files to during the minute:
| Folder | Files |
|---|---|
~/.cache/mesa_shader_cache_db | 102 |
~/.config/discord | 61 |
~/.cache/fontconfig | 5 |
~/.local/share | 3 |
~/.cache/dconf | 1 |
How to read this card
- This is the first minute after launch with no action at all: what the program does on its own. Normal use may involve more requests.
- A “built-in SDK” means the library’s code was found. It does not prove data transfer, and an address in the code is not a request.
- The review was made automatically using a single method. You can check any program yourself here.