Skip to the content.

Route 2: DNS filtering

What it is: the TV asks a DNS resolver for the address of every domain it wants to reach. A filtering resolver answers “does not exist” for ad and telemetry domains. The TV itself is not modified at all. Revert by removing the filter.

What it is not: a TV setting. It is network administration, and depending on how you set it up it can affect every device on the network. Do not start this on a shared network without the agreement of everyone affected.

Setup options

Point only the TV at the filter when possible (manual DNS on the TV, or per-client rules in AdGuard Home / Pi-hole), so nothing else in the house is affected.

The blocklist

Subscribe, do not copy:

https://raw.githubusercontent.com/ipanalytics/Hisense-VIDAA-DNS-Clean-TV-Blocklist/main/Blocked_Domains_AdGuard.txt

AdGuard Home: Filters → DNS blocklists → Add blocklist → Add a custom list, paste the URL, save, then Update filters.

Pi-hole: Lists (v6; Group Management → Adlists on v5) → paste the same URL in the address field, save, then update gravity (Tools → Update Gravity or pihole -g). Pi-hole parses the AdGuard syntax of that list directly; use Blocked_Domains.txt from the same repo if your filter wants plain hostnames.

Limit the filter to the TV only

AdGuard Home: Client settings → add the TV (by IP or MAC), and under Filters choose only the VIDAA list for that client.

Pi-hole: Group Management (v5; Clients/Groups on v6) → create a group (for example tv), add the TV as a client by IP or MAC, then assign the VIDAA list to that group only. Every other device keeps your previous setup unchanged, and removing the TV from the group reverts it instantly.

The author’s observations come from Hisense VIDAA sets in Europe/Germany; individual rule comments distinguish observed hosts from inferred candidates. The author reports YouTube and Netflix working, not every app or every model. Effects on Toshiba remain untested here (see TESTING.md).

Upstream snapshot: 11 November 2026

IPanalytics’ update 045c377 adds 13 active rules and two documented-but-disabled options: 150 active, 45 disabled, 195 total at that commit, checked 14 November. These are upstream counts, not a hardware-verification result or a fixed promise about future subscriptions. Refreshing the subscription brings future changes too.

The new active rules cover advertising/monetization reporting and resources, regional monetization backends, an advertising-portal CDN, Hisense/Xumo beacons and telemetry/tracking hosts. These additions overlap the reporting and monetization coverage that our 9 November community comparison described as missing. Do not add a second list just to fill that old gap.

The same update explicitly documents the Prime Video trade-off: six recommendation API/UI rules remain active because upstream prioritizes the clean home screen, but owners reported missing Prime Video thumbnails and parts of its UI. That setup does not use Prime Video. See the six named hosts and smallest-change recovery procedure in TROUBLESHOOTING.md. The upstream author credits the Owen3H fork that disables those rules; this is a reported workaround, not a test here.

Two additional options stay disabled upstream: recommend-ui.vidaahub.com can affect launcher tiles and artwork; api-4know-eu.hismarttv.com can affect search suggestions and voice answers. They are not default blocks, and this project does not recommend enabling them without observations on your set. No rules are copied into our supplement and no TV results are added by this documentation update.

Other community lists

The upstream list above is the one this project documents and tests against. Others exist; know their trade-offs before mixing:

The supplement

blocklists/toshiba-uv1553db-supplement.txt holds domains observed on our Toshiba that the upstream list misses. It starts empty on purpose: rules are added only from real DNS observations on the device, never guessed.

Before you subscribe the TV to any list of your own, check the file offline:

python3 scripts/validate_blocklist.py your-list.txt

It rejects malformed rules (including scoped Adblock options like $client=, which this project does not interpret), duplicates and rules shadowed by a parent-domain rule, and --upstream checks your list adds nothing the upstream list already covers. This validates syntax only; whether the rules block the right domains comes from observing your own TV, never from the validator.

Honest warnings

From the upstream author and justatv.eu: