Free FRP
freefrp.net · Egress and tunnels · 1 record · JSON
Free FRP (freefrp.net) Egress and tunnels
caveatanonymousno cardDrequest-rate
| Free tier | Connection port: 7000; password: freefrp.net; open ports: 80 / 443, 10001 to 50000; current version: 0.56.0. [translated] unit unlimited; metered on none |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No quota is published anywhere on the site.; ingress: udp free_allowance: none published |
| Identity | anonymous No account: a shared server password is printed on the home page. |
| Limits | |
| Binding | request-rate No byte quota and no rate cap are published, so no volume constraint exists in the vocabulary. The one published limit is a unique remote port inside a shared 10001-50000 range, recorded here as request-rate. That is not what breaks at 1 TiB/month; the true failure mode is a volunteer server with no operator obligation, which the vocabulary has no kind for. |
| Interface | cli Standard frpc against a published server and password. |
| Tooling | any frpc |
| Composes with | A zero-identity UDP entry point, same role as freefrp.com with a narrower port range. |
| Reliability | No ban policy and no SLA are published; nothing governs whether the server stays up. |
| Notes | Anonymous and quota-free, but with no operator identity and no stated limit the risk is the service vanishing rather than a metered cut-off. A 1 TiB/month run on a volunteer server is the least likely thing it survives. |
| Evidence rung | documented The endpoint and port range are on the vendor page today; the UDP statement is from the docs page read today. Only a probe shows whether UDP is served. |
| Checked | 2026-10-23 (live); stale on 2026-11-22 |
| Parsed numbers |
|
Evidence (2)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | freefrp.net/ | shared server on port 7000, open ports 10001-50000 |
| 2026-10-23 | freefrp.net/docs | TCP and UDP proxy types are documented for this server |
More fields (7)
{
"wg_path": "inside-udp",
"wg_detail": "The docs page documents TCP and UDP proxy types against this server; a WG datagram can be proxied on a port from 10001 to 50000.",
"ingress": "udp",
"volume_tib_month": null,
"volume_stated": "No quota is published anywhere on the site.",
"bytes_transit": "yes",
"transit_note": "One volunteer server carries the datagrams."
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable