WTN Claim Register What people say about We The North, checked one claim at a time
Register › Reference

We The North addresses

Three published addresses for the same platform. Copy rather than retype, and verify the signature once you are through.

Address 1 hn2paw7zadwkcra3qzv5e4q547i7e5lvxm62cfxqftuqdu7moiu2ceyd.onion
Address 2 hn2paw7zfvndw3dovycegeqmvvnf4pl67b3g2p7pohjlzavloosh73id.onion
Address 3 hn2paw7zrgujyhnt6mgxlt2q6uhgbke4itpqitxhyfbumq3wtnckbuyd.onion

This site publishes the list and does not monitor it. An address that opens is not an address that is genuine, and the check that settles it takes under a minute.

Addresses

The three addresses at the top of every page are a published list. This page is about what that does and does not mean.

What a published list is

A statement about which addresses are in use. That is genuinely useful and it is not a security claim. This site does not probe them, does not monitor them, and publishes no uptime figure, because a number it cannot back would be worse than none at all.

The separationReachability and authenticity are different questions. A prober can answer the first and nothing automated can answer the second, which is why the check happens at the other end.

Why several rather than one

Almost everything that makes an onion unreachable happens in the path rather than at the destination. A descriptor that failed to publish, an introduction point dropping out of consensus, a bad relay in the middle of your circuit, flooding aimed at one address. Every item there is per address, and the service behind them is fine throughout. Several addresses make those failures independent of each other, which is the whole argument.

They are not fully interchangeable in every respect. An older address has been in circulation longer, appears in more scraped lists, and attracts more junk traffic. A newer one is quieter and often noticeably faster, and appears in fewer places, so somebody who only ever saw the old one may be suspicious of it.

Keeping your own copy

WhereVerdict
Password manager entryGood. Under your control, easy to date and edit.
A text file you ownGood, and you can note where each came from.
PaperGood. Cannot be edited by anything running on your machine.
Browser bookmarkPoor. Often synced, easy to click without thinking, and it hides the string behind a name you chose.
MemoryBad. Nobody recalls fifty six characters, and near enough is the failure being exploited.

The habit that matters

  1. Copy, never retype. Every manual transcription is a chance to introduce an error that will look like an attack when it fails.
  2. Note the source and the date beside each one. A single line, and it is the difference between judging something later and guessing.
  3. Compare against a published list every few weeks. Under a minute, and it is the entire maintenance burden.
  4. Delete rather than archive when something drops off. This is the half that actually protects you.
  5. Verify on arrival regardless of how familiar the string looks.

If you are going to spot check a string rather than paste and compare, check characters twenty through forty. That is where a forgery differs, and it takes exactly as long as checking the ends.