Skip to content
emailrules.today

Trust

How a finding earns its place.

Sources

Primary material, attached to the action.

Each rule names its publisher, source URL, publication date when the publisher provides one, and the date Emailrules last verified it. A report snapshots the rule and source used for that check.

Browse the source register

Method

How a claim becomes a rule

  1. 01

    Find

    Use a regulator, standards body, mailbox provider or sending-platform primary source.

  2. 02

    Extract

    Record the exact published fact without turning it into Emailrules advice yet.

  3. 03

    Interpret

    State who it applies to, when it starts and what remains uncertain.

  4. 04

    Detect

    Define the bounded message, DNS or context evidence that can support a finding.

  5. 05

    Review

    A person approves provider and regulator changes before publication.

  6. 06

    Recheck

    Watch the source, retain its verification date and publish corrections when the reading changes.

Read the full methodology

Coverage

A bounded check, not a universal verdict.

Campaign preflight covers message structure, authentication evidence, unsubscribe evidence, sender identity, selected measurement risks and rules applicable to the context supplied. It does not predict inbox placement, certify legal compliance or infer recipient geography.

See the coverage map

Freshness

Verification dates stay visible.

The corpus contains 41 public rules. The newest recorded verification is 4 Aug 2026. Source pages are checked for changes, but a machine never publishes a changed interpretation.

Inspect freshness

Corrections

Site corrections are not market changes.

Provider, platform and regulator changes belong in Changes. Corrections to Emailrules claims are recorded separately so an internal fix cannot be mistaken for an external event.

Read or report a correction

Campaign handling

Untrusted input with no active capabilities.

  • Webhook signatures are verified against the untouched webhook body.
  • Campaign HTML is never rendered; remote images are not fetched and links are not opened.
  • Attachments are not interpreted as campaign content.
  • The report stores normalized findings, not the body, subject, recipient or raw headers.
  • Could not determine is kept separate from pass and fail.