Network-wide ads & trackers blocking DNS server
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ainar Garipov f5959a0dc6 Pull request: upd-chlog 2 weeks ago
.github Pull request: upd-domains-and-links 2 weeks ago
bamboo-specs Pull request: upd-domains-and-links 2 weeks ago
build Pull request: all: update go and backend tools 1 year ago
build2 Pull request: all: update go and backend tools 1 year ago
client Pull request: upd-domains-and-links 2 weeks ago
client2 Pull request: all: add bamboo specs 1 year ago
doc * tech doc: update architecture picture 2 years ago
internal Pull request: upd-domains-and-links 2 weeks ago
openapi Pull request: upd-domains-and-links 2 weeks ago
scripts Pull request: upd-domains-and-links 2 weeks ago
.codecov.yml Pull request: all: reformat yaml, add yaml formatting standard 2 years ago
.dockerignore Pull request: all: add a new Makefile and scripts, remove goreleaaser 2 years ago
.gitattributes Pull request: all: upd go 6 months ago
.gitignore Pull request: 3172 fix mobileconfig 1 year ago
.twosky.json Pull request: client: add fi, uk locales 9 months ago Pull request: all: fix some typos 12 months ago Pull request: upd-chlog 2 weeks ago Pull request: all: add links to new guidelines 1 year ago
LICENSE.txt Initial commit 4 years ago
Makefile Pull request: all: add stub binary for new api 4 months ago Pull request: upd-domains-and-links 2 weeks ago
changelog.config.js Pull request: all: less annoying pkg names 1 year ago
go.mod Pull request: all: fix quic reply id 2 months ago
go.sum Pull request: all: fix quic reply id 2 months ago
main.go Pull request: all: add stub binary for new api 4 months ago
main_v1.go Pull request: all: add stub binary for new api 4 months ago
staticcheck.conf Pull request: all: imp docs, names 1 year ago


AdGuard Home

Privacy protection center for you and your devices

Free and open source, powerful network-wide ads & trackers blocking DNS server. | Wiki | Reddit | Twitter | Telegram

Code Coverage Go Report Card Docker Pulls
Latest release adguard-home

AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.

It operates as a DNS server that re-routes tracking domains to a “black hole”, thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers, and both share a lot of code.

Getting Started

Automated install (Linux and Mac)

Run the following command in your terminal:

curl -s -S -L | sh -s -- -v

The script also accepts some options:

  • -c <channel> to use specified channel.
  • -r to reinstall AdGuard Home;
  • -u to uninstall AdGuard Home;
  • -v for verbose output;

Note that options -r and -u are mutually exclusive.

Alternative methods

Manual installation

Please read the Getting Started article on our Wiki to learn how to install AdGuard Home manually, and how to configure your devices to use it.


You can use our official Docker image.

Snap Store

If you're running Linux, there's a secure and easy way to install AdGuard Home - you can get it from the Snap Store.



If you want to integrate with AdGuard Home, you can use our REST API. Alternatively, you can use this python client, which is used to build the AdGuard Home Add-on.

Comparing AdGuard Home to other solutions

How is this different from public AdGuard DNS servers?

Running your own AdGuard Home server allows you to do much more than using a public DNS server. It's a completely different level. See for yourself:

  • Choose what exactly the server blocks and permits.
  • Monitor your network activity.
  • Add your own custom filtering rules.
  • Most importantly, this is your own server, and you are the only one who's in control.

How does AdGuard Home compare to Pi-Hole

At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using "DNS sinkholing" method, and both allow customizing what's blocked.

We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning.

AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort.

Disclaimer: some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature.

Feature AdGuard Home Pi-Hole
Blocking ads and trackers
Customizing blocklists
Built-in DHCP server
HTTPS for the Admin interface Kind of, but you'll need to manually configure lighttpd
Encrypted DNS upstream servers (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt) (requires additional software)
Cross-platform (not natively, only via Docker)
Running as a DNS-over-HTTPS or DNS-over-TLS server (requires additional software)
Blocking phishing and malware domains (requires non-default blocklists)
Parental control (blocking adult domains)
Force Safe search on search engines
Per-client (device) configuration
Access settings (choose who can use AGH DNS)
Running without root privileges

How does AdGuard Home compare to traditional ad blockers

It depends.

“DNS sinkholing” is capable of blocking a big percentage of ads, but it lacks flexibility and power of traditional ad blockers. You can get a good impression about the difference between these methods by reading this article. It compares AdGuard for Android (a traditional ad blocker) to hosts-level ad blockers (which are almost identical to DNS-based blockers in their capabilities). This level of protection is enough for some users.

Additionally, using a DNS-based blocker can help to block ads, tracking and analytics requests on other types of devices, such as SmartTVs, smart speakers or other kinds of IoT devices (on which you can't install traditional ad blockers).

Known limitations

Here are some examples of what cannot be blocked by a DNS-level blocker:

  • YouTube, Twitch ads
  • Facebook, Twitter, Instagram sponsored posts

Essentially, any advertising that shares a domain with content cannot be blocked by a DNS-level blocker.

Is there a chance to handle this in the future? DNS will never be enough to do this. Our only option is to use a content blocking proxy like what we do in the standalone AdGuard applications. We're going to bring this feature support to AdGuard Home in the future. Unfortunately, even in this case, there still will be cases when this won't be enough or would require quite a complicated configuration.

How to build from source


Run make init to prepare the development environment.

You will need this to build AdGuard Home:

  • go v1.17 or later.
  • node.js v10.16.2 or later.
  • npm v6.14 or later (temporary requirement, TODO: remove when redesign is finished).
  • yarn v1.22.5 or later.


Open Terminal and execute these commands:

git clone
cd AdGuardHome

Please note, that the non-standard -j flag is currently not supported, so building with make -j 4 or setting your MAKEFLAGS to include, for example, -j 4 is likely to break the build. If you do have your MAKEFLAGS set to that, and you don't want to change it, you can override it by running make -j 1.

Check the Makefile to learn about other commands.

Building for a different platform. You can build AdGuard for any OS/ARCH just like any other Go project. In order to do this, specify GOOS and GOARCH env variables before running make.

For example:

env GOOS='linux' GOARCH='arm64' make


make GOOS='linux' GOARCH='arm64'

Preparing release

You'll need this to prepare a release build:


make build-release CHANNEL='...' VERSION='...'

Docker image

  • Run make build-docker to build the Docker image locally (the one that we publish to DockerHub).

Please note, that we're using Docker Buildx to build our official image.

You may need to prepare before using these builds:

  • (Linux-only) Install Qemu: docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
  • Prepare builder: docker buildx create --name buildx-builder --driver docker-container --use

Resources that we update periodically

  • scripts/translations
  • scripts/whotracksme


You are welcome to fork this repository, make your changes and submit a pull request —

Please note that we don't expect people to contribute to both UI and golang parts of the program simultaneously. Ideally, the golang part is implemented first, i.e. configuration, API, and the functionality itself. The UI part can be implemented later in a different pull request by a different person.

Test unstable versions

There are two update channels that you can use:

  • beta - beta version of AdGuard Home. More or less stable versions.
  • edge - the newest version of AdGuard Home. New updates are pushed to this channel daily and it is the closest to the master branch you can get.

There are three options how you can install an unstable version:

  1. Snap Store -- look for "beta" and "edge" channels there.
  2. Docker Hub -- look for "beta" and "edge" tags there.
  3. Standalone builds. Use the automated installation script or look for the available builds below.


curl -s -S -L | sh -s -- -c beta


curl -s -S -L | sh -s -- -c edge

Report issues

If you run into any problem or have a suggestion, head to this page and click on the New issue button.

Help with translations

If you want to help with AdGuard Home translations, please learn more about translating AdGuard products in our Knowledge Base.

Direct link to AdGuard Home project on CrowdIn:


Here's what you can also do to contribute:

  1. Look for issues marked as "help wanted".
  2. Actualize the list of Blocked services. It can be found in filtering/blocked.go.
  3. Actualize the list of known trackers. It it can be found in [this repo] companiesdb.
  4. Actualize the list of vetted blocklists. It it can be found in client/src/helpers/filters/filters.json.

Projects that use AdGuard Home


This software wouldn't have been possible without:

You might have seen that CoreDNS was mentioned here before — we've stopped using it in AdGuard Home.

For a full list of all node.js packages in use, please take a look at client/package.json file.


Our main idea is that you are the one, who should be in control of your data. So it is only natural, that AdGuard Home does not collect any usage statistics, and does not use any web services unless you configure it to do so. Full policy with every bit that could in theory be sent by AdGuard Home is available here.