An add-on keeps reaching out to its server — is that normal?
The question arises for anyone who has opened a network monitor with extensions installed. Traffic from an empty tab seems alarming, and figuring out who is sending it and why is tricky at first glance. It is worth learning how to distinguish a innocuous update from telemetry.
I set up a popular add-on for tabs, and everything works. But the network monitor shows it pinging some third-party domain once a minute, even when the tab sits idle. The listing does not mention it. Is this tracking, or am I reading too much into it?
The first step is to separate yours from theirs: turn off all extensions at once and see whether the background noise stops. If it goes quiet, the cause is one of them, and you switch each back on individually until the traffic reappears. That isolates the culprit in two minutes flat, no guessing.
If there is still no answer, a simple test helps: a necessary update goes to the author’s domain and to the point, while telemetry runs nonstop, in the background, to a third-party server. The second type almost always hides in the settings behind a toggle nobody knows about.
Why the permission list does not address this
Access to tabs in the manifest and sending their list out are two different things, and a lone permission line can’t tell them apart. Formally the add-on truthfully declares access; what it does with that access is not visible from the manifest. So watch the traffic, not the permission list.
It is easier not to guess each time and leave free webmaster tools within reach — ones that say plainly they collect nothing. And this tab chore is quick to close with a telemetry-free swap — geo-targeting for TDS, works the same and doesn’t call home.
Reviews like this are handy not for paranoia but for the habit: a few minutes with the network monitor after installing, and “pinging somewhere” becomes a clear picture of what goes where.