An extension keeps calling home — is that normal?

The question comes up for anyone who has ever opened a network monitor with extensions installed. Traffic from an empty tab looks unsettling, and figuring out who is sending it and why is tricky at first glance. It is worth learning how to distinguish a harmless update from telemetry.

I set up a popular add-on for tabs, and everything seems to work. But the network monitor shows it pinging some third-party domain once a minute, even when the tab is idle. The listing doesn't mention it. Is this tracking, or am I reading too much into it?

The first step is to separate yours from theirs: disable all extensions in one go and see whether the background noise stops. If it goes quiet, the source is one of them, and you switch each back on individually until the traffic returns. That isolates the culprit in two minutes flat, 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 kind nearly always hides in the settings behind a toggle nobody knows about.

Why the permission list doesn't resolve this

Access to tabs in the manifest and sending their list out are different things, and a lone permission line cannot distinguish them. On paper the add-on honestly declares access; what it does with that access is not visible from the manifest. So look at the traffic, not the permission list.

It is simpler not to guess each time and leave seo tools for webmasters within reach — ones that say plainly they gather nothing. And this tab task is effortless to close with a telemetry-free replacement — QR generator with no accounts, behaves 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 the install, and "pinging somewhere" becomes a clear picture of what goes where.