Torzon, read the screenA collection of the things you actually see, explained

The collectionAddresses

Addresses

An address that started answering again

You saved an address a year ago, it went dark, and today it loads. That feels like good news and it is the opposite, for a reason that takes one sentence to state and is almost never stated.

What it is
A string that dropped out of circulation and now serves something
Where you meet it
Your own notes, old bookmarks, archived pages, screenshots
What it settles
That somebody is serving on it. Not who
Cannot tell you
That it is the same party as before, because it is not

The specimen

saved 2025-11-04 v7q...ryd.onion opened fine for months
spring 2026 v7q...ryd.onion stopped answering, dropped off every list
today v7q...ryd.onion login page, looks exactly right

The pattern, written out. Addresses are abbreviated on purpose. The third line is the one people read as a comeback, and it is the only line in the sequence that should make you close the tab.

Why a revival is not a revival

To serve on an exact onion address you need the private key it was derived from. Not a similar key. That one. So there are only two ways the third line happens, and neither of them is the market coming back to an address it retired.

Either the key leaked, which means the address is in the hands of whoever has it now, or what you are looking at is not the same string and you did not read far enough to notice. In practice the second is far more common, which brings this straight back to the near miss.

What the old string is worth to somebody else

Think about what a two year old address carries that a fresh one does not. It sits in archived pages, in old forum threads, in unmaintained lists, in bookmarks and screenshots and other people notes. Anybody answering on something that resembles it inherits all of that for free, and the traffic arriving is filtered down to people who trust the string because they remember it.

Why this one catches the experienced

Every other specimen in this collection gets filtered by experience. This one runs the other way. The reader most likely to be holding a long dead address is the one who has been at this for years, feels sure about it, and is least likely to stop and compare a string they recognise.

Newer readers paste from a current list every single time, because they have nothing memorised to fall back on. It is one of the few places in this subject where knowing less protects you more.

What to do with it

  1. Do not log in and check afterwards. That order hands over the exact thing the check was for.
  2. Compare it against a current published set, pasted rather than read.
  3. If it is not in the set, it is not in use. Not maybe, not an old mirror still quietly running.
  4. Delete it from wherever you keep addresses, so this question does not come up again next year.