Try our Chrome extension
Easily add the current web-page from your browser directly into your changedetection.io tool, more great features coming soon!
Chrome Webstore
Changedetection.io needs your support!
You can help us by supporting changedetection.io on these platforms;
- Rate us at AlternativeTo.net
- Star us on GitHub
- Follow us at Twitter/X
- G2 Software reviews
- Check us out on LinkedIn
- And tell your friends and colleagues :)
The more popular changedetection.io is, the more time we can dedicate to adding amazing features!
Many thanks :)
changedetection.io team
Not yet seconds ago
False
Not yet seconds ago
Triggered text Ignored text Blocked text
7 hours ago
Skip to content
Navigation Menu
Sign in Appearance settings
* Platform
+ AI CODE CREATION
o GitHub Copilot Write better code with AI
o GitHub Copilot app Direct agents from issue to merge
o MCP Registry Integrate external tools
+ DEVELOPER WORKFLOWS
o Actions Automate any workflow
o Codespaces Instant dev environments
o Issues Plan and track work
o Code Review Manage code changes
o Code Quality Enforce quality at merge
+ APPLICATION SECURITY
o GitHub Advanced Security Find and fix vulnerabilities
o Code security Secure your code as you build
o Secret protection Stop leaks before they start
+ EXPLORE
o Why GitHub
o Documentation
o Blog
o Changelog
o Marketplace
View all features
* Solutions
+ BY COMPANY SIZE
o Enterprises
o Small and medium teams
o Startups
o Nonprofits
+ BY USE CASE
o App Modernization
o DevSecOps
o DevOps
o CI/CD
o View all use cases
+ BY INDUSTRY
o Healthcare
o Financial services
o Manufacturing
o Government
o View all industries
View all solutions
* Resources
+ EXPLORE BY TOPIC
o AI
o Software Development
o DevOps
o Security
o View all topics
+ EXPLORE BY TYPE
o Customer stories
o Events & webinars
o Ebooks & reports
o Business insights
o GitHub Skills
+ SUPPORT & SERVICES
o Documentation
o Customer support
o Community forum
o Trust center
o Partners
View all resources
* Open Source
+ COMMUNITY
o GitHub Sponsors Fund open source developers
+ PROGRAMS
o Security Lab
o Maintainer Community
o Accelerator
o GitHub Stars
o Archive Program
+ REPOSITORIES
o Topics
o Trending
o Collections
* Enterprise
+ ENTERPRISE SOLUTIONS
o Enterprise platform AI-powered developer platform
+ AVAILABLE ADD-ONS
o GitHub Advanced Security Enterprise-grade security features
o Copilot for Business Enterprise-grade AI features
o Premium Support Enterprise-grade 24/7 support
* Pricing
Type / to search
Sign in
Sign up Appearance settings
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Uh oh!
There was an error while loading. Please reload this page.
AdguardTeam / AdGuardHome Public
* Notifications You must be signed in to change notification settings
* Fork 2.5k
* Star 36.1k
* Code
* Issues 1.2k
* Pull requests 116
* Discussions
* Actions
* Projects
* Wiki
* Security and quality 3
* Insights
Additional navigation options
* Code
* Issues
* Pull requests
* Discussions
* Actions
* Projects
* Wiki
* Security and quality
* Insights
master
Branches Tags
Go to file
Code
Open more actions menu
Folders and files
Name Name Last commit message Last commit date
Latest commit
History
4,545 Commits
4,545 Commits
.github .github
bamboo-specs bamboo-specs
build build
client client
client_v2 client_v2
doc doc
docker docker
internal internal
openapi openapi
scripts scripts
snap snap
.codecov.yml .codecov.yml
.gitattributes .gitattributes
.gitignore .gitignore
.markdownlint.json .markdownlint.json
.prettierignore .prettierignore
.twosky.json .twosky.json
AGHTechDoc.md AGHTechDoc.md
CHANGELOG.md CHANGELOG.md
CONTRIBUTING.md CONTRIBUTING.md
HACKING.md HACKING.md
LICENSE.txt LICENSE.txt
Makefile Makefile
README.md README.md
SECURITY.md SECURITY.md
changelog.config.js changelog.config.js
go.mod go.mod
go.sum go.sum
main.go main.go
main_next.go main_next.go
staticcheck.conf staticcheck.conf
View all files
Repository files navigation
*
* README
* Contributing
* GPL-3.0 license
* Security
More items
Privacy protection center for you and your devices
Free and open source, powerful network-wide ads & trackers blocking DNS server.
AdGuard.com | Wiki | Reddit | Twitter | Telegram
AdGuard Home is a network-wide software for blocking ads and 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/Unix/MacOS/FreeBSD/OpenBSD)
+ Alternative methods
+ Guides
+ API
* Comparing AdGuard Home to other solutions
+ How is this different from public AdGuard DNS servers?
+ How does AdGuard Home compare to Pi-Hole
+ How does AdGuard Home compare to traditional ad blockers
+ Known limitations
* How to build from source
+ Prerequisites
+ Building
* Contributing
+ Test unstable versions
+ Reporting issues
+ Help with translations
+ Other
* Projects that use AdGuard Home
* Acknowledgments
* Privacy
Getting Started
Automated install (Linux/Unix/MacOS/FreeBSD/OpenBSD)
To install with curl run the following command:
curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v
To install with wget run the following command:
wget --no-verbose -O - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v
To install with fetch run the following command:
fetch -o - https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | 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.
Docker
You can use our official Docker image on Docker Hub.
Snap Store
If you're running Linux, there's a secure and easy way to install AdGuard Home: get it from the Snap Store.
Guides
See our Wiki.
API
If you want to integrate with AdGuard Home, you can use our REST API. Alternatively, you can use this python client, which can be used to build the AdGuard Home Assistant integration.
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, it's 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 the so-called “DNS sinkholing” method and both allow customizing what's blocked.
Note
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.
Note
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) ✅ ❌ (requires non-default blocklists)
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 the flexibility and the power of traditional ad blockers. You can get a good impression about the difference between these methods by reading this article, which 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
Prerequisites
Run make init to prepare the development environment.
You will need this to build AdGuard Home:
* Go v1.25 or later;
* Node.js v24.10.0 or later;
* npm v10.8 or later;
Building
Open your terminal and execute these commands:
git clone https://github.com/AdguardTeam/AdGuardHome
cd AdGuardHome
make
Warning
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 Home for any OS/ARCH that Go supports. In order to do this, specify GOOS and GOARCH environment variables as macros when running make.
For example:
env GOOS= ' linux ' GOARCH= ' arm64 ' make
or:
make GOOS= ' linux ' GOARCH= ' arm64 '
Preparing releases
You'll need snapcraft to prepare a release build. Once installed, run the following command:
make build-release CHANNEL= ' ... ' VERSION= ' ... '
See the build-release target documentation.
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 the builder:
docker buildx create --name buildx-builder --driver docker-container --use
See the build-docker target documentation.
Debugging the frontend
When you need to debug the frontend without recompiling the production version every time, for example to check how your labels would look on a form, you can run the frontend build a development environment.
1. In a separate terminal, run:
( cd ./client/ && env NODE_ENV= ' development ' npm run watch )
2. Run your AdGuardHome binary with the --local-frontend flag, which instructs AdGuard Home to ignore the built-in frontend files and use those from the ./build/ directory.
3. Now any changes you make in the ./client/ directory should be recompiled and become available on the web UI. Make sure that you disable the browser cache to make sure that you actually get the recompiled version.
End-to-End (E2E) Frontend Tests
AdGuard Home uses Playwright for E2E testing. Tests are located in tests/e2e.
Running Tests:
* npm run test:e2e – run all tests (headless).
* npm run test:e2e:interactive – run tests interactively.
* npm run test:e2e:debug – run tests in debug mode.
* npm run test:e2e:codegen – generate new test code.
Setup:
1. Run npm install to install dependencies.
2. Run npx playwright install to set up required browsers.
Warning: Playwright will download and install its own browser binaries for testing, which may differ from the browsers installed on your system.
Contributing
You are welcome to fork this repository, make your changes and submit a pull request. Please make sure you follow our code guidelines though.
Please note that we don't expect people to contribute to both UI and backend parts of the program simultaneously. Ideally, the backend 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 versions of AdGuard Home. More or less stable versions, usually released every two weeks or more often.
* edge: the newest version of AdGuard Home from the development branch. New updates are pushed to this channel daily.
There are three options how you can install an unstable version:
1. Snap Store: look for the beta and edge channels.
2. Docker Hub: look for the beta and edge tags.
3. Standalone builds. Use the automated installation script or look for the available builds on the Wiki.
Script to install a beta version:
curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c beta
Script to install an edge version:
curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | 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. Please follow the instructions in the issue form carefully and don't forget to start by searching for duplicates.
Help with translations
If you want to help with AdGuard Home translations, please learn more about translating AdGuard products in our Knowledge Base. You can contribute to the AdGuardHome project on CrowdIn.
Other
Another way you can contribute is by looking for issues marked as help wanted, asking if the issue is up for grabs, and sending a PR fixing the bug or implementing the feature.
Projects that use AdGuard Home
Please note that these projects are not affiliated with AdGuard, but are made by third-party developers and fans.
* AdGuard Home Remote: iOS app by Joost.
* Python library by @frenck.
* Home Assistant add-on by @frenck.
* OpenWrt LUCI app by @kongfl888 (originally by @rufengsuixing).
* AdGuardHome sync by @bakito.
* Terminal-based, real-time traffic monitoring and statistics for your AdGuard Home instance by @Lissy93
* AdGuard Home on GLInet routers by Gl-Inet.
* Cloudron app by @gramakri.
* Asuswrt-Merlin-AdGuardHome-Installer by @jumpsmm7 aka @SomeWhereOverTheRainBow.
* Node.js library by @Andrea055.
* Browser Extension by @satheshshiva.
* Zabbix Template for AdGuard Home by @diasdmhub.
* Chocolatey package by niks255.
Acknowledgments
This software wouldn't have been possible without:
* Go and its libraries:
+ gcache
+ miekg's dns
+ go-yaml
+ service
+ dnsproxy
+ urlfilter
* Node.js and its libraries:
+ React.js
+ Tabler
+ And many more Node.js packages.
* whotracks.me data
You might have seen that CoreDNS was mentioned here before, but we've stopped using it in AdGuard Home.
For the full list of all Node.js packages in use, please take a look at client/package.json file.
Privacy
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. See also the full privacy policy with every bit that could in theory be sent by AdGuard Home is available.
About
Network-wide ads & trackers blocking DNS server
adguard.com/adguard-home/overview.html
Topics
adblockadguarddnsdns-over-httpsdns-over-quicdns-over-tlsdnscryptgolangopen-sourceprivacy
Resources
Readme
GPL-3.0 license
Contributing
Contributing
Security policy
Security policy
Activity
Custom properties
Stars
36.1k stars
Watchers
326 watching
Forks
2.5k forks
Report repository
Releases
Used by
Contributors
Languages
Footer
© 2026 GitHub, Inc.
Footer navigation
* Terms
* Privacy
* Security
* Status
* Community
* Docs
* Contact
* Manage cookies
* Do not share my personal information
You can’t perform that action at this time.
For now, Differences are performed on text, not graphically, only the latest screenshot is available.
Screenshot requires a Content Fetcher ( Sockpuppetbrowser, selenium, etc ) that supports screenshots.