Features

• Block using hostname matching method
• No complex matching technique and hence it is very fast
• No complex object saving and hence it is memory friendly

---

• Load requested features from GitHub

1. What is "adHost" extension and how does it work?

   Normally ad-blocking add-ons rely on a RegExp based list of hostnames, domains, or keywords as the source to match the URLs that are requested against this list to either allow or reject the requests. In this extension, instead, a predefined list of hostnames that are known is matched against all the requested hostnames. This method is faster for sure but might not be as powerful as the RegExp alternative. Based on a few days of using this add-on, the hostname matching is sufficient for everyday usage. Although I recommend installing a popup blocker add-on along with this extension to have the full protection.

2. What is the default hostname list? Can I expand the list?

   By default, the extension adds all the hostnames listed in https://adaway.org/hosts.txt, https://hosts-file.net/ad_servers.txt, and https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext. You can extend this list by adding comma separated list of additional hostnames from the options page. Also, you can completely disable the extension in a certain top hostname pages by adding the name of it to the whitelist section.

   To check a hostname, open the options page. There is a textbox to check whether a hostname is going to be blocked or not. If not, you can add it into the list

3. What's new in this version?

   Please check the Logs section.

4. How can I report a new malicious hostname?

   Please open a bug report in the GitHub repository or add a comment in the review section

Matched Content

Reviews

What's new in this version

Need help?

If you have questions about the extension, or ideas on how to improve it, please post them on the support site. Don't forget to search through the bug reports first as most likely your question/bug report has already been reported or there is a workaround posted for it.