Skip to content

NetGuard: Block Internet Access Per App Without Root

NetGuard: Block Internet Access Per App Without Root

NetGuard review: use logs to spot real data leaks, test Private DNS setup limits, and migrate per-app firewall rules across Android devices.

App summary

App
NetGuard
Developer
Marcel Bokhorst (M66B)
License
GPL-3.0-only
Version
unknown
Size
unknown
Price
Free; optional pro features may require payment (exact pricing unknown)

NetGuard is an Android app from developer Marcel Bokhorst (M66B), released under GPL-3.0-only, free to use with optional pro features that may require payment at a price the fact data does not specify. Its stated job is narrow and concrete: act as a local firewall so you can block internet access per app without root. That is the whole pitch, and it is worth taking literally.

The trouble starts when people hear “firewall” and assume encryption, anonymity, or automatic ad blocking. None of those are in the documented scope. NetGuard’s documented functions are a local firewall, per-app rules for Wi-Fi and mobile data, logging and notifications, an install path, and privacy and security considerations tied to that local behavior.

This review defends a specific position: judge NetGuard as a GPL-3.0 Android local firewall with per-app Wi-Fi and mobile data rules and logging. Do not judge it as an encrypting VPN, an antivirus, or a zero-config ad blocker. Its pro pricing and several edge-case behaviors remain unknown, and pretending otherwise would be dishonest.

How to Read NetGuard Logs to Spot a Real Data Leak

Logging and notifications are listed in the fact data as a NetGuard function, which makes them the documented evidence source for rule activity. If you want to know whether a rule is doing anything, the app’s own logs and notifications are where that information is supposed to surface. That is a modest claim, but it is the one the documentation supports.

Reading those logs usefully means tying each entry back to the per-app rules for Wi-Fi and mobile data. A connection attempt from an app you blocked on mobile data but allowed on Wi-Fi is not automatically a leak. It may be the rule doing exactly what you asked. The rule context is what turns a raw log line into a finding, and the two rule surfaces — Wi-Fi and mobile data — are separate, so you have to check which one produced the traffic before drawing conclusions.

Here is the honest limit. Exact log fields, export options, and a step-by-step leak-detection workflow are unknown in the fact data. You should not expect a documented “leak score,” a forensic timeline, or a built-in investigation guide. What you can do is use the documented per-app rule structure as your reference frame and read the logs against it.

Keep privacy and security claims tied to local firewall behavior. Logging here is evidence of local rule activity, not anonymization and not encryption. A log entry showing that an app was blocked tells you a rule matched. It does not tell you that traffic was encrypted, and it does not tell you that you are anonymous. Those are different properties, and conflating them is how people end up trusting a tool for something it never claimed to do.

NetGuard With Android Private DNS: Setup Reality and Unknowns

The fact data confirms Android as the platform and describes a local firewall with per-app Wi-Fi and mobile data rules. It does not document Private DNS behavior at all. That means any claim that NetGuard filters Private DNS queries, conflicts with Private DNS, or requires Private DNS to be disabled is outside the fact set. Treat the interaction as unknown.

The practical consequence is that you should not promise yourself filtering compatibility. Android Private DNS changes how DNS resolution is handled at the operating system level. Whether NetGuard’s local rules see, affect, or ignore that traffic is not described in the documentation we have. If you enable Private DNS and expect NetGuard to behave a certain way, you are guessing.

Logging and notifications are the documented place to verify rule effects, so they are the natural first stop when you change something. But the exact log details are unknown, which means verification is a matter of observation, not a documented procedure. You can watch what the app reports after a change; you cannot cite a manual that explains precisely what each field means.

Anchor your privacy and security expectations in the local firewall function, not in DNS encryption or anonymity. Private DNS is about DNS encryption. NetGuard’s documented scope is local per-app blocking. Those are separate concerns, and the fact data does not merge them. If DNS privacy is your priority, that is a different conversation from per-app rule control.

Backing Up and Migrating NetGuard Per-App Rules Between Android Devices

Per-app rules for Wi-Fi and mobile data are core NetGuard functionality according to the fact data, which makes them the main thing a reader would want to preserve when moving to a new phone. Your rule set is the work. Rebuilding it by hand is the cost of losing it.

The fact data does not list backup, export, import, or migration features. That is a real gap, not a footnote. You should mark those capabilities as unknown rather than inventing a method. There is no documented file format, no documented export button, and no documented import flow in the material we are working from.

Installing NetGuard is a documented function. Migrating your rules is not. A fresh install on a new device is within the documented scope; carrying your configuration over is an open question. Those are different tasks, and the documentation only covers the first one.

Avoid implying cloud sync or a specific file format, because neither appears in the fact data. If portability matters to you — and for a rule-heavy firewall it usually does — resolve that question before you depend on the app. Do not assume a backup exists just because a similar app has one.

NetGuard Is a Local Firewall, Not an Encrypting VPN or Antivirus

The fact data describes NetGuard as a local firewall with per-app Wi-Fi and mobile data rules. It does not describe an encrypting or anonymizing VPN. That distinction matters because Android’s interface may present VPN-related signals, and users reasonably confuse the two. The documented function is local filtering, not traffic encryption.

There is no antivirus or malware scanning in the fact data. None. If you are looking for a scanner that inspects apps for malicious behavior, NetGuard is the wrong tool, and no amount of rule configuration will turn it into one. Readers seeking malware protection should look elsewhere.

Users who want IP masking or anonymous browsing should skip NetGuard based on the documented local firewall scope. The app does not claim to hide your address or route your traffic through another location. Judging it against that standard is a category error.

The defensible value is rule-based local control plus logging and notifications. That is a real value, but it is not zero-config ad blocking and it is not anonymity. NetGuard gives you a way to decide which apps reach the network on which connection type, and it gives you signals about what happened. That is the honest sales pitch.

One more correction: NetGuard does not require root access to work. The title of this review says so, and the fact data frames the app as an Android local firewall rather than a root-dependent tool. If you avoided it because you assumed root was mandatory, that assumption was wrong.

What the Local Firewall Does With Per-App Rules

A local firewall, in the sense the fact data uses, means the filtering happens on the device. It is not a remote service making decisions for you. The rules live with the app, and the app enforces them locally. That is the architecture the documentation describes, and it is the basis for every privacy claim you can responsibly make.

Per-app rules for Wi-Fi and mobile data are two separate surfaces. You can treat an app differently depending on which connection it is using. That separation is the heart of the product. A reader who only blocks mobile data for a chatty app has made a different decision from a reader who blocks both, and the app is built to express that difference.

There are no documented domain-level rules. The documented unit is the app, not the domain. So the common reader question — can NetGuard block specific domains without root? — is not answered by the fact data. It may or may not be possible; the documentation we have does not say. Do not plan around it.

Whether NetGuard can block system apps or only user-installed apps is also not documented. Do not assume either way. If your goal depends on blocking a system component, verify that before you commit to the app as your solution.

Installing NetGuard and What the Official Source Gives You

Installation is a documented NetGuard function. That sounds trivial, but it matters for this review because the fact data treats install as part of the product’s scope. Use the official source for the app. Do not pick up builds from unofficial mirrors, and do not treat a random APK as equivalent to the real thing.

The project is licensed GPL-3.0-only. That is a fact about the software license, not a promise about any particular build. A copyleft license tells you something about how the source can be used and redistributed. It does not tell you that every distributed binary behaves identically, and it does not settle questions about feature differences between distribution channels.

The reader question about Play Store versus GitHub versions is fair, but the fact data does not document the differences. Do not assume the builds are identical, and do not assume they are different. The honest answer is that this comparison is outside the documented material. If build identity matters to you, verify it at the source rather than trusting a general claim.

Users on managed devices that prohibit VPN services are the wrong audience. If your device policy blocks VPN-type services, NetGuard’s documented local firewall role is likely incompatible with that policy. The exact behavior in a managed environment is not documented, so treat it as a reason to check with whoever administers the device before installing.

Notifications, the VPN Key Icon, and Other On-Device Signals

Notifications are a documented NetGuard function, and they function as a signal rather than a verdict. A notification can tell you that something happened. It cannot, by itself, tell you whether the underlying rule was correct for your intent. Read notifications alongside the per-app Wi-Fi and mobile data rules, not in isolation.

The VPN key icon in Android’s status bar is a platform indicator for a VPN-type connection. The fact data does not document the icon itself, so treat it as an Android signal rather than a NetGuard feature. It is not proof that your traffic is encrypted, and it is not proof that you are anonymous. It is a status-bar convention.

A common expectation is that NetGuard can run alongside another Android VPN. Nothing in the fact data supports simultaneous operation, and the misconception is worth naming directly. Do not plan on keeping another VPN active at the same time. If you need both, that is a constraint to resolve before you build a workflow around the app.

Battery behavior on modern Android phones is not documented in the fact data. Neither is Always-on VPN interaction. Those are real questions, and they deserve real answers, but this review cannot supply them from the material available. Anyone who tells you a specific battery figure is going beyond what is documented.

Pricing, the Pro Tier, and Licensing in Plain Terms

NetGuard is free, with optional pro features that may require payment. The exact pricing is unknown in the fact data. That is the entire pricing story we can tell honestly. Do not expect a number here, because inventing one would be worse than leaving the gap visible.

Because the pro tier is described only as “optional pro features,” you should not assume what it unlocks. It may add capabilities; it may not. The documentation does not enumerate them. If a specific feature matters to your decision, confirm it before paying.

The GPL-3.0-only license is a fact about the project, not a feature of the app. It tells you the software is free and open source under a specific copyleft license. It does not tell you that the app is better, safer, or more private than a closed-source alternative. License and behavior are separate questions.

Marcel Bokhorst (M66B) is the developer. That attribution belongs in a review because it identifies who is responsible for the project, but it is not a reason to trust or distrust the app on its own. Judge the documented behavior, not the biography.

Ads, Domains, and What Rule-Based Blocking Cannot Promise

Does NetGuard block ads inside apps and browsers? The fact data does not document ad blocking. The documented unit is per-app internet access, not content filtering. You can deny an app’s access to Wi-Fi or mobile data, and that may incidentally stop that app’s ads, but that is a consequence of blocking the app, not a documented ad-blocking feature.

Zero-config ad blocking everywhere is the wrong expectation. NetGuard is not described as a set-and-forget content filter. It is described as a local firewall with per-app rules. If you install it expecting ads to vanish across every app without configuration, you will be disappointed, and the disappointment will be your expectation’s fault, not the app’s.

Domain-level blocking without root is not documented either. The fact data gives you per-app rules for Wi-Fi and mobile data. It does not give you a documented domain blocklist workflow. Treat domain-level control as unknown rather than promised.

What rule-based blocking can promise is narrower and more useful: you can decide that a given app does not reach the network on Wi-Fi, on mobile data, or on both. That is a real capability, and it is the one the documentation supports. Build your expectations around it.

Verdict

NetGuard is for Android users who want local, rule-based control over which apps reach the network on Wi-Fi and mobile data, and who value logging and notifications as evidence of what those rules are doing. It is also for people who understand that “without root” is part of the pitch and who are comfortable with a GPL-3.0-only project whose pro pricing is not documented.

It is not for users seeking IP masking or anonymous browsing. It is not for users who want an antivirus or malware scanner. It is not for parents who need parental control content filtering. It is not for anyone who must keep another VPN active at the same time. It is not for users expecting zero-config ad blocking everywhere, and it is not for people on managed devices that prohibit VPN services.

The app’s defensible value is rule-based local control plus logging and notifications. That is a modest, specific, and genuinely useful combination. It is not encryption, it is not anonymity, and it is not automatic content filtering. Readers who want those things should look at different tools.

Several behaviors remain unknown: exact log fields and export options, Private DNS interaction, backup and migration paths, Play Store versus GitHub build differences, battery impact, Always-on VPN behavior, system-app coverage, and pro pricing. A careful reader will treat those as open questions rather than settled facts. NetGuard is worth considering on the strength of what is documented, and only on that strength.

Pros

  • Open source and auditable
  • No root required
  • Local filtering without a remote VPN server

Cons

  • Occupies Android's VPN slot, so it cannot run with another VPN at the same time
  • Does not inspect encrypted traffic or provide antivirus protection
  • Some pro features may require payment; exact feature set and pricing are unknown
Download from the official source

The link goes straight to Marcel Bokhorst (M66B). We do not host app files.

Open official page →

Frequently asked questions

Is NetGuard free?

The recorded pricing model is Free; optional pro features may require payment (exact pricing unknown).

What license does it use?

It is listed under GPL-3.0-only.

Where can I download the official version?

The official link points to https://netguard.me/.

This article was drafted with AI assistance using official developer documentation, release notes, privacy policies, and public data, then reviewed by an editor. We do not claim lab testing. The full method is on our Review Method page.