reticulum.site

← simple search

Here you can open a Reticulum site without installing Reticulum. This server tries to link you to the site using the 'interfaces' (ways into the mesh) it has. You can add a so-called connection hint below to help it link. A connection hint is the address of a remote Reticulum interface or peer that this server can connect to, which may provide a better path to the site.

Original terminal view · An existing server connection was the verified local interface · nururl:///a14cc4f1220f59a296af11f45c0453f2/page/live.mu · Use web view

Interactive web view

A separate view where pages like this can become interactive, with editable text boxes, page buttons, and automatically updating sections. Seats are limited; this view uses its own session cookie. Text you enter is sent only when an updating section refreshes or you activate a page button.

Open this site in interactive web mode

Reticulum LoRa Scanner - 869.400-869.650 MHz (ct127)                                                
Page views: 354   since 2026-09-29                                                                  
Last 24 hours (static)                                                                              
                                                                                                    
This facility is provided to assist people setting up a Reticulum RNode in the 868 MHz              
ISM band, by giving feedback as to whether their signal is received at this location.               
                                                                                                    
Every Reticulum packet heard in Southern UK over LoRa anywhere in the 869.400-869.650 MHz           
slice (the part of 868 MHz that allows 500 mW), whatever its bandwidth, spreading                   
factor or coding rate. An RTL-SDR feeds a grid of LoRa decoders; the frequency shown                
is the sender's, measured from the signal. Each line is one packet; relayed copies                  
are merged (heard = copies, hops = hop count, 1 = direct). Announce signatures are                  
verified, so names are genuine; everything else is end-to-end encrypted and shows                   
only its type, size and destination. Delivery receipts (proofs) are matched to the                  
packet they confirm and their signature is checked against the recipient's announced                
key; link traffic is labelled with the destination the link was opened to.                          
                                                                                                    
Comments or questions? Send a message: lxmf@9845aed67ab981c008f6c387aa2e97b9                        
                                                                                                    
Auto-refreshes every 10s (NomadNet / MeshChatX). Reload, or static page.                            
See the announced destinations, or the decoder grid.                                                
                                                                                                    
────────────────────────────────────────────────────────────────────────────────────────────────────
⧖

Site address (destination hash) or nururl i Connection hint (interface) or nururl (optional for opening a site)

Accepted connection data: A hostname, IPv4 address, or Yggdrasil IPv6 address uses TCP; an omitted port becomes 4242. I2P accepts a bare 52-character B32 label, …b32.i2p, or i2p://…b32.i2p. Tor accepts a v3 …onion address or tor://…onion, with an optional port. Tor connections use this server’s Tor client and are never sent to DNS. A complete nururl may be pasted into either box. Leave this box blank to use the server’s existing connections.

nururl preview, generated automatically from the data above i

Connections/interfaces supported: public TCP/IP, Yggdrasil, I2P, Tor, and automatically discovered Reticulum interfaces.

Selected sites
Reticulum source code