aboutsummaryrefslogtreecommitdiffstats
path: root/docs/specs/2026-09-09-contacts.md
AgeCommit message (Collapse)AuthorFilesLines
25 hoursdocs: correct the Accept header and the dependency claimDanilo M.1-5/+10
The spec named a strict Accept: application/rdap+json while the plan, and so the code, sends application/rdap+json with application/json at q=0.9. A spec review caught the disagreement. The wider header is the right behaviour, since some registries serve plain application/json and a strict header would lose a contact that was published, so the spec moves to match the code and now records why. Both documents also claimed requirements.txt stays empty. There is no requirements.txt in this repository and there never has been, so the claim was true only vacuously. They now say the tool declares no dependencies, which is the thing actually being promised. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wrfqr2xqQfhtXCscU7zrdz
26 hoursdocs: spec the contacts subcommandDanilo M.1-0/+345
Settles what the umbrella design left open for this part: RDAP bootstrap, caching policy, and what happens for a netblock that publishes no abuse contact. Scope is IPs and domains, with a URL contributing only its host. The bootstrap files are fetched from IANA and cached with a long TTL, while responses are cached in memory for one run only: a stale bootstrap merely misses, but a stale abuse address sends a report into a dead mailbox silently. The registrable domain is found by walking up the labels and asking the registry rather than by bundling a Public Suffix List, which would be a transcribed table that goes stale weekly. Address extraction is a strict abuse-role match with no fallback. In particular it never constructs abuse@<domain>, because for a phishing domain that mailbox belongs to the attacker and mailing it would confirm both the catch and that the address is live. Adds a fourth non-negotiable property: a query carries a bare host or IP and never a URL. Property 1 governs what is published, and a query is a disclosure that appears in no report, so a path segment that parse deliberately flags rather than redacts would otherwise leak. Transport is urllib with an injected fetch, so requirements.txt stays empty and the suite keeps passing with sockets raising, for the whole suite rather than for everything except contacts. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wrfqr2xqQfhtXCscU7zrdz