Trust cockpit

Daily monitoring of your cryptographic trust surface — DBR score, findings, and meaningful change detection.

Watched domains

Domains you're monitoring · per-tier cap · alert preferences.

Trust event history

Private scan history and meaningful changes for your monitored domains.

Trends + benchmarks

DBR trend, score-breakdown over time, and sector context.

Alert delivery

Email, webhook, and weekly digest — how Cipherwake notifies you of meaningful change. (Paste a Slack incoming-webhook URL in the webhook field if you want Slack delivery.)

Integrations

GitHub Action, CLI, API, webhooks, and approved-vendor enforcement.

Account + security

Plan, billing, security, and data preferences.

Setup status

Which Cipherwake surfaces are wired up for your account. None of these are required — they each cover different workflows.

Quotas & usage

What your tier is consuming this month. Resets on the 1st.

Domain of record

Your account's primary monitored domain. Claiming is optional — monitoring fires either way. It unlocks future owner-only controls (rebuttal text on public reports, faster takedown rights).

Subscription

Current tier
Included on your plan

    API access

    Free CI uses GitHub OIDC metering — GitHub Actions do not need a signed API key. Use this key for CLI / API calls where required.

    Rotation displays the new key once — copy it immediately.
    Quota by tier: Free 100/mo per repo (OIDC) · Founder Pro 5,000/mo. Launch pricing locked while subscription active.
    Domains monitored
    on your current plan
    Scan cadence
    Daily
    re-scan within 24h
    Alerts
    Email
    on meaningful change
    Ownership
    Public
    unclaimed · monitoring active
    • Loading…

    Monitoring cadence

    daily · next scan within 24h
    TLS observation
    public handshake + cipher class
    CT log synchronization
    new cert issuance detection
    SPKI continuity check
    public-key fingerprint diff
    Script inventory diff
    3rd-party host appear/remove
    Header posture compare
    HSTS · CSP · DMARC
    Subdomain surface scan
    DNS + CT-derived hostnames
    Next daily scan window: 02:00–06:00 UTC · See faster cadences →
    Email
    Active
    on meaningful change
    Domains covered
    1
    monitored
    Rules
    Balanced
    meaningful changes only
    Last alert
    None yet
    since baseline today

    Delivery channels

    Where Cipherwake sends meaningful trust-change notifications.

    Email
    Active

    Sends meaningful changes to your account email by default. Override the destination below.

    Webhook
    Founder Pro

    Outbound HMAC-SHA256 signed POST. Send trust diffs to your own server or any HTTPS endpoint.

    Signing secret:
    Weekly digest
    Included

    Mondays 09:00 UTC — engineer-targeted recap of the past week (alerts, subdomain/script/cert changes, top score movers).

    Alert rules

    Cipherwake fires email/webhook alerts only when these rules match — never on routine no-change scans.

    Active
    DBR score drops or grade falls
    Material regression on the trust posture.
    Active
    Certificate rotation or near expiry
    Cert renewed, issuer changed, or < 14 days remaining.
    Active
    TLS posture changes
    RSA-KEX appears, hybrid PQC lost, TLS version drops.
    Active
    SPKI / public key changes
    Unexpected rotation outside cert renewal window.
    Active
    New third-party script detected
    Polyfill.io-style supply chain change.
    Active
    Subdomain takeover signal
    Dangling CNAME to a deprovisioned third-party service.
    Free uses Cipherwake's Balanced rule set. Founder Pro unlocks per-rule on/off toggles and custom thresholds.

    Recent deliveries

    Last 50 alerts and their delivery outcomes per channel.

    No alerts sent yet
    Daily monitoring is active. Alerts appear here once Cipherwake detects a meaningful change.
    armed
    Baseline captured
    Next scan compares against this state. We deliver only when changes are meaningful.
    GitHub Action
    Not connected
    100/repo/mo via OIDC
    CLI
    Available
    npx pqcheck
    Webhooks
    Founder Pro
    outbound delivery
    Vendor allowlist
    Founder Pro
    script policy

    GitHub Action — Trust Diff CI

    — / — calls this month

    Fails your CI build when the public trust surface regresses. Comments diff results on every PR. No API key needed — Free tier uses GitHub OIDC.

    CI behavior
    Balanced fails CI when any fires:
    • DBR score drops by ≥ 1.0
    • Grade drops by ≥ 1 band
    • Certificate expires within 14 days
    • HSTS or CSP removed · DMARC weakens to "none"
    • New third-party script host appears
    • SPKI / public key changes
    • New high-risk TLS/cert finding appears
    Underlying config: fail-on: balanced
    Baseline
    GitHub Action snippet
    - uses: cipherwakelabs/pqcheck@v4
      with:
        mode: trust-diff
        domain: your-domain.com
        baseline: last-week
        fail-on: balanced
        comment-on-pr: true

    CLI — pqcheck

    npm package →

    Run scans from any terminal. Same trust posture data the GitHub Action and Dashboard use.

    Webhooks Founder Pro

    See Founder Pro →

    Send trust diffs to your endpoint with HMAC-SHA256 signing. Available on Founder Pro — paste a URL on the Alerts tab after upgrading.

    Approved vendor scripts Founder Pro

    Mark intentional third-party scripts (Stripe.js, Google Analytics, etc.) as approved. Vendor change alerts only fire on unapproved drift — filters the noise from benign vendor updates.

    Scans recorded
    across watched domains
    DBR changes
    0
    in selected window
    Cert / key
    0
    alerts in selected window
    Script changes
    0
    alerts in selected window
    Alerts emitted
    0
    across all event types

    Trend view

    Timeline

    Chronological events grouped by date. Each row shows before → after values for DBR, cert, key, scripts, headers, or alerts.

    Baseline analysis

    Baseline captured for your monitored domain. Trend and change-density insights populate after future scans.

    Baseline · today
    your monitored domain
    DBR baseline established · daily monitoring active.
    ·

    Score anatomy

    DBR risk polygon + per-component contribution. Bigger polygon = healthier posture. Methodology →

    Key exchange is typically the largest DBR driver until hybrid PQC key agreement is shipped.

    Scan cadence

    Daily monitoring activity for the last 90 days. Each cell = one day. Hover for details.

    No data Scan completed Scan + diff detected Missed window

    Finding categories

    Categorized counts from the live scan. Lets you see at a glance whether risk is concentrated in TLS, email security, headers, or third-party scripts.

    Certificate & CT activity

    Observed certificate history from the public TLS handshake + Certificate Transparency logs. Real history even before private monitoring accumulates.

    What would improve this score?

    Prioritized technical fixes ordered by DBR impact + ease of implementation. Cipherwake doesn't push tickets — these are starting points for a posture review.

    1. Loading prioritized fixes…

    DBR trend

    Decryption Blast Radius score over time for your monitored domains. Free shows 30 days; Starter 90; Growth/Scale 365.

    Current avg
    30-day delta
    Domains

    Change anatomy

    Which DBR components moved most. Helps answer "why did the score change?"

    Portfolio risk position

    Where you sit vs the public-scan corpus + the biggest fix you can ship.

    Your worst DBR
    vs corpus
    Last 7 days
    Biggest fix

    Percentile = your worst-domain DBR vs the latest score of every distinct monitored domain (last 30d). Biggest fix ≠ biggest DBR driver: the Drivers panel below identifies where your risk sits (e.g. key exchange); the Biggest fix card identifies where you can act first given effort (e.g. a DNS TXT record). Root-cert and PQC-server-stack findings are excluded from Biggest fix because they're vendor-dependent. Methodology →

    Integrations

    Cipherwake inside your release + monitoring workflow. CI gating, vendor enforcement, and portfolio export.

    Profile

    Your account identity. Display name shows up in welcome emails + (future) team invites.

    Email
    Display name

    Security

    Two-factor authentication + active session management. Recommended for accounts with paid subscriptions or admin access.

    2FA (TOTP) Not configured
    Active sessions
    Recent activity Loading…

    Last 50 sensitive actions on this account (deletions, exports, team changes, API-key rotations, identity unlinks). Older entries roll off per the data retention schedule on /privacy.

    Connected accounts Loading…
    Transfer account ownership

    Only the current account owner can transfer ownership. The new owner must have an active Cipherwake account (free or paid). We review every request and verify proof of corporate authority before completing the transfer; this isn't an automated flow.

    Need to transfer ownership? Use the feedback form with proof of corporate authority and we'll work with you.

    Preferences

    UI theme + alert delivery timezone. Defaults follow your system settings.

    Theme
    Timezone
    Global notification channels

    Master switches for delivery channels. Per-domain alert settings only fire on enabled channels — turning off Email here mutes ALL email alerts even if a domain is configured to send them.

    Email alerts
    Webhook alerts
    Webhook alerts
    Monthly digest email

    An end-of-month summary of your watched-domain posture changes, top regressions, and sector benchmarks. Separate from the weekly digest (which fires every Monday). Off by default.

    Monthly digest

    Privacy & data rights

    Export your data anytime (GDPR Art. 15) or delete your account permanently (Art. 17).

    Export your data
    Includes account profile, watched domains, scan history (last 1,000), alerts (last 90 days), API-key metadata, and subscription history. Stripe customer ID excluded — request directly from Stripe.
    Download JSON

    Delete account

    Permanent. Cancels any active subscription immediately (not at period end). All watched domains, scan history, alerts, and API keys are deleted. Cannot be undone — signing up again with the same email creates a fresh account.