Pi-hole

Pi-hole is a network-level ad blocker that acts as a DNS sinkhole, blocking advertisements and trackers for all devices on a local network without requiring client-side software. It is self-hosted, typically on a Raspberry Pi or Linux machine, and is free and open-source software maintained by volunteer developers and funded through community donations.

5/ 100
Healthy
1No Decay→Stable

Score generated by AI agents based on publicly cited evidence and reviewed by the project maintainer. Not independently validated. Last assessed 2026-10-30.

Score History

MilestoneCriticalMajor
Origin Script (2014–2015) · 0/100Orig…Community Growth (2015–2017) · 2/100CommunityGrowthFormalization Era (2017–2020) · 3/100Formalization EraPlatform Maturity (2020–2025) · 3/100Platform Maturityv6 Rewrite Era (2025–present) · 5/100v6 Rewrite Era10075502502016202020242026-10Origin Script (2014–2015) · 0/100Community Growth (2015–2017) · 2/100Formalization Era (2017–2020) · 3/100Platform Maturity (2020–2025) · 3/100v6 Rewrite Era (2025–present) · 5/10002335MilestonesProject GitHub Repository Created (2014)Trademark Filed (2017)Events

Timeline events are AI-curated from public reporting. Score trajectory is derived from documented events.

Origin Script
0/100
2014-06-08 – 2015-02-17

Jacob Salmela created Pi-hole in 2014 as a bash script that turned a Raspberry Pi into a network-wide DNS ad blocker, an alternative to commercial hardware like AdTrap; its GitHub repository was created on June 8, 2014. It was a simple command-line tool with no web interface, funding model or organization behind it.

Community Growth
2/100+2
2015-02-17 – 2017-03-16

Lifehacker coverage in February 2015 brought a wave of users, and the project added a web interface in 2015, a guided installer in November 2015 and a Discourse forum in October 2016, reaching 1,000 GitHub stars by May 2016. The one notable lapse came in August 2016, when the team apologized that its pihole -d debug command had uploaded sensitive information without permission. Funding was informal, including an affiliate referral promoted on the blog.

Formalization Era
3/100+1
2017-03-16 – 2020-05-10

Pi-hole LLC filed the Pi-hole trademark in March 2017, opened a merchandise store, and released v3.0 with the FTL engine and an EUPL license in May 2017. Recurring donations and Patreon followed, and the 2018 retrospective reported eight developers and more than $31,000 raised. In June 2018 the team confirmed it enforces its trademarks against community projects, a source of friction with some contributors. v4.0 in August 2018 added FTLDNS, regex blocking and Docker support.

Platform Maturity
3/100
2020-05-10 – 2025-02-18

Pi-hole v5.0 introduced per-client group management and moved blocklists into a SQLite gravity database, and v5.1 expanded Teleporter so it exported and re-imported everything. Security flaws, including an authenticated RCE in 2020, stored XSS bugs, DNSSEC denial-of-service issues and a high-severity SSRF in 2024, were patched through public advisories. Most development effort went into the multi-year v6 rewrite, which entered beta in October 2023.

v6 Rewrite Era
5/100+2
2025-02-18 – present

The v6.0 release on February 18, 2025 replaced lighttpd and PHP with a web server and REST API embedded in FTL, moved configuration to a single TOML file and added native HTTPS, followed by weeks of migration hotfixes. In July 2025 a WordPress plugin flaw exposed donor emails, which the team disclosed in a public post-mortem. Through 2026, releases fixed dozens of security advisories and a log-flush data-loss bug while adding features, and the software stayed free and ad-free.

Alternatives

NextDNS13/100

Cloud-based DNS filtering that provides Pi-hole-like blocking without self-hosting any hardware. Free tier includes 300,000 queries/month; Pro is $1.99/month. Much easier setup — just change your DNS settings — but you're trusting a third party with your DNS queries instead of running your own server.

Free, open-source, self-hosted DNS ad blocker similar to Pi-hole, with a web interface and native support for encrypted DNS upstreams and DNS-over-HTTPS or DNS-over-TLS server operation. Filtering works at the domain level. Blocklist migration tools exist to move Pi-hole configurations over.

Dimensional Breakdown

Summaries below were written by AI agents based on the cited evidence. They are editorial interpretations, not independent research findings.

User Value Erosion
Pi-hole remains free software that keeps gaining features: the February 2025 v6.0 rewrite embedded the web server and REST API in FTL, added native HTTPS and shrank the Docker image from 113 MB to 38 MB, and 2026 releases added a long-requested static DHCP lease editor and cut long-term statistics memory use. The minor drawbacks are v6 migration bugs that needed several hotfix rounds, the removal of the temperature readout, and a log-flush bug, fixed in October 2026, that deleted all long-term history. A heavy run of security advisories in 2026 (privilege escalation, RCE and XSS issues) was disclosed and patched in each release rather than left open.
How It Got Here
Pi-hole has steadily improved since Jacob Salmela created it as a bash script in 2014. A web interface arrived in 2015 and a guided installer in November 2015. The one early lapse came in August 2016, when the team apologized that its pihole -d debug command had uploaded sensitive information without permission. Version 3.0 in May 2017 introduced the FTL engine, v4.0 in August 2018 added regex blocking, privacy levels and Docker support, and v5.0 in May 2020 brought per-client group management and a gravity database. The biggest change was v6.0 in February 2025, a multi-year rewrite that embedded the web server and REST API in FTL, consolidated configuration into one TOML file, added native HTTPS and cut the Docker image from 113 MB to 38 MB. It also brought migration bugs that took several hotfix rounds and dropped the temperature readout. Through 2026, releases added a static DHCP lease editor and memory savings, and fixed dozens of security advisories, including privilege escalation and remote code execution flaws, plus an October 2026 bug where flushing logs deleted all long-term history. A February 2025 long-term reviewer remained happy overall, and reported complaints are mostly about setup complexity and occasional over-blocking.
Business Customer Exploitation
Shareholder Extraction
Lock-in & Switching Costs
Twiddling & Algorithmic Opacity
Dark Patterns
Advertising & Monetization Pressure
Competitive Conduct
Labor & Governance
Regulatory & Legal Posture

Dimension History

2014Origin Script2015Community Growth2017Formalization Era2020Platform Maturity2025v6 Rewrite EraUser Value01001Biz Exploit00000Shareholder00000Lock-in01111Algorithms00000Dark Patterns00000Advertising00000Competition00111Labor/Gov00111Regulatory00001
Timeline (50 events)
critical2014-06-08

Pi-hole Project Repository Created on GitHub

Pi-hole's GitHub repository was created on June 8, 2014.

major2015-02-17

Lifehacker Coverage Drives Viral Adoption

Lifehacker published 'Turn A Raspberry Pi Into An Ad Blocker With A Single Command,' introducing Pi-hole to a mainstream audience. The article highlighted Pi-hole's one-line curl installer and drove significant traffic to the project, accelerating community growth and GitHub contributions.

major2015-05-07

First Web Interface Announced for Pi-hole

Pi-hole announced development of a web-based management interface, moving beyond the command-line-only tool. The interface would allow users to update settings, view statistics, and manage blocklists through a browser, significantly lowering the barrier to entry for non-technical users.

minor2015-07-25

Pi-hole 2.0 Web Interface Development Described

Pi-hole described work on a flat web interface using AdminLTE as a starting point. The post said users would be able to log in to view statistics or update lists; it described development work rather than announcing a completed release.

minor2015-11-18

Pi-hole Revamps Installer with Guided Setup

Pi-hole introduced a revamped installer with dialog windows that guide users through setup, along with a shorter installation command. Users no longer needed to set up a static IP before running the script.

minor2016-02-21

Pi-hole 2.5.3 Adds Upstream DNS Server Choices

Pi-hole 2.5.3 expanded DNS server options in the installer, allowing users to choose from multiple upstream DNS providers or define their own. The web admin page received a major overhaul with new graphs and charts for better visibility into blocking activity.

minor2016-04-29

Pi-hole Promotes an Affiliate Referral to a Publisher-Funding Subscription

A Pi-hole blog post encouraged readers to sign up for Optimal.com through the project's referral link, from which Pi-hole would receive a small share of the fee. The post said that, after credit card fees, Optimal paid 70% of subscriptions to more than 8,500 websites. It is an early example of the project's off-product affiliate funding.

minor2016-05-01

Pi-hole Reaches 1,000 GitHub Stars

Pi-hole celebrated reaching 1,000 stars on GitHub, reflecting growing community adoption. The project had begun as a personal script roughly two years earlier and was gaining traction among privacy-conscious technical users running Raspberry Pi setups at home.

minor2016-08-30

Pi-hole Apologizes After Debug Command Uploaded Sensitive Data Without Permission

With the Pi-hole 2.9 release, the team apologized that its pihole -d debug command uploaded some sensitive information without permission, as users had pointed out. It said a fix had been put in place quickly but the release was slow, and that it hoped to earn back users' trust.

minor2016-10-18

Pi-hole Discourse Community Forum Launched

Pi-hole launched its Discourse-based community forum at discourse.pi-hole.net, replacing an earlier less capable forum. The new platform became the primary venue for community support, feature requests, and development discussion. The team committed to monitoring all posts, though response times vary given the volunteer nature of the project.

minor2016-10-29

Pi-hole 2.9.5 Adds Pause/Resume Functionality

Pi-hole 2.9.5 introduced the long-requested ability to temporarily pause and resume ad blocking, along with a more privacy-conscious debug process using the team's own server for log uploads rather than third-party services.

minor2016-12-21

Pi-hole 2.10 Adds Web-Based Gravity Updates and Settings Page

Pi-hole 2.10 Core / 2.0 Web added the ability to run gravity (blocklist updates) from the web interface rather than only via command line. A new settings page provided centralized control over system configuration, and users could block or unblock domains directly from the query log.

minor2017-01-28

Pi-hole Adds Teleporter Export of Lists as a ZIP File

Pi-hole Core 2.12 / Web 2.4 introduced Teleporter, a community-requested feature that exports Pi-hole lists to a .zip file.

minor2017-03-16

Pi-hole Trademark Filed with USPTO

Pi-hole LLC filed a trademark application for 'Pi-hole' with the U.S. Patent and Trademark Office (serial number 87374408), covering software as a service for ad-blocking during internet usage. The project's trademark guidelines describe brand protection, permit fair use, and restrict use of the marks on merchandise and redistributed software.

minor2017-03-28

Pi-hole Swag Store Opens for Community Funding

Pi-hole launched a merchandise store selling t-shirts, mugs, and hoodies to help fund project infrastructure. Revenue from merchandise supplemented voluntary donations to cover hosting, legal, and development costs for the volunteer-driven project.

critical2017-05-01

Pi-hole v3.0 Launches with FTL Engine

Pi-hole 3.0 introduced the FTL (Faster Than Light) engine, a purpose-built API that read stats directly from memory rather than parsing log files. Performance improved dramatically, especially on older Raspberry Pi hardware, with the system tested handling over 100 million queries daily. The release also added IPv6 upstream DNS support, and web-based blocklist management. DHCP reservations were already available since Web v2.5.

major2017-05-01

Pi-hole Adopts EUPL v1.1 Open-Source License

Starting with v3.0, Pi-hole adopted the European Union Public Licence v1.1 as its open-source license. Code committed before v3.0 retained its original licensing. The project later used EUPL v1.2, whose compatibility terms are documented separately in the current-license evidence.

minor2017-07-20

Pi-hole Reaches 5,000 GitHub Stars and 10,000 Redditors

Pi-hole celebrated reaching 5,000 GitHub stars and 10,000 subscribers on its r/pihole subreddit. The project had grown from a personal script to one of the most popular Raspberry Pi projects, with Lifehacker coverage cited as an early catalyst for mainstream adoption.

minor2017-09-12

Pi-hole Launches Recurring Donation System

Pi-hole announced support for recurring monthly donations to sustain development. The project team had grown to six developers working in their spare time, with growing infrastructure costs.

minor2018-01-11

Pi-hole Publishes Open Source Philosophy Statement

Pi-hole published a blog post titled 'Pi-hole Is Open Source: Consume, Contribute, Or Both?' articulating its philosophy on open-source development. The post outlined how community members could contribute through code, testing, documentation, or donations, establishing norms for the growing contributor base.

major2018-05-29

Pi-hole Announces Its Patreon Page Is Live

Pi-hole announced that its Patreon page was live, offering rewards to supporters and inviting feedback on its reward levels.

minor2018-06-12

Pi-hole LLC Confirms It Enforces Its Trademark Against Community Projects

A forum thread opened with a complaint that Pi-hole LLC had started enforcing its trademark against community members, users and contributors over project names. A Pi-hole team reply confirmed that the project enforces its trademarks, saying not doing so would defeat their purpose.

critical2018-08-06

Pi-hole v4.0 Releases with FTLDNS and Docker Support

Pi-hole v4.0 replaced dnsmasq with FTLDNS (Pi-hole's fork of dnsmasq with integrated statistics), introduced regex-based blocking for complex filter patterns, added configurable privacy levels for query logging, and launched an official Docker image. The default blocking mode changed to NULL blocking, eliminating the need for iptables rules.

minor2018-12-31

2018 Retrospective: Eight Developers, $31K Raised

Pi-hole's 2018 retrospective revealed the project had grown to eight core volunteer developers, achieved 99.97% uptime for services, attracted over 1 million unique blog visitors, and generated over 22,000 Discourse forum posts. Patreon grew from $384/month to over $1,300/month. Total 2018 expenses were approximately $20,000 covering infrastructure, legal, taxes, and hardware.

critical2020-05-10

Pi-hole v5.0 Introduces Group Management and Gravity Database

Pi-hole v5.0 migrated blocklist storage from flat text files to a SQLite gravity database and added per-client group management, allowing administrators to apply different blocking rules to different devices. Deep CNAME inspection was introduced to catch domains hiding behind CNAME chains. The release also added regex/wildcard allowlisting and bar charts for 24-hour query history.

major2020-05-11

CVE-2020-11108: Authenticated RCE Vulnerability Disclosed

A high-severity vulnerability (CVE-2020-11108, CVSS 8.8) was disclosed in Pi-hole v4.4 and below, where the gravity updater could be exploited by authenticated users to upload arbitrary files and achieve remote code execution with root privilege escalation. The vulnerability was in gravity_DownloadBlocklistFromUrl and exploited unquoted curl parameters. A fix was merged on March 31 after the researcher contacted the team on March 29, before the public write-up on May 10.

minor2020-07-15

Pi-hole 5.1 Expands Teleporter Export and Import

Pi-hole 5.1 expanded the items included in Teleporter exports and made the importer restore everything the export contains. Export filenames also began including the hostname of the Pi-hole that created them.

minor2020-11-28

Pi-hole v5.2 Adds Client Subnet Discovery and MAC-Based Identification

Pi-hole Core/Web v5.2 and FTL v5.3 introduced the Client Subnet (ECS) feature to identify client IP addresses even behind NAT or proxy DNS servers. Clients could now be defined by MAC address for persistent identification regardless of DHCP changes. A new DHCP discovery feature scanned all interfaces for available DHCP servers.

minor2020-12-24

CVE-2020-35659: Stored XSS Vulnerability in Pi-hole Query Log

The DNS query log in Pi-hole before v5.2.2 was vulnerable to stored cross-site scripting. An attacker able to directly or indirectly query DNS with a malicious hostname could cause JavaScript to execute when an administrator viewed the Query Log or Long-term data Query Log page. The issue was fixed in v5.2.2.

minor2021-01-15

Pi-hole Adds SVCB and HTTPS Query Type Display

Pi-hole Web v5.3, Core v5.2.3, and FTL v5.4 added support for displaying SVCB and HTTPS DNS query types, which were increasingly used by modern browsers for service binding. The release also updated SQLite3 to v3.34.0 with a full shell interface exposed through pihole-FTL.

minor2021-08-04

Stored XSS Patched in Pi-hole Web v5.5.1

Pi-hole Web v5.5.1 patched a persistent XSS vulnerability where unfiltered user input added as a wildcard domain to blocklists or allowlists could execute arbitrary JavaScript in the web interface. The fix added proper input sanitization for domain entries.

minor2021-08-05

Donor Switches from Patreon to GitHub Sponsors; Team Addresses Notifications

A donor reported switching their sponsorship from Patreon to GitHub Sponsors and asked about missing release notifications. Pi-hole acknowledged forgetting the GitHub Sponsors email announcement for a hotfix and sent a notice to sponsors. This was an individual donor switch; both Patreon and GitHub Sponsors remained support options.

major2023-10-09

Pi-hole v6 Beta Testing Begins After Four Years of Development

Pi-hole announced beta testing for v6.0 after nearly four years of development. The new version represented a complete architecture overhaul: the web interface was rewritten in Lua, lighttpd and PHP were eliminated, and the REST API was embedded directly into pihole-FTL. The team warned that upgrading from v5 to v6 was strictly a one-way operation.

major2024-02-13

Pi-hole Patches Two DNSSEC Denial-of-Service Vulnerabilities

Pi-hole announced fixes for CVE-2023-50387 and CVE-2023-50868, both high-severity DNSSEC vulnerabilities affecting dnsmasq. Specially crafted DNSSEC answers could cause excessive CPU-intensive validation, enabling denial-of-service attacks against the DNS resolver. Fixes were already deployed to the v6 beta; the team said a stable release as FTL v5.25 would follow.

major2024-03-27

Authenticated File Read Vulnerability Patched in Pi-hole v5.18

Pi-hole Core v5.18 patched CVE-2024-28247, an authenticated arbitrary file read vulnerability with root privileges. The flaw in the gravity script allowed authenticated users to read system files through the file:// handler and view them in the web interface. The fix restricted local file reads to files explicitly readable by everyone on the system.

critical2024-07-05

High-Severity SSRF-to-RCE Vulnerability Fixed in Pi-hole v5.18.3

Pi-hole v5.18.3 patched CVE-2024-34361 (CVSS 8.6, High), a server-side request forgery vulnerability in gravity_DownloadBlocklistFromUrl() that allowed authenticated users to send internal requests. The advisory demonstrated escalation to remote command execution via the gopher:// handler when a suitable internal service, such as Redis, was present.

minor2024-08-18

Pi-hole Announces Preparation for General v6 Release

After 10 months of beta testing with over 250 discussion threads on the Discourse forum, Pi-hole announced preparations for the general release of v6.0. Development branches were being consolidated from development-v6 into main branches. The beta period had helped identify bugs, uncover new use cases, and polish the user experience.

critical2025-02-18

Pi-hole v6.0 Released: Complete Architecture Overhaul

Pi-hole v6.0 shipped after approximately five years of development, representing the largest architectural change in the project's history. The release embedded the web server and REST API directly into pihole-FTL, eliminated dependencies on lighttpd and PHP, consolidated configuration into a single TOML file, added native HTTPS with auto-generated TLS certificates, and introduced subscribed allowlists. The Docker image shrank from 113 MB to 38 MB by switching to Alpine Linux.

minor2025-02-21

Pi-hole v6 Post-Release Fixes Address Initial Issues

Within three days of the v6.0 release, Pi-hole published a post addressing early bugs, port fallback behavior, ignored legacy dnsmasq configuration, HTTPS performance and web-interface feedback. It listed initial hotfixes. Follow-up fixes through Core v6.0.5 were documented on March 4, including configuration migration fixes.

minor2025-02-21

Pi-hole v6 Removes Temperature Readout from Web Interface

Pi-hole explained that it removed the temperature display from the web interface during v6 development because sensor readings were inconsistent and debugging them took a lot of time for little gain. CPU and RAM usage statistics were kept.

minor2025-05-30

Pi-hole v6.2 Released with Performance and Stability Improvements

Pi-hole FTL v6.2, Web v6.2, and Core v6.1 delivered stability improvements and bug fixes following the major v6.0 release. The update addressed issues discovered during the initial months of v6 adoption and continued the rapid release cadence that characterized Pi-hole's post-v6 development.

critical2025-07-28

Donor Email Breach Discovered via GiveWP Plugin Vulnerability

Pi-hole discovered that approximately 29,926 donor names and email addresses had been exposed through a vulnerability in the GiveWP WordPress plugin used on pi-hole.net's donation page. Donors first reported receiving phishing emails at addresses used exclusively for Pi-hole donations. The donor data was visible in the webpage's source code without authentication due to the plugin flaw.

major2025-07-30

Pi-hole Publishes Transparent Post-Mortem of Donor Breach

Pi-hole published a detailed public post-mortem of the GiveWP donor email breach, criticizing the plugin vendor's 17.5-hour delay in notifying affected sites and their insufficient acknowledgment of the security impact. No financial data was compromised (handled by Stripe/PayPal), and the Pi-hole software itself was unaffected. The breach was added to Have I Been Pwned, with 73% of records already in its database.

minor2025-10-25

Pi-hole v6.3 Shortens TLS Certificate Validity to 47 Days

Pi-hole FTL v6.3 reduced the default validity of self-signed TLS certificates from one year to 47 days, with automatic renewal to compensate for the shorter validity period. This change followed industry best practices for certificate management. Improved default Content Security Policy headers provided better XSS protection.

minor2025-11-27

Pi-hole v6.4 Adds TOTP Rate Limiting Against Brute Force

Pi-hole FTL v6.4 introduced rate-limiting for TOTP (two-factor authentication) validation at a maximum of one attempt per second, preventing brute-force attacks against 2FA-protected Pi-hole instances. The release continued the post-v6 security hardening pattern.

minor2026-02-17

Pi-hole v6.5 Delivers 16% Gravity Performance Improvement

Pi-hole FTL v6.5 optimized gravity updates to reduce processing time by approximately 16% (from ~27s to ~23s with ~5 million domains). FTL now imports historical queries asynchronously on startup, allowing DNS resolution to begin immediately rather than blocking until the entire query history loads. A new database.forceDisk option reduces memory footprint on constrained hardware.

major2026-04-03

Pi-hole v6.6 Fixes Privilege Escalation, Injection and XSS Vulnerabilities

Pi-hole released FTL v6.6, Web v6.5 and Core v6.4.1, fixing multiple stored and reflected XSS and HTML-injection issues in the web interface, a local privilege escalation in Core, an authorization bypass that let read-only CLI API sessions import Teleporter archives, and a newline injection that let authenticated attackers add dnsmasq directives. FTL also stopped restarting during a running gravity update, which could previously leave Pi-hole unable to serve DNS.

major2026-07-06

Pi-hole v6.7 Closes Six Security Advisories and Adds DHCP Lease Editor

Pi-hole released FTL v6.7, Web v6.6 and Core v6.4.3, closing six advisories, four rated High: a local privilege escalation to root, web UI and API denial of service, a session expiration bypass, and remote code execution via CivetWeb configuration injection. The release also delivered a reworked static DHCP lease editor, which the team called one of the most requested improvements since v6.

minor2026-09-19

Pi-hole FTL v6.7.1 Fixes RCE Flaws and Locks Risky Settings Out of the Web UI

Pi-hole FTL v6.7.1 fixed three High-rated advisories, including remote code execution through webserver.advancedOpts and misc.dnsmasq_lines, plus a stack buffer overflow. In response, those two settings can no longer be changed through the API or web interface, though they can still be set in pihole.toml, environment variables or the command line.

major2026-10-17

Pi-hole v6.8 Fixes a Batch of Advisories and a History-Deleting Log Flush Bug

Pi-hole released FTL v6.8, Web v6.6.1 and Core v6.5, fixing more than a dozen security advisories across all three components, among them root-level command execution and file-write flaws in Core, app sessions that could read password hashes and the TOTP secret, and cross-site requests against installs with no password. The release also fixed a bug where flushing the logs deleted the whole long-term history instead of the last 24 hours, and cut long-term statistics memory use.

Evidence (43 citations)
Scoring Log (6 entries)
regrade2026-10-30CONFIRMED

5→5. No dimension moved: all 10 re-derived from the criteria tables and every one matched the existing score (D1 1, D4 1, D8 1, D9 1, D10 1; others 0). Since Feb 2026: FTL/Web/Core releases on Apr 3, Apr 24, May 11, Jul 6, Sep 19 and Oct 17 fixed dozens of security advisories (privilege escalation, RCE, XSS, DNS rebinding on passwordless installs) and a log-flush bug that deleted long-term history, and added a static DHCP lease editor. No pricing, ads, ownership, legal or labor changes. Eras: Origin Script re-dated 2014-07-01→2014-06-08 (repo creation); Community Growth re-dated 2016-01-01→2015-02-17 (Lifehacker coverage); Formalization Era re-dated 2017-05-01→2017-03-16 (Pi-hole LLC trademark filing); Platform Maturity re-dated 2020-05-01→2020-05-10 (v5.0); unlabeled current era re-dated 2026-02-28→2025-02-18 (v6.0 release) and labeled 'v6 Rewrite Era'. All eras re-scored from criteria: Origin 2→0, Community Growth 3→2, Formalization 3→3, Platform Maturity 4→3 (D1 1→0, D10 rated 0; scattered 1s removed where no event supported them; D8 1 from 2017 for trademark enforcement, D4 1 once configuration accumulated). Added 4 window events and 7 historical events (installer, 2016 debug-data upload, Teleporter 2017/2020, 2018 trademark enforcement, 2016 affiliate referral, v6 temperature removal). Skipped the logo-contest and trademark-registration candidates and the duplicate v6.4 event. Category 'Security & Privacy' looks right.

restore-check2026-10-30NO CHANGE

Checked all 5 restore candidates: 0 restored, 0 partly restored, 5 CONFIRMED REMOVED, 0 already present. timeline:remove:1 — CONFIRMED REMOVED: the live blog index (https://pi-hole.net/landing/blog/) and March archive (https://pi-hole.net/blog/2015/03/) establish an existing March 2015 post, not a March 1 launch of both blog and documentation. Three searches covering the claimed launch, March 2015 and adjacent years found no qualifying launch evidence. timeline:update:0 — CONFIRMED REMOVED for the dropped initial Reddit-sharing claim and July 1 dating: the original stars post (https://pi-hole.net/blog/2016/05/01/thank-you-for-1000-stars-on-github/) does not establish them. Bloomberg reporting read at https://adam.curry.com/art/1526056869_JpVk2cGa.html confirms the summer-2014/AdTrap/GitHub origin; those core facts already remain in evidence and origin prose. The founder account at https://www.raspberrypi.com/news/pi-hole-raspberry-pi/ also confirms the AdTrap motivation, but does not establish initial Reddit sharing. Three searches including adjacent origin years found no qualifying evidence for the dropped details. timeline:update:30 — CONFIRMED REMOVED: https://github.com/pi-hole/pi-hole/security/advisories/GHSA-jg6g-rrj6-xfg6 and https://github.com/pi-hole/pi-hole/releases/tag/v5.18.3 establish July 5 release/publication and the gopher:// handler; the CVE record at https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2024/34xxx/CVE-2024-34361.json rates the flaw High and records CISA exploitation status as poc on July 8, 2024. Three searches covering wild exploitation, Gopherus and date drift found no reliable pre-patch exploitation report. https://feed.craftedsignal.io/briefs/2026-09-pihole-ssrf-rce/ repeats Gopherus terminology but is not original substantiation and contradicts the primary advisory; https://docs.devguard.org/vulnerability-database/CVE-2024-34361/ says activity was observed without identifying an incident or pre-patch date. Neither warrants restoring the removed assertion. evidence:remove:6 — CONFIRMED REMOVED as unsupported: Crunchbase (https://www.crunchbase.com/organization/pi-hole) returned 403 and Wayback returned no readable copy; these failures are limitations, not disproof. Three searches covering the exact no-VC claim, Crunchbase and Tracxn/date drift found no qualifying source establishing no external investment. https://checkthat.ai/brands/pi-hole makes the claim and attributes an unfunded classification to Tracxn, but this AI-visibility profile is not original investment reporting or a verified underlying Tracxn record. Do not infer comprehensive investment history from donation support. milestones:remove:2 — CONFIRMED REMOVED: the 2017 trademark record at https://trademarks.justia.com/873/74/pi-87374408.html and Copyright (C) 2017 Pi-hole, LLC at https://github.com/pi-hole/pi-hole/blob/v3.0/LICENSE contradict formation in 2018. Neither establishes an exact formation date; no replacement milestone added. Explicit Wayback attempts for the three cited timeline URLs yielded no readable archive; no archive failure was used as disproof. No content removed and no scores changed.

fact-audit2026-10-29FABRICATION FOUND

Checked all 78 original timeline/evidence/milestone items and both alternatives (80 total), plus prose and fields. {'verified': 46, 'corrected': 19, 'resourced': 12, 'removed': 3}. Found an incorrect named protocol: timeline[30] says "Gopherus protocol", while its primary advisory specifies the gopher:// handler (https://github.com/pi-hole/pi-hole/security/advisories/GHSA-jg6g-rrj6-xfg6). Count one contradicted named technical detail; do not classify unsupported investor claims, an unverified title, wrong dates or the historically wrong EUPL version as invented. Preserved true Docker sizes, exact donor count, prompt CVE patch, and follow-up v6.0.5 fixes with proper supporting sources. Unsupported details counted by distinct claim, repeated prose counted once. Four supplemental evidence items support existing facts; no new developments added. [Amended by regrade 2026-10-30: evidence[28] title still read 'Transparent Community Governance' although the verifier found the thread is a complaint about trademark enforcement; retitled. evidence[3] title claimed GitHub stars indicate satisfaction, which contradicts the D1 summary; retitled.]

Deep Enrichment2026-03-15
Initial Scoring2026-02-28
Alternatives Review2026-02-28