An extension keeps phoning home — is that expected?
The question arises for anyone who has opened a network monitor with extensions installed. Traffic from an empty tab looks unsettling, and telling who is sending it and why is tricky at first sight. It is worth understanding how to distinguish a innocuous update from telemetry.
I installed 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 description does not mention it. Is this tracking, or am I reading too much into it?
The first move is to separate yours from theirs: turn off all extensions in one go 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 a couple of minutes, no guessing.
If there is still no answer, an easy test helps: a required update goes to the author’s domain and to the point, while telemetry runs continuously, in the background, to a third-party server. The second type nearly always hides in settings behind a toggle no one knows about.
Why exactly the permission list doesn’t settle this
Access to tabs in the manifest and sending their list outward are two different things, and a lone permission line cannot tell them apart. Formally the add-on truthfully declares access; what it does with that access isn’t visible from the manifest. So watch the traffic, not the permission list.
It is simpler not to guess each time and leave webmaster tools handy — ones that say plainly they gather nothing. And this tab task is effortless to close with a telemetry-free stand-in — VirusTotal Domain Monitor, works the same and does not call home.
Reviews like this are valuable not for paranoia but for the habit: a few minutes with the network monitor after the install, and “pinging somewhere” turns into a clear picture of what goes where.