Security
This page says how the page you are reading is protected, and where to write if you have found a hole. The guide asks you for no name, no password and no money; the whole question of security here is one thing — that the page reaches you as we sent it.
The site has no unencrypted connection: a request over http is turned into https by the browser itself, and it has been told so a year ahead. Whoever reads your network — the café owner, your provider, the stranger on station Wi-Fi — sees that you opened enfilade.guide and does not see which page.
Fonts, photographs, the map and both of its libraries sit on our server. There is not a line of foreign code on the page, and it makes no outside requests. A tampered counter or a compromised font from someone else’s server is the usual way foreign code reaches a site; that way is not open here.
Along with the page the browser receives a set of rules: take everything from our server only, run no code whose fingerprint is not in the set, send what you type nowhere outside, do not open our page inside someone else’s. Everything is forbidden except what is named. If a foreign line ever reaches our markup, the browser will not run it.
The guide asks for no name, no password and no payment, sets no cookie and writes nothing into the browser’s memory. There is nothing here to steal from a reader: the section was built that way. What remains of you after you leave is written on the privacy page.
The connection requires TLS 1.2 or 1.3. A browser ten years old will not open the site; we will not lower the requirement for it.
Write to us. Say what you did and what came of it; add the address of the page if you can. We answer within a week. While we repair it, we ask you not to make the finding public; when it is fixed we will write and tell you what was changed and when.
This page was written on 22 August 2026. It changes with the section: when the section is changed, so is this page.