about

The trailing dot is a DNS convention. Appended to a fully-qualified domain name, it tells the resolver the name is complete – stop here, look no further. It appears in zone files and in the output of dig and almost nowhere else. Most software strips it silently. It is precise, invisible, and almost entirely beside the point unless you are the kind of person for whom it is entirely the point.

This is a publication for that kind of person.

Twenty-three issues across two volumes and fifteen years: conference talks on threat intelligence and incident response; technical essays on distributed systems, mesh networking, post-quantum cryptography, and peer-to-peer file transfer; a control channel hidden inside a video container; fiction about people who build things in the dark. Vol 1 ran from 2010 to 2018. Vol 2 resumed in 2022 and continues.

The range is intentional. A risk assessment framework presented at a government IT symposium in 2011 belongs in the same catalog as a post-quantum file transfer tool published last week. Both are about the same underlying problem: understanding systems well enough to make them do what you intend.

The trailing dot is not a typo.

The proprietor of this establishment has been working in security and infrastructure since before most modern cloud providers were incorporated. The work spans incident response, threat hunting, network architecture, and the quieter discipline of building things that are not supposed to be noticed – mesh overlays, cryptographic gating layers, peer-to-peer transports, the kind of infrastructure that operates correctly by being unremarkable.

The Trailing Dot is where that work surfaces when it can be written down, made precise, and published without caveats about who owns the room. Two volumes. Twenty-three issues. No editorial calendar. No sponsored content. No comment section.

Some issues are talks – delivered at chapter meetings, symposia, and SANS community nights over the better part of a decade. Some are technical essays written because the work demanded documentation. A few are fiction. The Stonebreaker and Hudson stories are set in a near-future that is uncomfortably close to the present one. They are also, in their way, about infrastructure.

The proprietor is based in Minneapolis. The domain resolves. The zone file is in order. The trailing dot is present and accounted for.