Talk:BTDigg

Availability

The BTDigg site appears to be down for some time now, with Cloudflare DNS not even returning a record for it anymore. Does anyone have any updated info about this, and, if so, would they care to make this article current? — Preceding unsigned comment added by 62.169.106.213 (talk) 09:35, 17 September 2023 (UTC)

I'm curious, too. It doesn't seem "down" but the official domain shows the Nginx default (after fresh install) page.

Oxiq (talk) 11:19, 25 September 2024 (UTC)

Seized by the FBI HairyAreolas (talk) 08:05, 14 September 2025 (UTC)

btdig.com is not the same as btdigg.org

Note: I am not the IP editor whose edit was just reverted. I have refrained from editing the article, and instead am opening a discussion here. I am not the owner of either website, though I have some involvement in a dispute involving btdig.com's owner.

btdig.com isn't owned by the same person as btdigg.org, and no reliable source states they are owned by the same person. btdig.com copied its layout and code from btdigg.org, and thus erroneously refers to itself *as* btdigg.org. btdig.com links to the social media accounts for btdigg.org, but those accounts don't mention btdig.com and have been inactive since 2015. btdig.com isn't a phishing website or otherwise malicious, to be clear, just a separate project.

I spoke to the owner, who confirmed they were not the owner of btdigg.org & said btdig.com is a clone of btdigg.org. Problem is that I'm not a WP:RS and I can't prove those emails are real, hence why I haven't corrected the article myself. I'm also not sure how to handle a site self-identifying incorrectly when no reliable source contradicts it. Iam-py-test (talk) 20:44, 27 April 2026 (UTC)

@Sapphaline In regard to this edit, Nina Evseenko isn't a pseudonym as far as I can tell. This article identifies her as the owner, though it's an WP:SPS so probably it can't be cited here. She has a real presence online and specifically in regard to torrents, though that's clearly original research. In solidarity Iam-py-test (talk) 00:41, 16 June 2026 (UTC)

Well, there are thousands of Nina Evseenkos out there; I wouldn't be surprised if all these matches were simply coincidences. The person running archive.today also has many monikers, some of which are appropriated identities. sapphaline (talk) 10:38, 16 June 2026 (UTC)

And I have some evidence that the person who ran btdigg.org is the same person who currently runs archive.today and btdig.com, or they're at least close to each other; adding this to the article would be original research, though. sapphaline (talk) 10:56, 16 June 2026 (UTC)

I'm curious, what evidence do you have that btdigg.org was run by archive.today? In solidarity Iam-py-test (talk, she/her) 11:22, 16 June 2026 (UTC)

1. The russian version of the article, ru:BTDigg, was nominated for deletion review in March 2012. On that page we have a log of Nina Evseenko chatting in Skype with a then admin Petrov Victor, and her writing style (all-lowercase, calling Wikipedia by its English name instead of Russian "Википедия") is similar to the writing style of an IP editor who participated in a discussion about deprecating archive.today on ruwiki, and who I strongly suspect was an archive.today sysadmin. Frequent use of ASCII emoticons is also noteworthy, because the same tendency can be observed in Tumblr blog posts from archive-is account.
2. btdigg.org's main page was, for some time in June 2021, clearly GPT-3-generated nonsense about real estate. This was around the same time a fake Blogspot account was created for the "Nora" identity, with the only post from it also being GPT-3-generated nonsense, and I don't think this was some spammer buying the btdigg.org domain, because there are no snapshots of the usual domain-for-sale landing pages from this domain before October 2022. sapphaline (talk) 13:14, 16 June 2026 (UTC)

   Interesting, I was not aware of that. Thanks. I'll have to update my article. In solidarity Iam-py-test (talk, she/her) 15:13, 16 June 2026 (UTC)

   (LTA's comment removed) ~2026-36087-38 (talk) 17:06, 20 June 2026 (UTC)

   Who are you referring to? sapphaline? Me? I'm assuming you are referring to sapphaline based on your other edit In solidarity Iam-py-test (talk, she/her) 19:55, 20 June 2026 (UTC)

   ANI complaint filed. In solidarity Iam-py-test (talk, she/her) 20:15, 20 June 2026 (UTC)

   This person isn't related to archive.today or BTDigg by the way. sapphaline (talk) 06:35, 21 June 2026 (UTC)

References

Ownership / provenance

I'll add to what the previous Talk post here says. This article in its current form is written by someone either under the impression or deliberately trying to create the impression that the current btdig.com (and its onion version) are a "continuation" of the original btdigg.org which went offline ten years ago. There are no sources cited to justify that these two sites are related, and in fact the operator of the current btdig.com has admitted to people that they are not the same person as originated btdigg.org.

Beyond the problem of this article essentially falsifying or at best eliding provenance, it links to the current onion site. This site is insecure, requires Javascript be enabled for reCaptcha and then attempts to load various other scripts, and in short has all the hallmarks of being a honeypot. This article should probably be extensively reworked or removed. ~2026-32008-65 (talk) 02:26, 30 May 2026 (UTC)

special:diff/1364087436

@RiedleroD: what "badware distributor" are you referring to? sapphaline (talk) 23:27, 14 July 2026 (UTC)

I guess that's related to . Commented out the link until we can get noreferrer on it. sapphaline (talk) 23:30, 14 July 2026 (UTC)

last time I opened it, uBlockO blocked it because it redirected to a website in the "badware risk" filters. But it looks like it got changed to just advertising (maybe? it's unmarked inside the generic easylist filter) since then. I didn't take a closer look than that.

as for "works for me" - because of DNS caching, this unfortunately doesn't work like that. wait a week and check again; by then the cache should've cleared. on my end, I get 3 different answers from the 3 reputable DNS servers I use (1⁴, quad9, google DNS) so whatever this is is certainly still ongoing.

I'm speculating that the btdig.com owner sold the domain to a bad actor, which in turn is renting it out to the highest bidders. RiedleroD (talk) 23:37, 14 July 2026 (UTC)

Can you disable uBlock and open the page? What's on it? "I get 3 different answers from the 3 reputable DNS servers I use" - BTDigg uses fast flux. sapphaline (talk) 23:38, 14 July 2026 (UTC)

And can you do the same, but open it directly from the article? sapphaline (talk) 23:43, 14 July 2026 (UTC)

I can reproduce it: https://video.infosec.exchange/w/i6qG7TDif2HycNYwbqGyxz

It has nothing to do with referer, and I can reproduce across multiple IPs. In solidarity Iam-py-test (talk, she/her) 19:00, 16 July 2026 (UTC)

However, oddly, Meglodon is able to access the site fine: https://megalodon.jp/2026-0717-0423-45/https://btdig.com:443/

Maybe caching? In solidarity Iam-py-test (talk, she/her) 19:26, 16 July 2026 (UTC)

Indeed, and definitely not IP-based as I'm getting the same redirect with a Russian proxy. sapphaline (talk) 23:14, 16 July 2026 (UTC)

Wait, no, that was a Swiss proxy; accessing the website from a Russian one doesn't result in a redirect. sapphaline (talk) 23:19, 16 July 2026 (UTC)

See also this issue on their Github repository. sapphaline (talk) 23:22, 16 July 2026 (UTC)

Since .onion is offline, I commented out both links until either .onion is live again or redirect is removed from the clear web version per Wikipedia:External links#Official links ("If an official site is serving malware, its URL should be hidden until the website is cleaned up"). sapphaline (talk) 23:40, 16 July 2026 (UTC)