| Node | IP | Location | Type | Uptime | Used for | Status | Connect |
|---|
Click a node for its full detail — reputation source & freshness, geolocation, health, line facts and eligibility. Used for is your own bookkeeping: the sites you have run through each node, saved per node and shared by every device and key of that household. Editing it needs the write key; the read token only views. Connect mints a client config and revokes that household’s previous one.
Pagekind's aggregate counts, shown as reported: each card is one count over its own window, start included and end excluded, and nothing here adds them together, compares them or turns them into anything else. No data means the count was not measured, which is not a count of zero. Hover a card for what it does and does not count.
Connect on a household row is the normal way in — it works out which client is pinned to that household and mints for it. The box below is only needed when a household has SEVERAL clients pinned to it, where nothing can tell which one you meant. Either way, minting revokes that client's previous config: a WireGuard key admits one session, so whoever is using the old one is cut off at once.
Scan with the WireGuard app. The QR carries a shortened config: a QR code holds 2,953 bytes and the full one is about 4,400, so every warning above is omitted from it.