Node HandbookNODE HANDBOOK中文
Free nodes · risk

Free proxy nodes: the risk is not the price

A free configuration can be legitimate and still be the wrong thing to put your main accounts through. What matters is who produced it, what it changes on your device, and what you use it for.

Node Handbook editorial team ·

“Free” answers one question only

It answers what you paid. It does not answer who generated the configuration, what it does on your device, whether the exit is operated by anyone accountable, or whether the service you are reaching will treat that exit as hostile.

The practical frame is not “is this safe” but “what is the worst outcome I am accepting, and does this task justify it”.

Four questions about the source

  1. Who publishes it, and do they have a name to lose? A repository with history, issues and a maintainer is different from a channel that posts fresh links hourly.
  2. What does the page claim, and is it checkable? “Unlimited, all regions, no logs” is a marketing sentence. Look for what can be verified: file hashes, update times, test records with conditions.
  3. Does it ask for anything disproportionate? A root certificate, a system extension, an administrator script, or a login to an unrelated service are all out of proportion to “try these nodes”.
  4. What is the incentive? Someone is paying for the servers. Understanding who, and how, is part of reading the offer.

What a configuration can change on your device

ComponentWhat it can doWhy it matters
Proxies and groupsDefine where traffic goesThe visible part; least surprising
RulesDecide what is proxied and what is directA rule can send traffic you expected to protect straight out
DNS settingsChange which resolver answers, and through which pathAffects both privacy and whether names resolve at all
Scripts and overridesRewrite the configuration at load timeBehaviour may not match the file you inspected
Certificate trustLet a party sign certificates your device acceptsChanges the security model, not just the route

Importing is a decision about all five rows, not just the node list.

A five-minute check before importing

  • Open the file in a text editor and look at the top-level keys: proxies, proxy-groups, rules, dns, script or override blocks.
  • Search the rules for DIRECT on domains you expect to be proxied, and for broad match-all rules near the top.
  • Check whether it references external resources — rule sets, providers, scripts — hosted somewhere unfamiliar.
  • Confirm the format matches your client; a mismatched format is a functionality problem, not a security one, but it hides both.
  • If the source ships a QR code or a one-click link instead of a file, you lose the ability to inspect it before import.

HTTPS protects content, not identity

HTTPS protects the content in transit between your device and the site. The exit still sees which domains you contacted and when. It also sees traffic patterns, and a client-side component — if you installed one — is not constrained by HTTPS at all.

That is why the useful rule is by task, not by “is it encrypted”: general reading on a free node is a different risk from account access, payments, work systems or anything that identifies you.

Where free nodes are a reasonable choice

  • Testing whether a client configuration imports and starts.
  • Reading public documentation or news where the account is not logged in.
  • Checking whether a region-restricted page responds at all, before deciding to pay for a service.

Every one of those can be interrupted at any moment without consequence. That is the property that makes them suitable.

Monitoring and cleanup

  • Watch for unexpected redirects, certificate warnings, login prompts you did not trigger, or a sudden change in which sites load.
  • When you stop using a profile, remove it, turn off the system proxy and TUN, quit the client, and confirm plain networking returns.
  • If the profile ever included a certificate or extension, remove that too — a profile deletion does not always take trust settings with it.

Scope

This page does not assert that any particular free source is malicious, and it does not audit any provider. It describes the questions worth asking and the parts of a configuration worth reading, so that “it connects” is not mistaken for “it is acceptable for this task”.