Skip to content

docs: add sender verification spec (exploratory)#21

Merged
scourtney-godaddy merged 1 commit intomainfrom
sender-verification-spec
Apr 8, 2026
Merged

docs: add sender verification spec (exploratory)#21
scourtney-godaddy merged 1 commit intomainfrom
sender-verification-spec

Conversation

@scourtney-godaddy
Copy link
Copy Markdown
Contributor

Summary

Adds SENDER_VERIFICATION_SPEC.md, an exploratory design for per-sender email verification using ANS principles. Updates README.md with a link under a new Exploratory section.

The design applies per-entity signing keys, a SCITT transparency log, and DNS discovery to email senders. It targets business email compromise where domain-level authentication passes but the sender is compromised or impersonated.

Not an ANS protocol feature. A standalone design sketch.

Test plan

  • Mermaid diagrams render in GitHub preview
  • No internal hostnames, vendor names, or real infrastructure identifiers

Generated with Claude Code

@scourtney-godaddy scourtney-godaddy requested a review from a team April 8, 2026 16:13
Per-sender email verification using ANS principles: per-entity signing
keys sealed into a SCITT transparency log, discoverable via DNS. Targets
business email compromise where DKIM/SPF/DMARC pass but the sender is
not who they claim. Includes data formats, mermaid diagrams, gateway
verification path, BIMI integration, and Trust Index composition.

Exploratory sketch, not an ANS protocol feature.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@scourtney-godaddy scourtney-godaddy force-pushed the sender-verification-spec branch from 41d1f88 to 381bcd2 Compare April 8, 2026 16:17
@scourtney-godaddy scourtney-godaddy added this pull request to the merge queue Apr 8, 2026
Merged via the queue into main with commit c5192c3 Apr 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants