Across The Veil is an independent research and discussion forum founded in 2003. The original intent was simple: a place for people who were serious about the work. Not serious like humorless — serious like actually doing the reading, checking the sources, and not just reposting whatever shows up on a message board at 2 AM.

Over eleven years we covered a wide range of subjects: signal anomalies, unexplained aerial phenomena, institutional secrecy, cryptographic puzzles, and fringe signal research. At our peak we had a few hundred active users, a handful of whom were genuinely exceptional investigators.

The forum is now read-only. It's a record. Use it accordingly.

VeilKeeper. I founded this forum and administered it until I shut it down. That's all I'm putting in writing. If you've been here long enough, you know roughly what I do and why I'm careful about it. If you're new, that's fine — just know that the anonymity policy wasn't paranoia. It was professional hygiene.

I don't have a contact email anymore. The contact page is preserved but I don't expect to respond.

The honest version: we got too close to something, and I'm not sure what it was. I don't mean that dramatically. I mean that in the weeks before I made the decision, certain threads produced results that I wasn't prepared to have on a publicly writable forum anymore.

The Obscura thread in particular. Some of you know what I mean.

Keeping it writable felt like leaving a door open that I didn't have the right to leave open. So I closed it. The record stays. The door doesn't.

Yes. Everything that was public before March 14, 2014 remains accessible. Some threads are locked due to ongoing sensitivity concerns or because the original poster requested removal. A number of threads are restricted at my discretion. That list won't be published.

If you're looking for a specific thread and can't find it, it may have been in a restricted subforum, or it may have been removed. I won't confirm or deny specific removals.

Source your claims. Screenshot it, archive it, link it — if you can't point to the thing, you're speculating. Say so explicitly.

No personal information. Not yours, not anyone else's. Full stop.

Extraordinary claims require proportional evidence. Enthusiasm is not evidence.

Deliberate disinfo campaigns were grounds for an immediate permanent ban. We had two in eleven years. Both were handled.

No monetization. Nobody sells anything here. Nobody recruits. This is a research forum, not a platform.

Those rules were enforced consistently. I'm proud of that, for whatever it's worth now.

I don't know for certain, and anyone who claims certainty is either lying or wasn't paying attention.

I had suspicions about a small number of accounts over the years. Accounts that were technically within the rules but seemed oriented toward resolution rather than investigation — toward closing threads down rather than following where they led. Whether that was personality, institutional affiliation, or something else, I genuinely cannot tell you.

If you're going through old threads and something feels off about a particular user's posting pattern, trust that instinct and do your own analysis.

Read the Cicada 3301 thread first. Not because Cicada is the most important thing we covered, but because it's a clean example of how good collaborative research works: multiple people with different skill sets, documented steps, no attribution wars, and a genuine willingness to be wrong in public.

After that: develop a working knowledge of basic cryptographic methods. The Cipher Toolkit has functional tools for Base64, ROT13, Vigenère, Morse, Caesar, and Atbash.

Learn to archive. Things disappear. If you find something, preserve it before you share it, because by the time others come looking, the original may be gone. That's not always sinister. Sometimes it's just link rot. Preserve anyway.

Repeatability. Can it be reproduced? If a signal appears once and never again, that's data, but it's thin. If it recurs with any consistency — time, frequency, pattern — it's worth pursuing.

Exclusion. Have you eliminated the mundane explanations first? Atmospheric interference, equipment malfunction, human error, hoax. You don't get to skip this step because it's tedious. It's the most important step.

Cross-reference. Does it appear in any adjacent documentation? Dispatch archives, FOIA releases, local incident reports, amateur radio logs. Anomalies rarely exist in isolation. If something is real, it usually leaves multiple shadows.

If something passes all three: document carefully, share responsibly, and brace yourself for the people who will tell you it's nothing.

That thread is partially restricted. The portions that remain accessible are visible in the main index. Twenty-three posts. Four hundred and forty-one views. The thread closed March 11, 2014 — three days before I went read-only.

I'm not going to summarize what's in it here. Read what's available. Pay attention to who kills the momentum and when. Pay attention to the one user who almost names the thing and then goes quiet.

The word that almost got said: O B S C U R A. If you've read the thread, you already know it. If you haven't, go read the thread.

If you want to know why I went read-only when I did, that thread is most of the answer.

This forum is read-only. I can't speak to what others are doing now. What I can tell you is that several threads were left unresolved at close — not because the community gave up, but because the evidence ran out or the trail went cold in ways that felt deliberate rather than accidental.

The Hanson case subforum is fully locked. I won't be opening it.

The audio file coordinates thread is restricted. The geographic data in it is real.

There were a number of wire service dispatches — from a small independent outlet called Meridian Press — that came up across several threads. Their 1994 coverage of an incident in Washington state was referenced at least twice. Their archive is not publicly searchable in any meaningful way, but their dispatches are out there if you know how to look. A few of us got close to cross-referencing their signal anomaly coverage with our own documented cases. We never finished that work. I leave that for whoever finds this and decides it's worth picking up.

The Cipher Toolkit has browser-based tools for Base64, ROT13, Caesar shift, Atbash, Vigenère, and Morse code. Everything runs locally — nothing is sent anywhere.

The cipher megathread on the forum index is the written reference. Read it before you start. The toolkit is the tool. The megathread is the method.

A combination of reasons. Some external links are simply dead — eleven years of link rot. Some were removed at source. Some were pages that were only accessible for a limited window.

A small number of internal links point to restricted content. Those will return a notice rather than a 404, which is at least more honest.

Archive.org is your friend, though not everything was captured before it went down.

I don't know how to answer that responsibly.

Nobody was physically harmed in connection with this forum's activity in eleven years. I can tell you that two or three people went very quiet in ways that made me uncomfortable, and that I've thought about that regularly since. I can tell you that the decision to go read-only was not made casually or out of boredom.

What I can't tell you is what's on the other side of the Obscura thread. I looked. I got partway in. I made a decision about how much further I wanted to go.

That decision is yours to make. I just ask that you make it deliberately, not because you stumbled into it without knowing what you were walking toward.

Whatever you find: document it. Leave a record. That's all any of us can do.

No.

But I'll keep the lights on for as long as I can. The work deserves a place to exist.

— VK