Four tracker lists behind trackerslist.com, and two text files the README never explains

Four plain-text files, rebuilt on a daily commit

Nothing here needs installing. The top level of XIU2/TrackersListCollection is best.txt, all.txt, http.txt and nohttp.txt, each with an _aria2 twin, plus a CNAME, a _navbar.md, an index.html and a .nojekyll that together make the repository the source for the trackerslist.com site. The project updates daily, and the README carries the tally under an Updated heading dated 2026-11-03: best.txt at 70 trackers, all.txt at 126, http.txt at 50 and nohttp.txt at 75.

The four are cuts of the same source data rather than four independent lists. http.txt holds the announce URLs built on HTTP or HTTPS, nohttp.txt holds the rest, including the udp:// form that appears in the project's own aria2 sample line. Those two ought to add up to the whole list. They add to 125, one short of the 126 claimed by all.txt, and the README does not account for the entry that went missing.

A tracker hands out addresses, not pieces of the torrent

Before the lists matter, the mechanism. A tracker, per the README, records user information about who is downloading the same resource so that those users can be connected to each other, and that connection is what lifts BT download speed. The /announce paths in the sample line are where a client registers that interest.

Which makes the list a directory rather than a source. Nothing in the repository ships peers, files or a copy of any torrent. It ships addresses, and what a client does with them depends on the client, the port it listens on and the state of the NAT in front of it.

The README offers a check for that last part. Download ubuntu.torrent from the Ubuntu alternative downloads page. It is a popular resource with many users sharing it, so a healthy configuration should show high download speed. If the speed stays low with best.txt loaded, the list is not the next thing to change.

Six mirrors for the same best.txt

cf.trackerslist.com is the address the README leads with, and behind it sit six alternates for the same file: a Bitbucket raw link, three jsDelivr hostnames, cdn, fastly and gcore, cdn.statically.io, and raw.githubusercontent.com. Trackers get blocked by network operators, and a list served from one hostname becomes useless the moment that hostname stops resolving, so the mirrors are insurance rather than decoration.

The three jsDelivr addresses use the same CDN service under different hostnames, so they are not three independent copies. The jsDelivr paths also omit the branch name while the statically and raw.githubusercontent ones name master explicitly, so the two forms do not resolve the ref the same way. The README ranks none of them, documents no health check and says nothing about what to try when a fetch fails.

aria2.conf takes one comma-separated bt-tracker line

aria2 is the only client with a documented, copy-and-paste path. Fetch best_aria2.txt, or all_aria2.txt, http_aria2.txt or nohttp_aria2.txt, copy the contents, and use it as the value of bt-tracker= in the aria2.conf configuration file. The README shows the shape of the line with one HTTP and one UDP announce URL:

bt-tracker=http://aaa.aa:80/announce,udp://bbb.bb:80/announce

Comma-separated, no spaces. One warning attaches to this step: delete the old tracker content before pasting, or the previous value is still sitting in the file and you get the formatting errors the README names.

BitComet, qBittorrent Enhanced Edition, qBittorrent and Motrix are named as the other supported clients, each with a link out. qBittorrent gets one further note worth reading closely: a collapsed section titled for how versions below qBittorrent v5.0 work.

blacklist.txt and other.txt ship without any explanation

Two of the text files at the top of the repository are not documented at all. blacklist.txt and other.txt sit beside the four lists the README describes, and the README never says what either one contains or which address serves it. No URL in the mirrors section points at them, and no Aria2 variant exists for them.

That gap shows up when a tracker stops answering and you want to know why. A file called blacklist.txt is the obvious place to look for entries that were dropped, yet there is no stated format, no publication rule and no history. Anyone chasing a vanished tracker has to open the file and read it.

The rest of the top level explains the site's shape. _navbar.md and index.html build the trackerslist.com front end, CNAME binds the domain to the GitHub Pages site, .nojekyll turns off Jekyll processing, and img/ holds the figures the README embeds.

Issues are closed, so the list moves without you

The maintenance policy is blunt and worth reading before depending on this. The README states that Issues are closed and that submitted tracker addresses are no longer accepted, on the grounds that the project is small and simple and the author does not want to spend much energy on it. The only route left is a pull request, for an obvious error or to delete a tracker.

So the list moves daily. The repository's last push was on 2026-11-01, the README is dated 2026-11-03, and there are no GitHub releases, no version numbers and no changelog to pin against. Fetching by URL hands you whatever the current commit holds, which is the point for most people and the reason you cannot fall back to a known-good list if today's turns out to be worse.

The contents are assembled from six public sources the README credits: ngosang/trackerslist, newtrackon.com/list, the tracker.txt at github.itzmx.com, tinytorrent.net, torrenttrackerlist.com and DeSireFire/animeTrackerList. How often those are re-read, and what rule removes an entry, is not stated. The licence is GPL-3.0.

How this differs from ngosang/trackerslist and newtrackon

Two of the six sources are projects in their own right, and the difference in approach is easy to state. ngosang/trackerslist is itself a tracker list that this project brings together with the others, so the value added here is the delivery. The text sits behind a CDN, behind six mirrors, next to a website, and beside a rewrite of the same data into the comma-separated form aria2.conf expects. newtrackon.com/list is another of the credited sources, while this list publishes no per-tracker status.

The hand-picking is real but unquantified. The README says the list was put together by searching the web and keeping only the best entries, then gives no criteria: no uptime threshold, no minimum peer count, no rule for a tracker that answers today and is gone next month.

Editorial conclusion

Adopt it if you want a single address to paste into aria2.conf and never revisit the list. Skip it if you need to audit why a tracker disappeared: Issues are closed, submitted addresses are refused, and nothing documents the format of blacklist.txt. Before switching, compare the 70 trackers in the current best.txt with what your client already holds.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. Project website
4. README
5. XIU2/TrackersListCollection on GitHub