chameleon

Credential simulation infrastructure

The link wears their brand. The capture lands in your vault.

One link per target. A page that matches the service you pinned. Every submit stored under a key only your passcode unwraps — and forwarded wherever you ask.

No card to sign up. No script tag on the target. Credential-only capture, so the page never invents a field it should not have.

https://login.contoso-mail.com/a7k2

Sign in to continue

contoso-mail.com

••••••••

A bare 404, not a stack trace, when the link is spent.

How it works

Point, pin, read.

  1. Point a hostname at it

    One ownership TXT record and one routing record, with a copy button per value. TLS is issued for you.

  2. Pin the brand and mint

    A slug is bound to one service and one brand. The capture form matches what that brand actually asks for.

  3. Read or forward

    Captures land in the vault, encrypted under your service passcode. Mail them out to a verified address, or export CSV.

Design decisions

Built to fail quietly in the right places.

Deny is identical

Bad host, dead slug, spent link, lapsed payment — the same bare 404. A victim learns nothing from the error.

Edge-first rendering

Cloudflare serves the page, not the control plane. A deploy or a reboot does not take live links down.

Tenant walls in the database

Row-level security, not query discipline. A missed filter returns nothing rather than someone else's row.

Honest delivery

Mail is queued, retried and visible. A provider throttle parks the row instead of burning the retry budget.

Facts

Where pages render
Cloudflare edge
Where captures rest
Your tenant vault
Key wrapping
AES-KW under PBKDF2
Session
30 min idle, 12 h cap
Retention
30 days, export anytime
Billing
Per service, 30 days
“Credentials only. An OTP box that never sees an OTP is worse than no box.”

Start now

One login, one org, your own vault.

Activation waits for a confirmed address. The first verification mail is on us.