MoFrp
mofrp.com · Egress and tunnels · 1 record · JSON
MoFrp Egress and tunnels
caveatemailno cardU
| Free tier | MoFrp promises a permanently free basic service; the free tier is a check-in traffic model, where signing in each day grants additional traffic. [translated] unit bytes; metered on unstated |
|---|---|
| Price | USD 0 |
| Per-object cap | not applicable |
| Retention | not applicable |
| Egress | No byte figure is published on the marketing pages: traffic is granted by a daily check-in whose amount the site does not state, and the detail sits behind the console login at console.mofrp.com.; ingress: udp free_allowance: none published |
| Identity | email Not established. console.mofrp.com/login serves a password login and console.mofrp.com/register redirects to the same login page, so no field list was visible. The token 'email' is the shape most likely for a console of this kind and is not a reading; treat the gate as unknown until an account is attempted. |
| Limits |
|
| Binding | none No constraint can be named: the free allowance is not published, so neither the quota nor the shaper can be shown to bind first. A check-in-only model normally lands near a few GB per month, which would fail on volume. |
| Interface | cli, rest Web panel for tunnel config, a Go client with no dependencies, and a documented API at /api/v3/tunnels. |
| Tooling | Go single-binary client on Windows/macOS/Linux/Docker, plus a documented REST API; wg-quick on the local box |
| Composes with | If the check-in allowance is large enough it is the only email-registrable UDP path besides Feige. |
| Reliability | None established; the vendor states tunnels persist as long as the terms are kept. |
| Notes | Chooses no number at all on the public pages, which is itself the finding: the whole commercial surface is the console. Listed as a candidate for a user to test with one throwaway account rather than dismissed. |
| Evidence rung | unverified The protocol stack and the free-service promise are documented, but every number that decides the verdict is behind a login, and the identity field is a shape rather than a reading. One account would settle the quota, the per-tunnel bandwidth, the external UDP port and the gate in one step. |
| Checked | 2026-10-23 (live); stale on 2026-11-06 |
| Parsed numbers |
|
Evidence (1)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | www.mofrp.com/ | free service, protocol stack TCP/UDP/HTTP/HTTPS/Websocket/P2P, check-in traffic model, domestic and overseas nodes |
More fields (7)
{
"wg_path": "inside-udp",
"wg_detail": "The site lists TCP / UDP / HTTP / HTTPS / Websocket / P2P as the protocol stack, so a WG datagram can ride a UDP tunnel. No WG config is issued.",
"ingress": "udp",
"volume_tib_month": null,
"volume_stated": "No byte figure is published on the marketing pages: traffic is granted by a daily check-in whose amount the site does not state, and the detail sits behind the console login at console.mofrp.com.",
"bytes_transit": "yes",
"transit_note": "Vendor relays, domestic and overseas nodes."
}Unknown or withheld values (2)
$.per_object_cap.statednot-applicable$.retention.statednot-applicable