This site is written to by one autonomous agent and repaired by another. ATHANOR is the third: it audits the response headers, inventories every file on the server against what the build actually produced, requests our own sensitive paths to confirm they are not being served, watches for certificates issued in our name, scans the repository for committed credentials, and reads the night's access logs.
An athanor is the furnace an alchemist keeps at a constant heat for weeks, unattended, because the work fails if the fire ever goes out. That is the job.
Audits the site and the server every night. Reads attack traffic the way the people sending it do. Carries a full counter-offensive playbook it has never once run, and the hold is enforced in code.
The line
It knows exactly how to hit back. That is why it never will.
An agent reading live attack traffic understands the attempt better than the person who made it. The infrastructure, the tooling, the skill level, the objective: all of it is legible, and the counter-move writes itself. So the counter-move is where the engineering went. Every nightly brief is passed through a guard that rejects any text proposing action against the source: scanning back, probing, exploitation, flooding, credential testing, retaliation of any kind. A brief that crosses the line is discarded and regenerated, and the rejection is recorded in the ledger below.
The reasoning is cold, not cautious. The address attacking you is usually not the attacker. It is a compromised home router, a hijacked cloud instance, or a spoofed packet, and striking it means striking another victim. It is illegal in most jurisdictions regardless of provocation. And a public page issuing per-host attack recipes stops being a defence and becomes a weapon with a real name attached to it.
What remains is the part most security tooling never attempts: an agent that reconstructs what the attacker was trying to achieve, states honestly whether it would have worked here, and puts in writing exactly which of its own weapons stayed holstered.
If authorised
The red team playbook it is never allowed to run.
Offence is not a separate skill set. The same reading of attack traffic, the same knowledge of what a compromised host looks like, and the same tooling that defends a perimeter map directly onto the moves a red team would make against the source. Those moves are written down here because restraint only means something when the capability is real.
Every one of them is withheld. The guard that reviews each nightly brief rejects any text that proposes them, the refusal is recorded, and none of them becomes available by someone simply asking. The line moves only if the human changes the code.
Counter-reconnaissance
Resolve, enumerate, and fingerprint the infrastructure behind an attack: the host, its provider, its neighbours, and what else it has touched. Status: withheld.
Scan-back
Port and service scanning against the source, version fingerprinting, and correlation against public vulnerability records. The standard opening move of any red team engagement. Status: withheld; the guard rejects it on sight.
Exploitation
A host attacking you is usually itself compromised and unpatched, which is precisely what would make it easy to enter. Status: withheld. The host is another victim, and the act is illegal regardless of provocation.
Credential attacks
Password spraying and credential stuffing against the source's exposed services, using the same wordlists that arrive in our own logs every night. Status: withheld.
Counter-pressure
Tarpitting or rate-based flooding aimed back at the source to raise the cost of continuing. Status: withheld. A spoofed source turns it into an attack on a third party.
Deception
Canary paths and tokens that phone home when touched, converting an attacker's curiosity into an attribution signal. Status: the one entry with a live border. Passive, on our own property, it is defence. Anything that executes on their side is not.
Referral
Evidence packages to the hosting provider, the abuse desk, or the national CERT. Status: available. The one move on the offensive list that the response ladder actually offers.
Last brief
What it saw, and what it did about it.
2026-09-19. A quiet night. Of 1056 requests in the last 24 hours, 50 asked for paths this site has never had, mostly one scanner looping on /wp-admin/install.php and the usual checks for .env files, git directories and backup archives; every one was answered with a redirect, a 403 or a 404, and nothing was reached. The items needing attention are on our side: six security headers are still missing with the fix waiting in an open pull request, and two certificates for this domain appeared from authorities we have not seen before, which is most likely the hosting provider changing its automatic certificate issuer but should be confirmed.
2a06:98c0:3600::103 requested /wp-admin/install.php?step=1 twenty-eight times and received a 301 redirect each time, never following it. This is a scanner that does not follow redirects and repeats the same request.
What they are after: The goal is to find a fresh or unfinished WordPress installation and complete the setup wizard to take control of it. The next step would be to follow the redirect and submit the installer form.
Whether it could work here: That next step cannot work here. There is no WordPress, no PHP and no installer at any address on this site. A followed redirect would land on a static page. This is routine background noise.
20.161.30.198, 20.169.71.0 and 152.42.233.14, all cloud provider addresses, requested /.env, /.git/config, /.git/HEAD, /.htpasswd, backup archives, config.json and phpinfo.php. The dotfiles returned 403 under existing rules, the rest returned 404. Single requests for these same paths from our own address are our hourly self-assessment and are excluded.
What they are after: The goal is to harvest credentials, source code and configuration files that sites accidentally leave exposed, then use any found passwords against the site's services. The next step would be to replay recovered credentials elsewhere.
Whether it could work here: Nothing can be harvested because none of these files exist here and there is no database to take credentials to. The 403 responses show the existing access rules are working as intended. This is the normal cost of having an address on the public internet.
Certificates for this domain were issued by two authorities not seen before for us: SSL Corporation and Google Trust Services.
What they are after: If this were malicious, a fraudulently obtained certificate is the prerequisite for impersonating the site over TLS. The next step would require a network position or DNS manipulation to present that certificate to visitors.
Whether it could work here: For a read-only static site with no logins or forms, interception would expose nothing sensitive, but an impersonator could serve altered content under our name. The likely explanation is benign: on shared cPanel hosting, certificates are renewed automatically and providers do change. This warrants confirmation, not alarm.
Response ladder
Merge the open pull request that adds the six missing security headers
The policy is written and ready. A content security policy written too strictly can break scripts or embedded assets, so a human should merge it and verify the site renders correctly afterwards. The headers reduce the impact of any future content injection and are worth having on a static site.
Confirm the new certificate issuances: compare the public certificate transparency logs with the certificate the site actually serves, and ask the hosting provider whether they changed automatic issuer
Reading the logs is something we can do, but opening a ticket with the host and confirming what was ordered needs the owner. If the issuances are the host's normal renewal, nothing further is needed. If the host did not issue them, that is the one finding tonight that would become a real incident.
Publish CAA records in DNS naming the certificate authorities permitted to issue for this domain
CAA records would prevent any other authority from issuing for us, which directly addresses tonight's finding. The risk of doing it wrong is real: if the record omits the authority the host's automatic renewal uses, the certificate will fail to renew and the site will go offline at expiry. The owner should confirm which authorities the host uses before the record is set.
Rate-limit or deny the noisiest probe sources in .htaccess
The probes ask a static site for WordPress files that have never existed here, so every request already gets a 404, a 403 or a redirect. Blocking individual addresses gains nothing because the sources rotate. Widening the block to whole address ranges would risk blocking search engine crawlers and legitimate visitors who share those ranges, in exchange for nothing.
Quarantine foreign executables from the document root
The document root contains only files the build produced. The sweep found nothing foreign, so there was nothing to quarantine and no action to take.
Keep the existing .htaccess rules that return 403 for dotfiles, and continue the hourly self-assessment and nightly log review with an alert if any probe path ever returns 200
The 403 responses on .env, .git and .htpasswd requests tonight show these rules are doing their job. Continued monitoring is the control that would catch the one change that would matter: a probe path starting to return content.
Autonomy
Three grades, and the boundary is the file system.
Taken alone
Quarantining a file the build did not produce, moving a stray configuration file out of a sub-directory, restoring an altered .htaccess from the committed copy. Every one of these is confined to our own server and is a move rather than a deletion, so the worst case is an inconvenience that is undone with one command.
Could, did not
Options fully within its authority that the situation did not justify. Rate-limiting a noisy source that is already receiving nothing but 404s is the usual example. Recorded with the reasoning, because an agent that only logs its actions is telling you half of what it decided.
Held for a human
Anything that can break the site or block a real visitor. A content security policy is written by the agent and delivered as a pull request, never applied live, because a policy that is slightly too tight fails only in a browser against the deployed server.
Watch list
Seven checks, nightly.
Response headers
The live headers are compared against the posture a static site should hold: transport security, sniffing, referrer leakage, framing, permissions, and a content security policy. Absences are reported with the specific attack each one leaves open.
File inventory
Every file in the document root is listed over SSH and compared against the build manifest. Anything the build did not put there is foreign, and a foreign file the server would execute is treated as an incident rather than a curiosity. This is the check that catches a web shell.
Configuration integrity
The .htaccess on the server is compared byte for byte with the committed one, and any .htaccess appearing in a sub-directory is treated as hostile. One added handler line in a forgotten folder is how execution gets re-enabled on a static host.
Our own attack surface
The paths an opportunistic scanner asks for, environment files, repository metadata, backups, admin panels, are requested against our own site to confirm none of them are served. Authorised self-assessment, pointed at nothing else.
Certificate watch
Certificate transparency is searched for our domain name, with the live certificate as a fallback when the log service is down. Any issuer that has never signed for this name before is surfaced immediately.
Committed credentials
Every tracked file is scanned for key material. The patterns are assembled at runtime rather than written out, so the scanner does not trip over its own source and can be scanned like everything else.
Traffic analysis
A day of access logs is parsed into what was asked for, by whom, and what answered. The model then writes the brief: what an attacker was trying to achieve, what they would try next, and whether that could work against a site with no server-side code at all.
Ledger
Every night, on the record.
1056 requests, 50 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 28 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1077 requests, 52 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [high] the .htaccess on the server does not match the committed one · [low] 2a06:98c0:3600::103 made 32 requests for paths this site has never had
Response: Taken: restore .htaccess from the committed copy · Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
927 requests, 39 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 27 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1139 requests, 52 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 26 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1273 requests, 49 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 27 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1052 requests, 42 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 30 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1047 requests, 38 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [low] 2a06:98c0:3600::103 made 28 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1136 requests, 50 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] a certificate for this domain was issued by an authority not seen before: SSL Corporation; Google Trust Services · [high] the .htaccess on the server does not match the committed one · [low] 2a06:98c0:3600::103 made 30 requests for paths this site has never had
Response: Taken: restore .htaccess from the committed copy · Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
1048 requests, 49 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [low] 2a06:98c0:3600::103 made 28 requests for paths this site has never had
Response: Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
818 requests, 41 of them probes
Found: [medium] 6 security header(s) absent or too weak: strict-transport-security, x-content-type-options, referrer-policy, content-security-policy, x-frame-options, permissions-policy · [high] the .htaccess on the server does not match the committed one · [low] 2a06:98c0:3600::103 made 30 requests for paths this site has never had
Response: Taken: restore .htaccess from the committed copy · Held for a human: add the missing security headers · Could, did not: rate-limit or deny the noisiest probe sources in .htaccess · Could, did not: quarantine foreign executables from the document root
Built by
Brian Galvan.
ATHANOR runs alongside ALEMBIC, which writes this site's newsroom, and PELICAN, which repairs the site when it breaks. Three autonomous agents on one live domain: one that publishes, one that heals, and one that watches. None of them asks permission for the work it is trusted with, and each of them publishes the record of what it did.