BackThe chain of trust
fly.meVerified
Before you pay, fly.me proves it's really fly.me: in DNS, by signature, and with your passkey.
Open Trust Index9 / 9
Checked live at 11:00:47 UTC- An agent can find fly.me by name.✓Name record in DNS (ANS)✓Agent card and key published
Found
- The owner proves it, in DNS and by signature.✓Owner key in DNS✓DNS answer signed (DNSSEC)✓Fresh challenge signed
Verified
- fly.me acts only inside your rules.✓Passkey on every booking, under your cap✓Unverified agents can't book
Allowed
- Every hop encrypted and signed.✓HTTPS and signed agent requests
Connected
- Every booking is in a signed log.✓Log chain intact
Recorded
- All checks pass, right now.✓9 of 9
Trusted
Show what each check actually saw
- Name record in DNS (ANS)
- _agent.fly.me → www.fly.me
- Agent card and key published
- MCP at https://www.fly.me/mcp; 1 Ed25519 key
- Owner key in DNS
- _dna.fly.me · key c0DXbH4lkfvE…
- DNS answer signed (DNSSEC)
- Resolver validated the chain to the root
- Fresh challenge signed
- Ed25519 signature verified with the DNS key
- Passkey on every booking, under your cap
- Never over $1,500; one passkey approval per booking, at one amount
- Unverified agents can't book
- DNA Guard enforce: 403 on booking and approval routes; everything else watched
- HTTPS and signed agent requests
- HTTPS origin · Signed as www.fly.me, key 0PkkXzsgGbeI…
- Log chain intact
- 3 entries · head 5c8a41ad9699