Reference
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
ip |
string | yes | IPv4 or IPv6 address. |
Example request
curl -s "https://api2.globus.studio/v2/tor?ip=8.8.8.8"
The Tor detector checks an address against the Tor exit-node list. An exit node is the point where traffic leaves the Tor network for the public internet, so it is the address a website sees. A relay that stays inside the network is not an exit node and should not be flagged. A Tor detector answer is about the exit, not about the relay.
What the Tor detector returns
The JSON body has the address, an is_tor flag and a short message. The response is always JSON; the format parameter is ignored for compatibility. An invalid or missing address returns {"error":true,"message":"Invalid or missing IP address"}.
{
"ip": "8.8.8.8",
"is_tor": false,
"message": "The IP address is not using Tor."
}
How the list updates
The data lives in data/tor/exit_nodes.txt and is refreshed by php bin/cron.php tor, recommended every 30 minutes. A node that joined a minute ago may not appear yet. A node that left may still appear until the next refresh. Treat the answer as a recent snapshot.
What a hit means
A hit says the address is on the exit list. It does not say who is behind it or why they use Tor. A journalist, a privacy-conscious customer and a script can share the same network. The flag is a fact about the path, and the policy decides what to do with it.
A proportional response
The Tor detector result can shape a policy: for a login form, a Tor address can trigger a second factor or a manual review. For a public blog, it can be ignored. For an API with a free tier, it can share the rate limit with other anonymous traffic. Blocking every exit node punishes the users who need privacy and does little against a determined attacker.
Combine with other signals
An exit address with a fresh account and a burst of requests is different from one that reads a page. The bot detector and the IP geolocation API add context. The decision should depend on what the request does.
Privacy
Do not publish a list of your users’ Tor addresses. Log the flag, not the whole address, when you can. Keep retention short. The Tor detector describes a network path and should not become a permanent label on an account.
Exit nodes and relays
A Tor relay carries traffic inside the network. An exit node is the point where traffic leaves for the public internet. The Tor detector checks exit nodes because those are the addresses a website sees. A relay address that is not an exit node should not be flagged, and a flag on a relay is a false positive to review.
Testing the policy
Pick a known exit node and a normal address. Run both through the login flow. Confirm that the exit node gets the challenge and the normal address does not. Then test a Tor user with a valid second factor. The flow should allow the login and record the flag.
Review the rule after a month. If the challenge rate is high and the fraud rate is low, the policy is too strict. If the fraud rate is unchanged, the flag is not adding value.
Limits
The check is fast and rate limited. A flag on a Tor address is not a fraud score by itself. The list is a snapshot, so one call cannot prove that an address is clean forever. The Tor exit node guide covers policy examples and a test plan.
Related endpoints
The Tor detector covers the network; for the claimed client, use the bot detector UA. For a country or a city, use the geolocation API. Keep the response shape stable in your client; the message text is for humans and should not drive logic.
Further reading: RFC 1928, SOCKS5.