Website profiles · Technology insights · Alternatives

ublacklist.github.io

uBlacklist is a browser extension that filters Google Search results, available for Chrome, Firefox, Edge, and Safari. Chrome Web Store Firefox Add-ons Edge Add-ons App Store (maintained by Group-Leafy) GitHub Demo Features Completely block unwanted sites from appearing in search results Block sites by specific URLs using match patterns or regular expressions Block sites by specific titles using regular expressions Highlight preferred sites in search results Support for Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex Synchronize rulesets across devices using Google Drive, Dropbox, OneDrive, WebDAV, or browser sync Subscribe to public rulesets

No paid content found Multilingual
Visit website
Profile views 10 Outbound visits 1 Normal
uBlacklist Full homepage screenshot

At a glance

Category
Development
Language
English
Paid-content signal
No paid content foundObserved
Registered
2013
Hosting
FastlyInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is uBlacklist?

uBlacklist is a browser extension that filters search results. Instead of blocking ads or trackers, it removes or highlights entire sites in the results pages you already use—mainly Google Search, but also Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex. It runs on Chrome, Firefox, Edge, and Safari.

It is aimed at people who keep seeing the same low-value domains in search results—content farms, scraped copies, spammy forums—and want them gone without switching search engines.

H3 What it can do

  • Completely block unwanted sites from appearing in search results.
  • Block sites by specific URLs using match patterns or regular expressions.
  • Block sites by specific titles using regular expressions.
  • Highlight preferred sites in search results rather than hiding them.
  • Synchronize rulesets across devices using Google Drive, Dropbox, OneDrive, WebDAV, or browser sync.
  • Subscribe to public rulesets, so you can start from a maintained blocklist instead of writing every rule yourself.

H3 How it compares to similar tools

Approach What it filters Where it works Main trade-off
uBlacklist Search result entries, by site, URL or title Multiple search engines Only affects search results, not the sites themselves
Search engine built-in filters Limited safe-search or domain preferences One engine Little control, rarely portable
Ad/tracker blockers Ads and tracking scripts Across the web Usually do not remove organic search results

H3 A practical example Suppose you search for a recipe and the first page is full of copied versions from one aggregator. You add that domain as a rule in uBlacklist; those results disappear from Google, Bing and DuckDuckGo on every device where your ruleset syncs. If you would rather keep them visible but deprioritized, use the highlight feature for sites you trust instead.

H3 Deciding whether to use it Choose uBlacklist if you want per-site control over search results and use more than one search engine. Skip it if your problem is ads on pages rather than results, or if you only ever use one search engine that already lets you block domains. Also consider that regex title rules can be powerful but need care—an overly broad pattern can hide legitimate results.

A useful next step: install it in one browser, subscribe to one public ruleset, and add just two or three domains you personally distrust. Widen the rules only after you see how it behaves. For browser-level alternatives, Chrome Web Store and Firefox Add-ons list related extensions, though their filtering goals differ.

How do I install uBlacklist on Chrome, Firefox, Edge, or Safari?

Install uBlacklist from your browser's own extension store, because it ships as a native add-on for Chrome, Firefox, Edge and Safari rather than as a manual script or a single cross-browser package.

  • Chrome: install from the Chrome Web Store.
  • Firefox: install from Firefox Add-ons (AMO).
  • Edge: install from the Edge Add-ons store.
  • Safari: install from the App Store; the Safari version is maintained by Group-Leafy.

After installing, open the extension's options page to add your first blocked site, then reload your search results to see the effect. If you have a ruleset you already trust, subscribing to it is faster than typing rules by hand; otherwise start with one or two domains you never want to see again and confirm they disappear.

A practical next step: if you use several browsers or machines, set up rule synchronization so you aren't rebuilding the same list four times. uBlacklist supports Google Drive, Dropbox, OneDrive, WebDAV and browser sync for this.

One trade-off to weigh before installing: the extension filters results on Google plus Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN and Yandex, but it does not change the underlying search index. Blocked sites still exist; they are simply hidden from your result pages. If you need a site occasionally, use a URL or title pattern that is narrow rather than blocking the whole domain.

For background on the project and its documentation, see uBlacklist and the source repository on GitHub.

How can I block specific websites from appearing in my Google search results?

Install a search-result filter extension rather than relying on Google's built-in tools. uBlacklist is one option: it removes chosen sites from Google results and also works with Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex.

What it actually does

  • Blocks whole domains so they never appear in your results.
  • Blocks by URL pattern — match patterns or regular expressions, useful for subdomains or specific paths.
  • Blocks by title using regular expressions, which catches pages whose URLs vary but whose titles are predictable.
  • Highlights preferred sites, so good sources stand out instead of being buried.
  • Syncs rules across devices via Google Drive, Dropbox, OneDrive, WebDAV, or browser sync.
  • Subscribes to public rulesets, so you don't have to build every rule yourself.

Matching the tool to your situation

Situation Best approach
A few content farms keep resurfacing Add each domain by hand
One site floods results with many subdomains URL pattern or regex
Pages change URLs but keep the same title Title regex
Many people share the same junk sites Subscribe to a public ruleset
You work across laptop and phone Enable sync

A concrete example

Suppose a forum keeps appearing for technical queries but its threads are outdated. Add the domain as a rule, then test with a search you know triggers it. If the same operator runs several subdomains, switch to a wildcard or regex rule so you don't repeat the work.

Trade-offs to weigh

  • Regex rules are powerful but easy to write too broadly; a bad pattern can hide sites you wanted.
  • Public rulesets save time but reflect someone else's judgment, so review what you subscribe to.
  • A filter changes what you see, not what Google indexes — your results are personalized to your rules, not objectively cleaner.

Next step

Pick the extension for your browser (Chrome, Firefox, Edge, or Safari), add one domain you're tired of seeing, and run a test search. Once that works, decide whether a shared ruleset is worth subscribing to. For a second opinion on which filters exist, GitHub hosts the project and its rule lists, and Chrome Web Store lists the extension for Chrome users.

How do I use match patterns or regular expressions to block sites by URL or title?

uBlacklist supports two rule formats: match patterns and regular expressions. Match patterns are simpler and cover most URL-blocking needs; regular expressions are more powerful and are also the only way to block by page title.

Match patterns (URLs only)

A match pattern looks like *://*.example.com/*. The * wildcard stands in for any characters, so this pattern blocks every page on example.com and its subdomains across HTTP and HTTPS. To narrow it, be more specific: *://example.com/forum/* blocks only the forum section. Match patterns are the right choice when you know the domain you never want to see again.

Regular expressions (URLs and titles)

Regular expressions match against the full URL or the page title and let you combine conditions. For example, a URL regex could target a query string or a path fragment that a simple pattern cannot express, such as URLs containing both a domain and a specific keyword. For titles, you write a regex that matches the words you want gone — useful when spammy pages share a title formula rather than a single domain.

The key difference:

Match patterns Regular expressions
Applies to URLs URLs and titles
Difficulty Low Moderate
Best for Blocking whole domains or sections Blocking by keyword, path logic or title

A practical workflow

Start with match patterns for the obvious offenders. When you notice results that keep slipping through — same phrasing in the title, or a URL pattern across many domains — add a title or URL regex for that. Test a new rule on a search you can re-run so you can confirm it removes the right results and nothing else.

If you would rather not build rules yourself, uBlacklist can subscribe to public rulesets, which are collections maintained by other users. That is often the fastest route: subscribe first, then add personal rules for what the shared lists miss. Rulesets can also be synchronized across devices via services such as Google Drive, Dropbox or browser sync, so your rules follow you between browsers.

For a second opinion on what a site actually is before you block it permanently, Reddit discussions and Hacker News threads often surface whether a domain is low-quality or merely unfamiliar.

How do I synchronize my uBlacklist rulesets across multiple devices?

uBlacklist supports several ways to sync rulesets across devices: Google Drive, Dropbox, OneDrive, WebDAV, or the browser's built-in sync. Which one you pick depends on where you already store files and which browsers you use.

Choosing a sync method

  • Browser sync — simplest option if all your devices run the same browser family with sync enabled (for example, Chrome on desktop and Android). No extra account or configuration.
  • Google Drive / Dropbox / OneDrive — good when you mix browsers or platforms, since the ruleset lives in your cloud account rather than in one browser's sync service.
  • WebDAV — the choice if you run your own server (Nextcloud, for example) and prefer to keep the ruleset out of third-party cloud storage.

How to set it up

  1. Install uBlacklist on each device (Chrome, Firefox, Edge, and Safari are supported).
  2. Open the extension's options page and find the sync section.
  3. Select your provider and authorize the connection if prompted.
  4. On your other devices, connect the same account or server.
  5. If you use public rulesets, subscribe to them on each device — subscriptions and your personal block list are separate, so confirm both are present after syncing.

Practical notes

A concrete scenario: you block a set of sites on your work laptop, then want the same list on a personal desktop and phone. Browser sync handles this with no setup beyond signing into the browser; a cloud provider handles it even if the phone runs a different browser.

Two trade-offs worth knowing. First, syncing a ruleset is not the same as syncing subscriptions — if you rely on community-maintained lists, check that each device is subscribed, not just connected. Second, WebDAV gives you the most control but requires you to keep the server reachable and credentials current; a lapsed connection can leave devices silently out of date.

If you only use one browser everywhere, start with browser sync and skip the rest. If you mix browsers or want the list portable, pick the cloud service you already use daily.

Where can I find and subscribe to public rulesets for uBlacklist?

Public rulesets for uBlacklist are shared as subscription URLs — plain text lists of blocked (or highlighted) sites that the extension can pull in and keep updated. You subscribe to one by pasting its URL into uBlacklist's options under the rulesets/subscriptions section, rather than installing anything from a store.

Where to look:

  • The project's own repository and README. The uBlacklist project on GitHub links to community-maintained ruleset collections and explains the subscription format. Start here because the format details matter.
  • Community "awesome" lists. Search GitHub for uBlacklist ruleset collections; several maintainers publish curated lists grouped by topic, such as content farms, AI-generated spam, or region-specific low-quality sites.
  • Individual maintainers' pages. Many rulesets live on a person's GitHub Pages or repository, with a raw file URL you subscribe to directly.

When choosing a ruleset, weigh these trade-offs:

Consideration Why it matters
Scope A broad "spam" list blocks more but risks hiding sites you actually want
Maintenance Check the last commit date; stale lists miss new spam domains
Transparency Prefer lists you can read and inspect before subscribing
Overlap Multiple lists can duplicate rules; a few well-maintained ones beat many
Highlight vs. block Some rulesets promote preferred sites instead of blocking others

A practical next step: open uBlacklist's options, find the ruleset/subscription field, and add one well-maintained list first. Search for a term you know is polluted, confirm the results look better, and only then add more lists. If something useful disappears, remove that ruleset or add the site to an allowlist rather than abandoning the extension.

You can also sync your chosen rulesets across devices via Google Drive, Dropbox, OneDrive, WebDAV, or browser sync, so a subscription you set up on one machine follows you to the others.

Related questions

More questions →
What Can an Amazon Seller Browser Extension Actually Do for Your Listings?

An Amazon seller browser extension is a small piece of software that runs inside Chrome, Edge, or Firefox and adds information or shortcuts directly onto Amazon pages you already visit. In practice, it can overlay demand and competition data on a product page, pull quick numbers while you browse a niche, flag missing or weak listing elements, and save you from switching between tabs. What it cannot do is replace a full listing engineering or growth platform: extensions are lightweight, page-level helpers, while serious listing work — keyword architecture, AI-readiness, bulk optimization, and performance tracking over time — needs a dedicated toolset. The useful question is not "extension or platform" but "which jobs belong to each."

What a browser extension typically does well

Most seller extensions cluster around a few repeatable, on-page tasks. If your workflow involves a lot of browsing, these are where the time savings are real.

On-page data overlays

While you're on a product detail page, the extension can display estimated sales, revenue, review velocity, seller count, and price history in a panel next to the listing. This turns "open a separate research tab and paste the ASIN" into "read the number where you already are." For quick sanity checks on a competitor or a potential product, that's a genuine speed gain.

Quick product and niche research

Extensions often let you scan a search results page and see metrics for every listing at once, or export a batch of ASINs. This is useful for early filtering: you can spot which results have thin review counts, unstable pricing, or a dominant seller, and decide which few are worth deeper analysis.

Listing checks and basic audits

Some extensions highlight on-page elements — title length, bullet presence, image count, whether A+ content appears, whether key fields look empty. This is a fast visual audit, not a scoring system. It tells you what's there, not whether your listing is engineered to match how Amazon discovery works now.

Convenience features

Coupon and deal finders, price-drop alerts, review-request shortcuts, and quick links to seller tools fall into this bucket. They're small quality-of-life wins rather than strategy.

Where extensions fall short

This is the part sellers most often underestimate. An extension sees the page in front of you; it doesn't hold your catalog, your history, or your strategy.

Job Browser extension Full listing/growth platform
On-page competitor snapshot Yes, fast Yes, often deeper
Keyword architecture across a listing No Yes
AI-readiness / discovery optimization Rarely Core function
Bulk edits across many ASINs No Yes
Tracking your own listings over time Limited Yes
Historical trend and seasonality Usually shallow Yes
Team workflows and permissions No Yes

The pattern: extensions are read-and-react tools for pages you're already on. Platforms are build-and-manage tools for your own catalog. If your bottleneck is "I need to know if this niche is worth entering," an extension helps. If your bottleneck is "my listings aren't converting or aren't being surfaced the way Amazon discovery now works," an extension won't fix that — you need listing engineering, not a data overlay.

Scenarios: when an extension earns its place

  • Early product research. You're scanning dozens of search pages a day. An overlay that shows demand and competition inline saves hours of tab-switching. Worth it.
  • Competitor spot-checks. You want a fast read on a rival's pricing and review momentum before a pricing decision. An extension gives you that in seconds.
  • Quick listing sanity checks. You're about to publish and want to confirm images, bullets, and title are all present. A visual audit extension is handy.
  • Ongoing listing optimization. You need to align titles, bullets, and backend terms with how Amazon's discovery systems interpret intent, and to keep that consistent across a catalog. This is platform territory — an extension can't hold or apply that structure.
  • Scaling a catalog. Once you're managing many ASINs, bulk operations, version history, and team access matter more than any single-page overlay.

What to check before installing any extension

Extensions can read the pages you visit, and some request broad permissions. Before you install:

  1. Read the permission list. Does it need access to all sites, or only Amazon domains? Broader access than the job requires is a yellow flag.
  2. Check what data leaves your browser. Does it send your browsing or seller data to a server? Is that disclosed?
  3. Confirm the vendor. Prefer extensions from established sellers/tool providers with a real product behind them, not anonymous one-off add-ons.
  4. Test on a non-critical account first. If it touches your Seller Central session, verify behavior before relying on it.
  5. Know the exit. Can you disable it cleanly, and does uninstalling remove stored data?

How to decide if it fits your stage

Ask three questions:

  • Is my main pain "I browse a lot and want data inline"? An extension is likely worth it.
  • Is my main pain "my listings underperform and I need to engineer them properly"? Skip the extension-first mindset; look at a listing/growth platform.
  • Am I managing more than a handful of ASINs? You'll outgrow page-level tools quickly; extensions become a supplement, not the system.

A practical setup for many sellers is both: an extension for fast on-page research, and a dedicated platform for the listing work that actually moves rankings and conversion. ZonGuru, for example, positions its toolset around listing engineering and AI-readiness rather than page overlays — the kind of work an extension structurally can't do. If you want to see where a full platform picks up, its pricing page outlines the options, and there's a free trial to test the workflow before committing.

The short version: a browser extension is a fast, cheap way to see more while you browse. It is not a listing strategy. Use it for the browsing jobs, and bring in a real platform for the engineering jobs — that division is what keeps your time and your listings both working.

How to Synchronize uBlacklist Rulesets Across Devices

uBlacklist can sync your rulesets across devices through Google Drive, Dropbox, OneDrive, WebDAV, or browser sync. You set this up once in the extension's options, and every device signed into the same sync account pulls the same rules. This works on Chrome, Firefox, Edge, and Safari, so you can mix browsers and still keep one consistent blocklist.

What "sync" actually covers

uBlacklist has two separate things people often confuse:

  • Your own rules — the sites, URL patterns, and title regexes you add yourself.
  • Subscribed public rulesets — shared blocklists you subscribe to, which update on their own.

Sync applies to your rulesets so that edits made on one device appear on the others. Subscriptions are a rule source: once you subscribe to a public ruleset, it feeds entries into your blocking setup, and you can rely on it instead of hand-maintaining every domain.

Sync methods available

Method Typical use
Google Drive You already live in Google's ecosystem
Dropbox Cross-platform, works well on desktop and mobile
OneDrive Microsoft account users
WebDAV Self-hosted or third-party storage you control
Browser sync Simplest option if you stay within one browser's account

Pick one and use it on every device. Mixing methods across devices is the most common reason rules look "missing."

Step-by-step setup

  1. Install uBlacklist on each device. Use the store for your browser — Chrome Web Store, Firefox Add-ons, Edge Add-ons, or the App Store (the Safari version is maintained by Group-Leafy).
  2. Open the extension's options page on the first device. This is where sync settings live.
  3. Choose a sync service from the list above and connect your account. The extension will ask you to authorize access to that storage.
  4. Add or import your rules on this device. If you already have a ruleset, this becomes the source of truth.
  5. Repeat the sync setup on your other devices, selecting the same service and account.
  6. Verify by adding a test rule on one device, then checking that it appears on another after the sync cycle completes.

Expected result: the same blocked sites and patterns apply everywhere, and a change on one device propagates to the rest.

Common snags

  • Different sync services per device. Rules won't merge — each service holds its own copy. Standardize on one.
  • Not signed in. Browser sync and cloud sync both require an active account session; a logged-out device won't pull updates.
  • Confusing subscriptions with your rules. A public ruleset you subscribe to updates independently. If a site is still blocked after you remove your own rule, check whether a subscription is supplying it.
  • Safari behaving differently. The Safari build is maintained separately, so confirm sync is configured there too rather than assuming it inherits desktop settings.

A practical setup

If you want minimal maintenance: subscribe to one or two reputable public rulesets for broad coverage, then use cloud sync (Drive, Dropbox, or OneDrive) for the handful of personal rules you add on top. That way the shared lists stay current on their own, and your custom entries follow you across every browser and device.

Where to Install uBlacklist and Try Its Demo

uBlacklist is available from the official extension stores for Chrome, Firefox, Edge, and Safari, and its source code and demo are hosted on GitHub. Use the store link that matches your browser; use GitHub if you want to inspect the project or try the demo before installing.

Install uBlacklist on your browser

Pick the entry that matches the browser you actually use. Each store handles installation and updates for that platform.

Browser Where to install
Chrome Chrome Web Store
Firefox Firefox Add-ons
Edge Edge Add-ons
Safari App Store (maintained by Group-Leafy)

The Safari build is listed as maintained by Group-Leafy, so treat it as a separately maintained distribution rather than the same package as the Chrome, Firefox, and Edge builds.

Source code, demo, and project page

The GitHub project page is the reference point for the extension itself. From there you can reach:

  • The Demo, to see how filtering behaves before committing to a setup.
  • The source code, if you want to review what the extension does.
  • Issue tracking and release information tied to the project.

If your goal is simply to filter search results, install from your browser's store. If your goal is to evaluate the tool first, start with the demo on GitHub, then install from the store once you're satisfied.

What you get after installing

uBlacklist filters search results rather than blocking sites at the network level. Its documented capabilities include:

  • Completely blocking unwanted sites from appearing in search results.
  • Blocking sites by specific URLs using match patterns or regular expressions.
  • Blocking sites by specific titles using regular expressions.
  • Highlighting preferred sites in search results.
  • Support for Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex, in addition to Google Search.
  • Synchronizing rulesets across devices using Google Drive, Dropbox, OneDrive, WebDAV, or browser sync.
  • Subscribing to public rulesets.

Choosing your next step

  • Just want it working now: install from the store for your browser, then add or subscribe to rulesets.
  • Want to test before installing: open the demo from the GitHub project page.
  • Using Safari: install from the App Store build maintained by Group-Leafy, and expect it to be handled separately from the other browsers.
  • Managing multiple devices: after installing, set up synchronization through one of the supported services so your rulesets stay consistent.
How does uBlacklist filter search results?

uBlacklist filters search results by matching each result against rules you provide, then either removing it from the page or marking it visually. You can block a site by its URL (using match patterns or regular expressions), block it by its title (using regular expressions), or highlight sites you prefer. It works on Google Search plus Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex, and is available for Chrome, Firefox, Edge, and Safari.

The three filtering mechanisms

1. Blocking by URL

This is the most common approach. You give uBlacklist a pattern that describes the result's URL, and any matching result is removed from the page.

Two pattern styles are supported:

  • Match patterns — the same syntax browser extensions use for permissions. For example, *://*.example.com/* blocks every page on example.com and its subdomains. This is the right choice when you want to block a whole site without thinking about individual pages.
  • Regular expressions — for finer control. For example, a regex can target a path segment, a query parameter, or a subdomain pattern that match patterns can't express. Use this when you need to block only part of a site.

The practical difference: match patterns are readable and hard to get wrong; regular expressions are powerful but easy to over-match. If a regex is too broad, you'll remove results you actually wanted.

2. Blocking by title

Instead of looking at the URL, uBlacklist can match the result's title text with a regular expression. This is useful when the same unwanted content appears across many domains, or when a site rotates its domain but keeps the same title format. The trade-off is that titles change more often than domains, so title rules tend to need more maintenance.

3. Highlighting preferred sites

Rather than removing results, you can mark sites you trust so they stand out in the results list. This doesn't hide anything — it just makes the results you care about easier to spot. It's the right tool when your goal is prioritization rather than exclusion.

How the rules reach your browser

You have two ways to supply rules:

  • Your own rules — entered directly in the extension.
  • Subscribed public rulesets — maintained by others and pulled in automatically. This is where the "subscribe" in the product description comes from: you subscribe to a ruleset rather than writing every rule yourself.

Rulesets can be synchronized across devices through Google Drive, Dropbox, OneDrive, WebDAV, or browser sync, so the same filtering applies on every machine where you use the extension.

Choosing between blocking and highlighting

Goal Mechanism What happens to the result
Remove a site entirely URL match pattern Disappears from results
Remove specific pages on a site URL regular expression Matching pages disappear
Remove content by title pattern Title regular expression Matching results disappear
Make trusted sites easier to find Highlight Stays visible, visually marked

What to check before relying on it

  • Pattern precision. A match pattern like *://*.example.com/* is broad by design. Confirm the scope before applying it, especially with regular expressions.
  • Search engine coverage. The extension supports the engines listed above; if you use an engine outside that list, filtering won't apply there.
  • Ruleset trust. Subscribed rulesets are maintained by third parties. Review what a ruleset blocks before subscribing, since you're delegating the filtering decisions to it.
  • Sync setup. Cross-device consistency depends on configuring one of the sync backends; without it, rules stay local to the browser where you entered them.

If your need is simply "stop seeing this site in search results," a URL match pattern is enough. If you need to suppress a class of results across domains, title regexes or a subscribed ruleset will save more effort. If you'd rather not hide anything, highlighting is the safer option.

Which search engines and browsers does uBlacklist support?

uBlacklist works on Chrome, Firefox, Edge, and Safari, and it filters results on Google plus Bing, Brave, DuckDuckGo, Ecosia, SearXNG, Startpage.com, Yahoo! JAPAN, and Yandex. If your browser and search engine are in those lists, you can install it from your browser's official add-on store and start blocking or highlighting sites immediately.

Browsers and where to install

Browser Install source
Chrome Chrome Web Store
Firefox Firefox Add-ons
Edge Edge Add-ons
Safari App Store (maintained by Group-Leafy)

Safari is the one platform with a named maintainer rather than the project's own store listing, so treat it as a separate distribution channel when you check for updates or report issues.

Search engines covered

  • Google
  • Bing
  • Brave
  • DuckDuckGo
  • Ecosia
  • SearXNG
  • Startpage.com
  • Yahoo! JAPAN
  • Yandex

Google is the primary target — the extension's core purpose is filtering Google Search results — but the same blocking and highlighting behavior extends to the other engines listed above.

What "support" means in practice

On any supported engine you can:

  • Completely block unwanted sites from appearing in results.
  • Block by URL using match patterns or regular expressions.
  • Block by title using regular expressions.
  • Highlight preferred sites so they stand out in results.

Rules are not locked to one machine. You can synchronize rulesets across devices through Google Drive, Dropbox, OneDrive, WebDAV, or browser sync, and you can subscribe to public rulesets instead of building your own list from scratch.

How to check your setup works

  1. Install the extension from the store matching your browser (see table above).
  2. Open a supported search engine and run a query.
  3. Add a site to your block list, then re-run the query — the blocked domain should disappear from results.
  4. If you use several devices, connect a sync provider and confirm the rule appears on the second device.

If results don't change, the usual causes are: you're searching on an engine outside the supported list, the extension is disabled or lacks permission for that site, or your rule pattern doesn't match the URL format the engine produces.

Choosing based on your setup

  • Chrome, Firefox, or Edge user on Google — the standard case; install from the matching store and you're done.
  • Safari user — supported, but install via the App Store listing maintained by Group-Leafy.
  • Privacy-focused engine user — DuckDuckGo, Startpage.com, Brave, Ecosia, and SearXNG are all covered, so you don't need Google to benefit.
  • Regional search needs — Yahoo! JAPAN and Yandex are supported alongside the Western engines.
  • Multi-device user — pick a sync provider (Google Drive, Dropbox, OneDrive, WebDAV, or browser sync) so one ruleset covers every browser you use.

Website Overview

Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks. An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2013, this domain has about 13 years of history. That suggests continuity, although ownership and purpose may have changed. The registrar, MarkMonitor Inc., specializes in corporate domain and brand management, suggesting attention to domain asset protection. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain uses the common .io extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Amazon Route 53, indicating managed DNS hosting. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The x-cache, x-served-by, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.

Technology Stack Analysis

The public page identifies Hugo 0.167.0, Fastly, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. The Generator tag identifies Hugo 0.167.0, making the publishing system easier to fingerprint. No viewport meta tag was detected, which may affect mobile layout behavior. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 10 characters, within a common display range.

Hosting and Email

DNSAmazon Route 53
HostingFastly
EmailUnknown
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagUnited States Inferred 185.199.108.153

Registration details

RDAP / WHOIS

RegistrarMarkMonitor Inc.
Registered2013-03-08
Expires2027-03-08
Domain statusclientDeleteProhibited https://icann.org/epp#clientDeleteProhibited、clientTransferProhibited https://icann.org/epp#clientTransferProhibited、clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Nameserversdns1.p05.nsone.net、dns2.p05.nsone.net、dns3.p05.nsone.net、ns-1622.awsdns-10.co.uk、ns-692.awsdns-22.net
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aublacklist.github.io185.199.108.1533600—
Aublacklist.github.io185.199.109.1533600—
Aublacklist.github.io185.199.110.1533600—
Aublacklist.github.io185.199.111.1533600—
AAAAublacklist.github.io2606:50c0:8000::1533600—
AAAAublacklist.github.io2606:50c0:8001::1533600—
AAAAublacklist.github.io2606:50c0:8002::1533600—
AAAAublacklist.github.io2606:50c0:8003::1533600—
NSgithub.iodns1.p05.nsone.net639—
NSgithub.iodns2.p05.nsone.net639—
NSgithub.iodns3.p05.nsone.net639—
NSgithub.iodns4.p05.nsone.net639—
NSgithub.ions-1339.awsdns-39.org639—
NSgithub.ions-1622.awsdns-10.co.uk639—
NSgithub.ions-393.awsdns-49.com639—
NSgithub.ions-692.awsdns-22.net639—
TXTgithub.iov=spf1 a -all3600—
CAAgithub.io0 issue "digicert.com"3600—
CAAgithub.io0 issue "letsencrypt.org"3600—
CAAgithub.io0 issue "sectigo.com"3600—
CAAgithub.io0 issuewild "digicert.com"3600—
CAAgithub.io0 issuewild "letsencrypt.org"3600—
CAAgithub.io0 issuewild "sectigo.com"3600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subject*.github.io
IssuerLet's Encrypt
Valid until2026-10-31T23:38 · Remaining when checked: 28 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlmax-age=600
serverGitHub.com
strict-transport-securitymax-age=31556952
access-control-allow-origin*

Identified technologies

Hugo 0.167.0Fastly

Pages, Search and Sharing

User reviews (0)

  • No reviews yet.