Guide 2 of 10

Watching traffic

Everything on the Watch tab: how monitoring starts and stops, the Today and Week summaries, the live connection list, and the detail page behind each connection.

Starting, stopping and pausing

Monitoring is what lets Demarc see traffic at all. Nothing is recorded, blocked or checked while it is off.

ControlWhereWhat it does
Start / StopPill at the top of Watch; also Settings › MonitoringStarts or ends monitoring. The label beside it reads “since 1:18 PM” while running and “not running” when off.
Pause / ResumeFooter of Watch; also SettingsPauses for 15 minutes, then resumes by itself. While paused traffic still flows, but nothing is recorded, blocked, firewalled, ruled or checked.
Always monitorSettings › MonitoringOff by default. When on, monitoring starts by itself when you open Demarc or restart your phone.
Always-on VPNSettings › MonitoringOpens Android’s own VPN settings, where you can have Android keep Demarc running from the moment the phone turns on. It is the only hard guarantee that monitoring is up.

Running, then paused

The footer is the status line: Protecting while running, Paused with the time it resumes, and a count of what was blocked today. Pause and Record sit at the right of it.

The key icon in the status bar is Android’s own sign that a VPN is active. It stays for as long as monitoring runs.

Watch tab on the Live view, paused until 1:35 PM, with Resume and Record in the footer
Only one VPN can be active on Android at a time. If another VPN app takes over, or you revoke Demarc’s permission, Demarc posts a “Monitoring was turned off” notification. Open the app and tap Start to take it back. If something blocks the start, a Couldn’t start monitoring card offers Try again and Open VPN settings.

Today

The default view: how much is moving, and who is responsible.

The live meter

At the top, throughput in and out, the number of live connections, and a sparkline of the recent past. The Today / Week / Live switch underneath chooses what the rest of the screen shows.

Connection names the network you are on and says what it can learn about you. “The sites you look up are visible” means every name your phone resolves can be read by your network and provider; Android Settings › Network › Private DNS, or Demarc’s own encrypted lookups, change that.

Watch tab Today view with live throughput, connection card and session totals

This session totals what has moved since monitoring started: Downloaded, Uploaded, While your screen was off, Moved despite Doze (traffic Android had told an app to stop, which went anyway) and Encrypted, as a percentage, with a note on whether site names were hidden too.

Last 24 hours is an hourly chart. It counts only what Demarc recorded while monitoring was on; periods it was off are drawn as a faint mark, not as zero. Which apps lists the apps that moved data in the background or with the screen off. Timeline there opens a view of which app you were using, which needs Usage access (see Permissions).

Week

Two weeks of history, kept on the phone.

Last 14 days

Daily bars for the last 14 days, and Top apps for the same window. Tap an app for its detail page.

Until you have captured some traffic it reads “No history yet — capture some traffic and check back.” See Stored data for how long each kind of history is kept.

Watch tab Week view with last 14 days and top apps, empty before any history

Live connections

Every flow as it opens, with the app that owns it.

Reading the list

Each row shows the destination, then the app, a protocol tag, the company or operator and country when known, and bytes each way. A dot on the left gives the state: red blocked, amber readable, green live, grey closed.

Group repeats (on by default) folds repeat connections from one app to the same host into a single row marked ×3. Blocked ones group on their own. Tap the app icon for the app, or the row for the connection.

Live connections list showing Chrome connections with protocol tags and bytes

Search and filter

The search box matches app name, site name, address and port. The menu at its right filters the list:

FilterShows
AllEvery connection.
DNS requestsThe names apps looked up, with a status of resolved, no answer, waiting or blocked and its category. If your phone uses Private DNS over TLS, this list cannot see lookups and says so.
Web (HTTPS)Port 443.
BlockedOnly what Demarc stopped, with the reason.
Reliable (TCP) / Fast (UDP)By transport.

What the tags mean

TagMeaning
plain HTTP · readableNot encrypted. Anyone on the network path can read it.
web / encryptedTLS. The site name may be visible, the contents are not.
lookupA DNS lookup. Lookup · readable is an unencrypted one.
clock / local / call setupNTP time sync, local-network discovery, and STUN for calls.
TrackerThe destination is a known tracking company.
blocked at …What stopped it: a list, a rule, the per-app firewall, and so on.
Apps that resolve names themselves are invisible in the DNS view. An app using its own encrypted DNS never shows its lookups to Demarc. Stop apps bypassing your settings closes that gap.

One connection, in full

Tap any row for everything Demarc knows about it, and for ways to act on it.

The top bar says whether anyone else could read it: Nobody else can read this or Anyone on this network can read this. Below that are four buttons:

ButtonWhat it does
Block this siteAdds the host to your own blocklist. An Undo bar appears. Shown only when the site name is known.
Make a rule from thisOpens the rule editor with the app, domain, port and transport filled in. See Create a rule.
Block this app’s internetCuts the whole app off. Becomes “Internet already blocked” once done.
CopyCopies host:port.

The cards below group the facts: This connection (protocol, state, what blocked it, operator, destination, site name), When it happened (foreground or background, screen on or off, first and last seen, background and screen-off data), Traffic (bytes and packets each way), Encryption details (server name and the app’s TLS fingerprint) and Where it went (country, network and operator, once the location database is on).

Foreground or background needs Usage access. Without it the context reads “Unknown (grant Usage Access)”.