Pi-Hole

pi-hole.net
Pi-Hole

Incredibly powerful, network-wide ad-blocker. Works out-of-the-box, light-weight with an intuitive web interface, but still allows for a lot of advanced configuration for power users. As well as blocking ads and trackers, Pi-Hole speeds up your network speeds quite significantly. The dashboard has detailed statistics, and makes it easy to pause/ resume Pi-Hole if needed.

Open Source

Pi-Hole Source Code

Author

pi-hole

Description

A black hole for Internet advertisements

#ad-blocker#blocker#cloud#dashboard#dhcp#dhcp-server#dns-server#dnsmasq#pi-hole#raspberry-pi#shell

Homepage

https://pi-hole.net

Repository

  • LicenseOther
  • Created08 Jun 14
  • Primary languageShell
  • Size9,344 KB
  • Stars61,823
  • Forks3,378
  • Watchers61,823

Language Usage

Language Usage

Project Health

  • Last commit20 minutes ago
  • Open issues35
  • Latest releasev6.6

Recent Commits

  • darkexplosiveqwx(11 Nov 26)

    Pi-hole core v6.6 (#6760)

  • Adam Warner(11 Nov 26)

    Merge commit from fork Fix piholeDebug.sh following symlinks and logging secrets (jvg9 + qfq3)

  • Adam Warner(11 Nov 26)

    Merge branch 'development' into fix/debug-redact-secrets Keep the tests of both sides in test/test_symlink_safety.bats. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(11 Nov 26)

    Merge commit from fork Do not let pihole-controlled paths steer root in checkout and uninstall

  • Adam Warner(11 Nov 26)

    Merge branch 'development' into fix/root-pihole-paths Keep the tests of both sides in test/test_symlink_safety.bats. Co-Authored-By: Claude Sonnet 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(11 Nov 26)

    Merge commit from fork Do not write into /etc/pihole as root from the installer (option A: keep install.log)

  • Adam Warner(11 Nov 26)

    Merge commit from fork Escape a custom `files.gravity` before splicing it into SQL

  • Dan Schaper(09 Nov 26)

    All symlink setups are forced Signed-off-by: Dan Schaper <[email protected]>

  • yubiuser(07 Nov 26)

    Bump trufflesecurity/trufflehog from 3.99.7 to 3.99.8 in the github-actions-dependencies group (#6759)

  • dependabot[bot](07 Nov 26)

    Bump trufflesecurity/trufflehog Bumps the github-actions-dependencies group with 1 update: [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog). Updates `trufflesecurity/trufflehog` from 3.99.7 to 3.99.8 - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](https://github.com/trufflesecurity/trufflehog/compare/31ce31ee1abbcc7dc8eee5764c17121c3044c8b2...ea68ca03c865c5f324e86e849ced20ed3cf9dbbb) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.99.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>

  • Adam Warner(06 Nov 26)

    Revise vulnerability reporting guidelines (#6757)

  • Dan Schaper(06 Nov 26)

    Revise vulnerability reporting guidelines Updated vulnerability reporting instructions to include GitHub's Security Advisory process. Signed-off-by: Dan Schaper <[email protected]>

  • DL6ER(18 Oct 26)

    Escape a custom `files.gravity` before splicing it into SQL A single quote in the path closed the `ATTACH DATABASE` literal in `gravity_copy.sql`, and everything behind it ran as SQL. Doubling it keeps the path one string literal. Signed-off-by: DL6ER <[email protected]>

  • Adam Warner(06 Nov 26)

    Do not log the password hashes or the TOTP secret in the debug log pihole -d logs /etc/pihole/pihole.toml through make_array_from_file, which redacted nothing, so webserver.api.pwhash, app_pwhash and totp_secret ended up in the debug log and in the tricorder upload (GHSA-qfq3-88xg-765w). The only existing redaction (pwhash in parse_file) is not used for this file. Replace non-empty values of these keys with "<removed>". Empty values are left as they are, so the log still shows whether one is set. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(06 Nov 26)

    Do not let pihole-controlled paths steer root in checkout and uninstall /etc/pihole and pihole.toml are controlled by the pihole user (GHSA-5w4v-f65m-323f): - pihole checkout wrote /etc/pihole/ftlbranch as root and chmod-ed it, following a symlink planted there. Write it as the pihole user instead, removing whatever is at the path first. - The uninstaller ran rm -rf on webserver.paths.webroot/webhome and rm -f on files.database, files.gravity and files.macvendor as root. Only remove the web interface directory if it is a checkout of the Pi-hole web repository, and delete the databases as the pihole user, before that user is removed. The defaults live in /etc/pihole, which is removed anyway. The macvendor.db download in the installer, also part of this advisory, is fixed together with GHSA-wp3p-45h3-2v82. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(06 Nov 26)

    Do piholeDebug.sh's work in pihole-owned directories as the pihole user /etc/pihole and /var/log/pihole are owned by the pihole user, who can replace any file in them with a symlink. pihole -d runs as root and read the logs and config files there with head/tail/sed, wrote the debug log with a plain redirect and then chmod/chown-ed it by path, so a planted symlink made root copy any file into the (pihole-readable) debug log, or truncate, overwrite and re-own any file (GHSA-jvg9-fm8x-2jqq). Do that work as the pihole user via setpriv instead, as pihole-FTL-prestart.sh and updatecheck.sh already do: - read files below those directories as that user - query gravity.db and pihole-FTL.db as that user (their paths come from pihole.toml, and pihole-FTL runs as that user anyway) - write the debug log as that user, removing whatever is at the path first, with mode 0640; the root chmod/chown is gone - upload it to tricorder as that user A symlink can then only lead to what the pihole user can already reach. The debug log is now owned by pihole:pihole instead of root:pihole. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(06 Nov 26)

    Write the install log as the pihole user `copy_to_install_log` truncated, `chmod`ed and `chown`ed /etc/pihole/install.log as root. A symlink planted there by the pihole user let it take over any file, or create one such as /etc/ld.so.preload. Root still reads the captured output, but the log is now written by pihole. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • Adam Warner(06 Nov 26)

    Do not write into /etc/pihole as root from the installer /etc/pihole is owned by the pihole user, who can therefore replace any path in it with a symlink. A root `pihole -r` or `pihole -up` followed such symlinks, so that user could take over files and directories elsewhere: 1. `move_old_dnsmasq_ftl_configs` created and `chown`ed `migration_backup_v6`, handing any directory to pihole. It now creates the directory as pihole, and pihole copies the world-readable v5 configs in. Root only removes the originals from the root-owned /etc/dnsmasq.d. 2. `installConfigs` created `hosts/custom.list` with `install -D`, which follows a symlinked `hosts/`. It is now created as pihole. 3. `FTLinstall` downloaded `macvendor.db` into /etc/pihole as root. It is now downloaded as pihole. /etc/pihole is handed to pihole right after the user is created, as a fresh install creates it root-owned before that. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Adam Warner <[email protected]>

  • darkexplosiveqwx(04 Nov 26)

    Allow running the test suite using podman (#6754)

  • darkexplosiveqwx(04 Nov 26)

    Add Fedora 45 to tests (#6753)

  • Dominik(04 Nov 26)

    use `setpriv` for dropping from root to pihole; stop requiring `sudo` (#6752)

  • darkexplosiveqwx(03 Nov 26)

    Allow running the test suite using podman Signed-off-by: darkexplosiveqwx <[email protected]>

  • darkexplosiveqwx(03 Nov 26)

    Add Fedora 45 to tests Signed-off-by: darkexplosiveqwx <[email protected]>

  • darkexplosiveqwx(01 Nov 26)

    use setpriv for dropping from root to pihole Signed-off-by: darkexplosiveqwx <[email protected]>

  • Dominik(02 Nov 26)

    Warn when a local repo is not marked as safe for git (#6746)

  • yubiuser(31 Oct 26)

    Bump trufflesecurity/trufflehog from 3.99.3 to 3.99.7 in the github-actions-dependencies group (#6750)

  • Adam Warner(31 Oct 26)

    Rely on the system's logrotate schedule instead of a nightly forced run (#6749)

  • Adam Warner(31 Oct 26)

    Rely on the system's logrotate schedule instead of cron The nightly "pihole flush once" cron job runs logrotate --force against the same state file and lock that the system's own scheduled logrotate uses (e.g. logrotate.timer). When the two coincide, one fails with exit status 3, and when they do not, the logs are rotated twice (the second rotation producing a near-empty stub). The @reboot run can race the system's catch-up in the same way. Remove both entries and let the system's logrotate handle rotation using /etc/logrotate.d/pihole. logrotate.timer (Persistent=true) and cron.daily with anacron already catch up after the machine was off. Fixes #6736 Signed-off-by: Adam Warner <[email protected]>

  • dependabot[bot](31 Oct 26)

    Bump trufflesecurity/trufflehog Bumps the github-actions-dependencies group with 1 update: [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog). Updates `trufflesecurity/trufflehog` from 3.99.3 to 3.99.7 - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](https://github.com/trufflesecurity/trufflehog/compare/e63326d6545de8f425d93ce24078c6e68d83f70e...31ce31ee1abbcc7dc8eee5764c17121c3044c8b2) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.99.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>

  • Dominik(30 Oct 26)

    Sample 1000 rows per index for ANALYZE (#6748)

Pi-Hole Security

6.3/10

Repo Security Summary

Updated 24 Aug 26

  • Maintained10/10
  • PackagingN/A
  • Dangerous-Workflow10/10
  • Code-Review10/10
  • Binary-Artifacts10/10
  • Token-Permissions0/10
  • CII-Best-Practices0/10
  • Fuzzing0/10
  • License9/10
  • Signed-ReleasesN/A
  • Branch-ProtectionN/A
  • Security-Policy10/10
  • SAST0/10
  • Pinned-Dependencies2/10

Security Advisories (11)

  • lowPatchedCVSS 2.2

    CVE-2026-119334file:// adlist read check and curl can resolve different files

  • highPatchedCVSS 7.3

    GHSA-mff6-cjc4-5wq9Pi-hole: gravity.sh chowns arbitrary directory to pihole via files.gravity config path (root LPE)

  • highPatchedCVSS 7.8

    CVE-2026-119335Local privilege escalation from `pihole` user to root via CVE-2026-41489 fix bypass

  • highPatchedCVSS 7.8

    CVE-2026-119336arbitrary root file clobber / chmod / disclosure via updatecheck.sh cron following /etc/pihole/versions symlink

  • highPatchedCVSS 7.8

    GHSA-j8vh-6fp9-cjcxLocal privilege escalation through pihole-FTL ambient CAP_CHOWN capability

  • highPatchedCVSS 8.8

    CVE-2026-50130Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate`

  • highPatchedCVSS 8.8

    CVE-2026-41489Local privilege escalation via config-controlled path in root-executed service hooks

  • mediumPatchedCVSS 6.4

    CVE-2026-33727Local Privilege Escalation (post-compromise, pihole -> root).

  • highPatchedCVSS 8.5

    CVE-2024-34361Blind Server-Side Request Forgery (SSRF) can lead to Remote Code Execution (RCE)

  • highPatchedCVSS 7.6

    CVE-2024-28247Authenticated Arbitrary File Read with root privileges

  • mediumPatched

    CVE-2021-29449Multiple Privilege Escalation Vulnerabilities Pihole

Pi-Hole Website

Website

Pi-hole – Network-wide Ad Blocking

Redirects

Does not redirect

Security Checks

All 65 security checks passed

Server Details

  • IP Address162.244.93.14
  • Hostnamelv-shared04.dapanel.net
  • LocationLas Vegas,Nevada,United States of America,NA
  • ISPWebhosting Holdings LLC
  • ASNAS965

Associated Countries

  • DEDE
  • NLNL
  • USUS

Safety Score

Website marked as safe

100%

Trackers

No known trackers found

Blacklist Check

pi-hole.net was found on 0 blacklists

  • AntiSocial Blacklist
  • Artists Against 419
  • Badbitcoin
  • Bambenek Consulting
  • CERT Polska
  • CoinBlockerLists
  • CRDF
  • CryptoScamDB
  • EtherAddressLookup
  • EtherScamDB
  • Fake Website Buster
  • MetaMask EthPhishing
  • NABP Not Recommended Sites
  • OpenPhish
  • PetScams
  • PhishFeed
  • PhishFort
  • Phishing.Database
  • PhishStats
  • PhishTank
  • Phishunt
  • RPiList Not Serious
  • Scam.Directory
  • SecureReload Phishing List
  • Spam404
  • StopGunScams
  • Suspicious Hosting IP
  • ThreatFox
  • ThreatLog
  • TweetFeed
  • URLhaus
  • ViriBack C2 Tracker

Website Preview

Website preview

Pi-Hole Docker

Container Info

pihole

A Linux network-level advertisement and Internet tracker blocking application which acts as a DNS sinkhole.

#Other#Tools

View on DockerHub

pihole/pihole:latest

Run Command

docker run -d \
  -p 53:53/tcp \
  -p 53:53/udp \
  -p 67:67/udp \
  -p 1010:80/tcp \
  -p 4443:443/tcp \
  -v /portainer/Files/AppData/Config/PiHole:/etc/pihole \
  -v /portainer/Files/AppData/Config/PiHole/DNS:/etc/dnsmasq.d \
  --restart=unless-stopped \
  pihole/pihole:latest

Compose File

version: 3.8
services:
  pi-hole:
    image: "pihole/pihole:latest"
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "67:67/udp"
      - "1010:80/tcp"
      - "4443:443/tcp"
    volumes:
      - "/portainer/Files/AppData/Config/PiHole:/etc/pihole"
      - "/portainer/Files/AppData/Config/PiHole/DNS:/etc/dnsmasq.d"
    restart: unless-stopped

Port List

  • 53:53/tcp
  • 53:53/udp
  • 67:67/udp
  • 1010:80/tcp
  • 4443:443/tcp

Volume Mounting

  • Container PathHost Bind
  • /etc/pihole/portainer/Files/AppData/Config/PiHole
  • /etc/dnsmasq.d/portainer/Files/AppData/Config/PiHole/DNS

Pi-Hole Reviews

More Ad Blockers

About the Data: Pi-Hole

Edit Pi-Hole Data

You can edit Pi-Hole's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external sources, a list of these can be found data documentation.

Origin Data

Modify Data

API

You can access Pi-Hole's data programmatically via our API. Simply make a GET request to:

https://api.awesome-privacy.xyz/v1/services/pi-hole

The REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.

Share Pi-Hole

Help your friends compare Ad Blockers, and pick privacy-respecting software and services.
Share Pi-Hole and Awesome Privacy with your network!