M-Abozaid / esp32-c3-adblock
Pi-hole-class DNS ad-blocker on a $2 ESP32-C3 (no PSRAM): 537k domains as 40-bit FNV-1a hashes in flash, binary-searched. UDP DNS sinkhole + web dashboard. https://youtube.com/shorts/RaxszOUMi8E?feature=share
- Stars
- 3,553 stars
- Forks
- 403 forks
- Language
- C++
- License
- MIT
- Created
- Jun 19, 2026
- Last push
- Nov 6, 2026
- Updated
- Nov 12, 2026
Why these Tags: an agent read the README and quoted it
- Ad blocker from the description:
Pi-hole-class DNS ad-blocker on a $2 ESP32-C3 (no PSRAM)
- DNS from the description:
UDP DNS sinkhole + web dashboard.
- ESP32 from the readme:
Also builds for the **ESP8266** (NodeMCU / D1 mini, 4 MB flash) — see ESP8266 notes.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 10, 2026: 3,541 stars on 2026-11-10.
Star History
121 days recorded, Jul 15, 2026 – Nov 12, 2026 (UTC). Net change +3,555 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/M-Abozaid/esp32-c3-adblock) Badge
[](https://awesomerepos.com/M-Abozaid/esp32-c3-adblock) Timeline
It gained stars on 109 of the 121 days recorded since Jul 15, 2026.
Its largest 7 days were Oct 3, 2026 to Oct 9, 2026: 1,869 stars.
In the 30 days to Nov 12, 2026 it got 556 stars, 76% fewer than in the 30 days before.
- Created on the Repository Host
- Reached 100 stars, 29 days after it was created
- Reached 500 stars, 35 days after it was created
- Reached 1,000 stars, 107 days after it was created
- Release blocklist
- +379 stars in one day
- Largest star day recorded: +388 stars, 2 days after release blocklist
- +350 stars in one day
- Latest push
- Entered the Repository Index: 3,541 stars on 2026-11-10
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 3 Observations, Nov 11, 2026 – Nov 13, 2026. Forks +2. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 12, 2026: no new push
- Nov 13, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of M-Abozaid/esp32-c3-adblock.
Improve the Health Facts of the GitHub repository M-Abozaid/esp32-c3-adblock. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/M-Abozaid/esp32-c3-adblock. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. The newest release tag is a semantic version Fact: The newest release tag is blocklist. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
2 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-06, 6 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
1 of 3 checks (1 without data)-
Yes: A release in the last 365 days
Newest release blocklist on 2026-10-04, 39 days ago. 1 release in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is blocklist. Source
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)-
Yes: A licence
GitHub finds the licence MIT. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 13, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 13, 2026: 3,553 stars, 403 forks, last push Nov 6, 2026, not archived. One of 3 Observations since Nov 11, 2026.