Maybe then you can categorize them, each group into specific title.
2 Likes
Weak opinion: I would guess that most users are only/mostly interested in hosting providers that fulfill as much as possible of your criteria. Only crypto support is not very interesting and might even be a distraction. Unless, you like to list them for the purpose of others not loosing time with providers that support crypto but fail at other criteria. The first post can probably just be an introduction text and link to our mediawiki.
In any case, as you prefer.
1 Like
This plan requires more time due to redundant entries across multiple countries on the Tor Project’s Good Bad ISPs page, which means it requires overhauling its primary sorting method to individual web hosting providers instead, among other column changes. Here is an example entry with my planned contributions (subject to further revisions):
| Company/ISP | ASN | Location(s) | Bandwidth | DDoS Protection | IPv6 | ToS/AUP | Bridges | Guard/Middle | Exit | Payment Method(s) | KYC/AML | Comments | Last Updated | Consensus Weight |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hetzner | AS24940 | Germany, Finland, Singapore, US | 1 Gbps unmetered on dedicated servers | Yes | Yes (/64) | ToC | Yes | Yes | No | Credit card, SEPA, bank/wire transfer, PayPal, and UnionPay | Yes (passport) | 05/2025 | 11.68% |
Current workload suggests this task will be completed in two months, so I will link a merge request from the Tor Project’s GitLab repository for the next monthly update.
IncogNET is no longer blocking the Tor Browser from accessing its website, so it has been added to the wiki. Cockbox and Ukrainian Data Network remain unverified due to lack of servers and/or “contact-walls”, but otherwise all entries from this topic and KYCNOT.ME have been thoroughly verified. Any web hosting providers with cryptocurrency payment support failing to meet the criteria established on the wiki have been (re)added to this topic’s wiki post instead.
I have decided to abandon the plan to completely revise the Tor Project’s Good Bad ISPs page, instead simply fetching any eligible entries from there to the Whonix Wiki for a lighter workload. Additionally, I will be editing this post throughout the month as I continue to filter each entry.
Flawed
A1[1]
Alwyzon[2]
Bthoster[2:1]
Creanova[2:2]
Digicube/Nexylan[3]
Gandi[4]
Gcore[5]
Infomaniak[2:3]
M247[3:1]
MAXKO Hosting[4:1]
OneProvider[2:4]
OVHcloud[2:5]
RackNation[2:6]
Scaleway[2:7]
Servarica[2:8]
TekSavvy[6][1:1]
T-Mobile[1:2]
Videotron[1:3]
VTR[6:1]
KYCNot.me has updated their database to include unverified community-contributed entries, but I plan on reviewing them next month. Ukrainian Data Network is currently inaccessible at the moment.
I am tackling KYCNOT.me’s hosting and VPS entries against our strict criteria on the Whonix Wiki, starting with their verified and approved services. SporeStack, one of the listed VPS services, references this website on their pricing page under the “Where else can you host for Bitcoin or Monero?” header:
This new resource along with the Tor Project’s Good Bad ISPs and KYCNOT.me’s entries will eventually be aggregated and crawled monthly, so here is a tenative roadmap to lead to that state:
- Filtering through every community contributed hosting and VPS service on
KYCNOT.me, ignoring previously crawled entries. - Filtering through the list of entries on
bitcoin-vps.com, ignoring previously crawled entries. - Filtering through the list of entries on the Tor Project’s Good Bad ISPs page, ignoring previously crawled entries.
- Aggregate and crawl all aforementioned third-party sources’ new entries every month, ignoring previously crawled entries.
The reasoning behind ignoring previously crawled entries is mostly based on efficiency, just like DNS caching, but I also have an assumption that any service provider caving in to external KYC/AML pressure is unlikely to change their privacy and/or anonymity posture to solely benefit their customer base in the future. To facilitate the last step of the roadmap, I will be utilizing the Wayback Machine to create a monthly snapshot of the bitcoin-vps.com website, since the other third-party sources have a changelog implemented for their entries in some form or another.
1 Like
Seems to be going really well so far! 
One small thing for the future. (Nothing went wrong yet but I should have mentioned this earlier perhaps.)
- Anonymous edit: diff
- Hosting Location Hidden Services - Wiki History
Could you please have a look at the wiki history to make sure no unknown edits slip through?
No rush at all. This can be done as per your usual schedule. As long as the edit isn’t confirmed, it’s non-public. (Only visible after login with a free account through diff or history.)
I am only mentioning this to avoid anonymous edits getting live without review.
2 Likes
Yes, I re-edited over the anonymous commit by correcting LNVPS’ requirements to include an SSH key. The checkout process uses its own API to generate a QR code for either the Bitcoin or Lightning invoice (alongside the wallet address), so there is no third-party payment gateway dependency whatsoever.
2 Likes
This stub task is now complete pending acceptance of the PrivateAlps wiki edit submission. I have also confirmed that HammerVM (https://hammervm.com/) and Strike (https://strike.bz/) request finer locale information other than country (address, city and postal code), so I have dismissed them based on this unnecessary personal information harvesting practice. If there is any issue about this decision, then such reconsideration demands that each of them will have three additional requirement entries due to the locale information mentioned earlier, along with previously crawled hosting providers being recrawled again.
The Wayback Machine is not successfully saving any snapshots of the website (regardless of reporting the issue upstream), so I manually save it (Ctrl + S) whenever I update the Whonix Wiki instead. The last update on the bitcoin-vps.com website as of this writing was March 9th.
1 Like