HaGeZi Blocklist: Structure, Impact, and False Positive Removal

HaGeZi Blocklist: Structure, Impact, and False Positive Removal

Kraken

When managing a web property or online application, sudden drops in user accessibility can often be traced back to Domain Name System (DNS) filtering. One of the most widely adopted filtering collections in the privacy and security community is the hagezi blocklist. When a domain is mistakenly added to this collection, legitimate visitors who rely on specific DNS resolvers or network-wide blockers lose the ability to load the website. Understanding how this system operates, who it affects, and how to submit an allowlist request is essential for site owners and network administrators dealing with unexpected access issues.

Understanding the HaGeZi DNS Blocklists

HaGeZi is a curated collection of community DNS blocklists hosted on GitHub and maintained by a single project maintainer. Unlike traditional antivirus software that scans individual files, executables, or page content using heuristic engines, this project deals strictly with domain names. It does not operate an automated web crawler or an independent reputation scanner. Instead, it aggregates, refines, and maintains lists of domains associated with advertisements, tracking scripts, telemetry, malware distribution, phishing, and scams.

When a user or organization integrates a hagezi blocklist into their network environment, their DNS filter checks every outgoing domain request against the active list. If a domain appears on the list, the DNS server refuses to resolve the address to an IP. Consequently, the website simply fails to load for anyone behind that specific filter, usually resulting in a browser connection error or a blank screen rather than a branded security warning page.

The Tiered Structure of the Lists

A defining characteristic of the HaGeZi project is its tiered filtering system. Rather than forcing everyone to use a single rigid list, the maintainer provides multiple tiers ranging from Light to Ultimate:

  • Light and Normal: Designed for minimal interference, blocking well-known ad networks, primary tracking domains, and confirmed malicious sites while keeping the risk of breaking everyday websites very low.
  • Pro and Pro++: More aggressive tiers that target broader telemetry, secondary tracking mechanisms, and domains that sit in grey areas between functional services and data collection.
  • Ultimate: The strictest tier, created for users who prioritize maximum privacy and security over convenience. Because it casts a much wider net, legitimate domains are far more likely to be caught as collateral damage on the Ultimate or Pro++ tiers than on the entry-level lists.

Alongside the main multi-purpose tiers, the project also maintains specialized lists. These include lists for Newly Registered Domains (NRD), Domain Generation Algorithms (DGA), the Most Abused Top-Level Domains (TLDs), and specific categories like gambling or piracy.

How Users Implement These Lists

To diagnose why a portion of your audience cannot reach your server, it helps to look at how everyday internet users and system administrators deploy these filters. In practice, people use the lists in two primary ways:

1. Local Filtering DNS Setups

Tech-savvy home users, small businesses, and IT administrators often run their own local DNS filtering software on hardware like a Raspberry Pi or a local server. The most common tools for this are Pi-hole and AdGuard Home. Users manually import the URL of their chosen HaGeZi tier into their dashboard. Every device connected to that local Wi-Fi or wired network is then filtered automatically. When someone on that network tries to visit a flagged domain, their local Pi-hole or AdGuard Home setup drops the request immediately.

2. Online DNS Services

A much larger group of people uses public or commercial online DNS services that have HaGeZi lists built directly into their infrastructure. Users do not need to manage the lists themselves; they simply change the DNS settings on their router, smartphone, or browser, and pick a filtering profile.

According to the project documentation, several prominent DNS providers integrate these lists into their services:

  • AdGuard DNS
  • ControlD
  • HaGeZi DNS
  • DNSBUNKER.org
  • Public RDNS
  • RobinGroppe.de
  • RethinkDNS
  • DNSwarden
  • OpenBLD.net

It is important to note that only visitors whose DNS setup actively uses a HaGeZi list are affected by a listing. Visitors on standard ISP connections or unrelated DNS resolvers will continue to reach your website without any interruption.

Distinguishing DNS Lists from Antivirus Engines

When a website owner discovers that users are being blocked, the initial reaction is often to check standard security aggregators like VirusTotal. However, DNS blocklists and traditional cybersecurity engines operate in separate ecosystems.

Scanning your URL on VirusTotal will show you whether security vendors such as Google Safe Browsing, Kaspersky, ESET, or Bitdefender flag your domain. While checking these is good practice, a completely clean report on VirusTotal does not mean your domain is clear of a DNS blocklist. HaGeZi lists are entirely independent from those commercial antivirus engines.

Conversely, if your domain has suffered a broader reputation issue—such as being hosted on a shared IP address with bad neighbors, or recently recovering from a compromised plugin—it might be flagged by multiple independent vendors simultaneously. If you find that your site is blocked across several different platforms, you must handle each vendor according to its own rules. You can use a central resource to check which antivirus engine or blocklist flags your website and track down the right submission channels. For instance, clearing a DNS filter will not remove an endpoint security block; for that, you would need to follow a dedicated CyRadar false positive report guide or submit individual appeals to ESET, Kaspersky, or Google Safe Browsing.

How to Verify If Your Domain Is Flagged

Before submitting a removal request, you must confirm that a HaGeZi list is actually the source of the block, and identify which exact list and rule are responsible. There are three reliable ways to check this:

Use the HaGeZi Blocklist Lookup Tool

The project provides a dedicated web utility called the HaGeZi Blocklist Lookup (accessible at hagezi-mirror.dnsbunker.org/listseek.php). This is the definitive way to check your status.

  1. Open the lookup page in your browser.
  2. Paste your domain name into the search box. You can check up to 50 domains at a time, entering one per line. If you paste a full URL, the tool automatically strips it down to the base domain.
  3. If your domain was registered recently, make sure to tick the checkbox labeled Include NRD and DGA lists, as these are excluded from the default search.
  4. Run the search. The tool reads the currently published lists and returns a result card for each entry, naming every specific HaGeZi list that blocks the domain along with the exact filtering rule.

Test on a Filtered Device

If you have access to a test device configured to use a service like ControlD or AdGuard DNS with a HaGeZi profile enabled, try loading your website there while comparing it to a standard mobile data or residential connection. If the domain fails to resolve on the filtered connection but loads normally everywhere else, a DNS filter is actively blocking it.

Gather Details from Affected Users

When a customer or visitor contacts you to report that your site is unreachable, ask them two specific questions:

  • Which DNS service, browser extension, or network filter are they running?
  • Which specific list tier (such as Normal, Pro, or Ultimate) have they selected?

Step-by-Step Guide to Requesting Removal

Once you have confirmed via the lookup tool that your domain is listed by mistake, you can ask the maintainer to fix it. If you want a quick summary of the required fields before starting, you can review this hagezi blocklist removal overview, or follow the complete walkthrough below.

Step 1: Verify That the Block Is a True False Positive

Before opening a ticket, inspect your own website thoroughly. Make sure the site is clean of any malware, unauthorized redirects, or deceptive scripts.

You should also confirm that the breakage is caused by your primary domain being on a HaGeZi list, rather than a third-party domain that your website loads. Sometimes a site fails to render properly because an external Content Delivery Network (CDN), analytics script, or font provider is blocked. Furthermore, verify that the block is actually unintended. If your domain is a gambling portal or hosts copyrighted files and appears on a dedicated gambling or piracy blocklist, the block is functioning as designed, and the maintainer will decline the removal request.

Step 2: Open an Allowlist Request on GitHub

The official and fastest method to get a false positive resolved is through the project's GitHub repository.

  1. Navigate to github.com/hagezi/dns-blocklists/issues and click the button to open a new issue.
  2. You will be prompted to sign in to GitHub. If you do not have an account, you can register a free personal account; the process does not require a corporate email address or company verification.
  3. From the list of issue templates, select Allowlist Request.

Step 3: Fill Out the Request Form Accurately

The GitHub template presents a structured form with required checkboxes and text fields in a specific order. Providing clear, accurate answers speeds up the review process significantly:

  • Prerequisite Checkboxes: You must tick both initial boxes confirming that you are testing against the current version of the lists, and that temporarily disabling the lists resolves the access issue.
  • Operating System: State the OS where the issue was observed (e.g., Windows, macOS, Android, Linux).
  • Which blocklist(s) caused the issue: Enter the exact name and tier you found during your lookup (for example, Multi PRO or Ultimate). Even if you discovered the block through a third-party resolver like AdGuard DNS or ControlD, you must name the underlying HaGeZi list here.
  • Where does the issue occur - on which website or in which app?: Provide the address of the broken site or the name of the application. To prevent live links in the ticket, it is common practice to defang the URL (for example, writing hxxps://example[.]com).
  • Which domain(s) need to be unblocked?: List the exact domain name(s) that need to be added to the allowlist (e.g., example[.]com).
  • Why should the domain(s) be unblocked?: Write a concise, factual explanation. State your relationship to the domain, what the site does, which list it appears on, and confirm that it does not host ads, trackers, or harmful content.

For example, a clear explanation looks like this:

example[.]com is the official website of our company, Example Ltd. The Blocklist Lookup shows it flagged on Multi PRO. We own the domain and operate the site directly. The website contains no advertisements, tracking scripts, or malicious downloads, and visitors using this list tier cannot open our pages. Please remove it from the blocklist.
  • Final Confirmations: Tick all the closing confirmation boxes verifying that you checked the domain with the Blocklist Lookup tool, that the request has not already been declined in a past issue, and that you have provided sufficient detail. Do not include any private personal data or sexually explicit content in your submission.

Step 4: Monitor the Issue and Wait for Propagation

After submitting the form, monitor the GitHub issue thread. While the project does not guarantee a fixed turnaround time, the maintainer is active and the project FAQ notes that GitHub issues are the fastest route to a fix. If you are completely unable to use GitHub, the project FAQ also lists an alternative support email address, though GitHub remains the primary channel.

Once the maintainer closes the issue and removes the domain, you can verify the fix by running the Blocklist Lookup tool again. Keep in mind how list updates propagate:

  • The Blocklist Lookup mirror runs up to a full day ahead of the public copies hosted on GitHub, GitLab, and Codeberg.
  • After the public repository updates, third-party services like ControlD or AdGuard DNS—as well as local Pi-hole installations—need time to fetch and refresh their local copies of the list, which usually happens on a daily schedule.

Important Rules and Exceptions to Keep in Mind

Before filing an allowlist request or troubleshooting a blocked domain, site owners should be aware of several specific policies established by the project maintainer:

Newly Registered Domains (NRD)

Cybercriminals frequently register fresh domains for short-lived phishing and malware campaigns. Because of this, many security-conscious users subscribe to NRD blocklists, which automatically block any domain for a set period after its initial registration. The HaGeZi project explicitly states that its NRD lists come with "no guarantees, no support, and no formal process for fixing false positives." If your domain is blocked solely because it was registered last week, an allowlist request will not clear it from the NRD feed; you simply have to wait for the domain to age out of the newly registered window.

Most Abused TLDs List

Certain top-level domain extensions are heavily favored by spammers due to low registration costs. On the HaGeZi Most Abused TLDs list, whole extensions may be restricted. For this specific list, the maintainer only considers exclusion requests for well-established domains that appear on major global ranking lists—such as Cisco Umbrella, Cloudflare Radar, or the Tranco list—or domains that are strictly required for popular, widely used applications to function.

The project documentation emphasizes that including a domain on a blocklist is a technical filtering decision made to satisfy the preferences of the list's users, not a legal accusation or moral judgment against the business. Because the higher tiers (like Pro++ and Ultimate) are designed to aggressively strip out anything resembling tracking, affiliate marketing, or promotional telemetry, domains that rely on those technologies may be blocked intentionally on those tiers.

By understanding the distinction between standard antivirus detections and DNS-level filtering, and by providing the exact list name and rule from the lookup tool, legitimate website owners can resolve false positives efficiently. For further help with DNS filters or other security vendors, you can always follow step-by-step guides to fix false positives and restore full access for your visitors.

Report Page