Skip to main content
The Connected Ecosystem

One Discipline, Three Surfaces

DNS Tool is one expression of a single idea: measure honestly, declare your confidence, and never collapse uncertainty into a verdict it hasn’t earned. That idea is published as theory, applied as this platform, and practiced as human judgment.

Three Connected Surfaces

Theory

Intellectual Resistance

The published epistemics: the Verification Principle, the Owl Semaphore, and related frameworks — each carrying its own honest status label, from proven theorem to open proposal. This is where the reasoning is written down and held to account.

Applied

DNS Tool

The theory made operational. Every domain analysis is backed by RFC citations and an evidence-weighted confidence score, with the Owl Semaphore used to classify how each document should be read. See the Approach and Confidence Engine.

Human Judgment

Organic Computer

The human substrate behind the work: evidence-first analysis with AI treated as an instrument, not an author. Where a person, not a pipeline, owns the conclusion.

Framework Status Ledger

These are the frameworks published at Intellectual Resistance, shown with the epistemic status each carries there. The statuses are reproduced as published — not upgraded. DNS Tool claims as shipped only what it actually implements in code.

FrameworkStated StatusRelationship to DNS Tool
The Verification PrincipleProven TheoremImplemented in code — priors are protocol-specific, empirical, and bounded away from 0 and 1.
Carrier ColorModelInforms how findings are communicated; not implemented as scoring logic.
Societal Control LeversCandidate VariablesResearch direction; not part of DNS Tool.
The Owl SemaphoreAlgebra Proven, Partition OpenUsed as the four-state notation for document classification. See Owl Semaphore.
Star-Centric TransportProposalForward-looking proposal; not implemented.
Applied: DNS Tool & Organic ComputerShippedThe live edge of the work — this platform and the consulting practice behind it.

What DNS Tool Implements

Only the parts of the theory that exist in code are claimed here:

  • Evidence-weighted confidence scoring inspired by Bayesian reasoning, with analytic confidence declared separately (ICD 203). See the Confidence Engine.
  • RFC-cited findings — every recommendation traces to a requirement level (MUST / SHOULD / MAY). See the Approach.
  • Owl Semaphore classification — the four-state notation applied to how each document should be read. See Owl Semaphore.
  • A transparent, documented architecture you can inspect. See the Architecture.
Straight talk about your data.

We use two cookies, both essential:

  • _csrf — Prevents cross-site request forgery. Required for form submissions. Security-only.
  • _dns_session — Only exists if you choose to sign in. No account required to use DNS Tool.

We log your IP address for two reasons: rate limiting (so nobody abuses the service) and security (identifying malicious actors and complying with legal obligations). We check source geography for analysis accuracy — DNS responses vary by region, and knowing which resolver answered from where makes the science better.

No tracking cookies. No analytics cookies. No ad networks. No data brokers. Our code is open-core — the application framework is publicly available under BUSL-1.1 with timed Apache-2.0 conversion. Verify it yourself.

If you create an account and want out, account deletion removes your login and scan history. Public domain analyses remain available because they contain only public DNS records, already hashed. Full details: Privacy Policy.