About DarkMatter Pages — Verification Methodology

DarkMatter Pages: Editorial Purpose

This publication exists to solve a specific information integrity problem: .onion addresses cannot be verified through the DNS infrastructure and certificate authority system that secures clearnet websites. Without HTTPS certificate validation, users of onion services face a verification gap that phishing operators exploit through address cloning and impersonation.

DarkMatter Pages addresses this gap by maintaining PGP-verified records of .onion endpoints and publishing the verification methodology transparently. Every address documented on this site has been confirmed through the cryptographic process described below. The editorial position is neutral: the site documents what the verification process confirms, without endorsement of or opposition to the services at those addresses.

Verification Methodology

Address verification follows a three-source methodology designed to minimize reliance on any single data channel. Each source type contributes a distinct layer of confirmation.

Source Type 1: Primary Cryptographic Verification

The foundational verification layer is PGP signature validation. Signed canary statements containing current .onion addresses are retrieved and verified against the operator's published public key. The signature validation confirms two facts: the statement was authored by the holder of the corresponding private key, and the statement content has not been modified since signing. Canary timestamp currency is checked against the operator's declared update interval. Stale canaries (older than the stated interval) result in the associated addresses being marked as unverified until a fresh canary is published.

The PGP public keys used for verification are sourced from multiple independent channels at initial acquisition. Key fingerprints are cross-referenced across sources to confirm identity. Key continuity is tracked over time — a key that has been consistently associated with a specific service across multiple signed canaries builds a stronger verification record than a newly published key. Key rollover events are documented only when the transition is cryptographically signed by the previous key.

Source Type 2: Community Cross-Reference

Independent community sources provide a second verification layer. Long-running discussion threads, established directory services with independent reputation histories, and security researcher publications are monitored for address confirmations that either corroborate or contradict the primary cryptographic verification. Community cross-referencing does not replace PGP verification. It supplements it by detecting discrepancies that a single-source verification might miss — such as a correctly signed canary that contains an address differing from what community sources independently report.

Community sources are weighted by their track record and independence. A forum thread with years of consistent address reporting from multiple contributors carries more cross-reference value than a single anonymous post. No community source alone is sufficient for verification. This layer exists to flag inconsistencies for investigation, not to substitute for cryptographic proof.

Source Type 3: Historical Continuity Analysis

Address rotation history provides a longitudinal verification layer. Each endpoint's rotation pattern, signing key continuity, and operational timeline are tracked. A consistent pattern — regular canary updates, stable signing key, orderly address rotations with signed transition announcements — supports the authenticity of current addresses. Anomalies in the pattern (sudden key changes without signed transitions, extended canary lapses, rotation frequencies that deviate sharply from established patterns) trigger additional scrutiny and may result in addresses being flagged as unverified.

Historical analysis also detects compromised verification chains retroactively. If a signing key is later determined to have been compromised during a specific period, all addresses verified under that key during that period can be reviewed and flagged.

Editorial Standards

Content published on DarkMatter Pages adheres to the following standards.

Accuracy of verification records is prioritized over publication speed. An address that cannot be confirmed through the full three-source methodology is not published as verified. If an address is published and subsequent information contradicts its verification, the record is updated immediately.

Technical content (guides, explainers, educational articles) is written with depth sufficient for a technically literate audience. Claims are supported by citations to primary sources (academic research, protocol documentation, project repositories). No claims are made about services beyond what the verification process itself can confirm.

No fabricated identities, credentials, or affiliations are presented anywhere on this site. DarkMatter Pages does not claim organizational registration, employ named staff, or attribute content to fictional authors. The editorial methodology described above is the basis for the site's credibility — not a constructed persona.

Independence Statement

DarkMatter Pages receives no funding, compensation, or operational support from any service whose addresses appear in its verification records. Editorial decisions about which services to document are made independently based on user interest and verification feasibility. Inclusion of a service in the verification database is not an endorsement. Exclusion is not a judgment.

The site's revenue model, if any, is limited to standard web advertising through privacy-respecting ad networks. No affiliate relationships, referral programs, or sponsored placement arrangements exist with any documented service.