Before we can understand tb-rg adguard.net, we must first understand the base domain: adguard.net.
AdGuard’s DNS filtering software sometimes sends anonymized query statistics to *.adguard.net for reputation checks or to update filter lists. The tb-rg segment might represent a specific telemetry batch ID for reporting group. In other words, your device or router is reporting usage metrics to a dedicated endpoint.
As third-party cookies depreciate, tracking is shifting to first-party redirects (e.g., example.com redirecting through its own tracking endpoint). AdGuard has announced that TB-RG will evolve to include first-party redirect chains that:
AdGuard’s solution: Even if the redirect is first-party, if it meets TB-RG heuristics (e.g., same domain serves as redirect >80% of the time), it will be blocked. tb-rg adguard.net
The overwhelming majority of tb-rg requests originate from Android devices, specifically those running:
The tb-rg domain is hardcoded into system-level components of these Android distributions, often within:
Unlike standard Android’s connectivity check (which pings connectivitycheck.android.com or www.google.com), OEMs frequently replace these endpoints with their own—and sometimes add extra probes like tb-rg. Before we can understand tb-rg adguard
To understand where tb-rg fits, you have to understand the difference between AdGuard's two main offerings:
Let’s break down the string: tb-rg.adguard.net.
So when you see tb-rg adguard.net in your logs, you are witnessing a connectivity probe. AdGuard’s solution: Even if the redirect is first-party,
Android’s connectivity service needs to know if the network has internet access. The standard check fetches a small file from a known server (e.g., http://connectivitycheck.gstatic.com/generate_204).
Some OEMs implement multiple parallel checks. If one endpoint is blocked (by DNS filtering), the system may still declare internet access via another. tb-rg.adguard.net could serve as a secondary probe—but only if the DNS resolver is not blocking it. Since AdGuard DNS does block it (by returning no valid record), the probe fails, possibly skewing the device’s network status detection.