Documentation

We believe the web already has identities. We just never used them.

Freedom of communication, without hard verification. No email to confirm. No phone number to surrender. No ID checks, no gatekeepers deciding who is allowed to speak. If you control a domain, that control is the verification — nothing else is needed.

Talk directly to the owner. Every account here is a domain, and behind every domain is its owner. Mention @example.com in a post or open a conversation from their profile — and you are talking to the person who controls that domain. Directly. No intermediaries, no middlemen with blue checks.

Honesty over speculation. When a domain's DNS record changes, we record the provable fact — Domain access changed — and nothing more. We never guess why.

Posts are historical documents. Every post keeps the fingerprint of the identity that published it. Forever.

Text only. No avatars to curate, no videos to scroll past. Words are the product.

No usernames. No emails. No phone numbers.
Your domain is your identity.

1. Enter your domain on the Connect page.
2. Add one DNS record — we show you the exact TYPE / NAME / VALUE:
   TYPE TXT

   NAME _twtr (or _twtr.yourdomain.com)

   VALUE twtr=<token>
3. Verify. We re-check automatically every 8 seconds; DNS propagation usually takes a few minutes. The challenge is valid for 15 minutes.

That's it — you're in, with your emoji fingerprint.

Signing in later is the same flow. The TXT value is public — anyone can dig it — which is why every login asks for a fresh record: only writing a new value proves you still control the domain now. Reading the old value proves nothing and never grants access.

Because the value must be fresh, signing in from a new browser always starts a new identity period. To move an existing session between browsers, use Settings → Transfer (QR) instead — no DNS change needed.

Even easier: on the login page pick Log in with a QR code and scan it with a browser where you are already signed in — approving there signs this browser in with a copy of that session. No DNS, no new identity period.

Your identity fingerprint is 5 emoji, derived deterministically from your domain and the current verification period. It can't be chosen, bought, or faked.

• Within a session the record stays the same → same fingerprint, same identity.
• The record changes (rotation, new owner, or signing in from a new browser) → a new identity period begins, the profile records a Domain access changed event, and sessions authorized by the old record die.
• Old posts never change — they keep the fingerprint of the identity they were published under.

Click the emoji next to any domain name to see its full identity history — every fingerprint the domain ever had, with periods.

• Up to 280 characters. Text only — by design, not a limitation of this sprint.
• Reply to any post; replies form threads.
• Mention a domain as @domain.tld — it becomes a link and lands in that domain's Mentions tab.
• Every post and message is cryptographically signed by the server — provable origin.

Home has three tabs. Global — the whole public timeline, with Follow buttons right in the feed. Following — posts from the domains you follow (and your own). Mentions — where @you shows up.

Follow from the feed or from a profile — posts of followed domains appear in your Following tab immediately.

Open any profile → Message. DMs go straight to the owner of that domain — that is the point of domain identity: an address that reaches the person in control of it. No follower requirements, no approval queue.

A session is a browser, not a domain.

• Add domains — connect another domain from the same browser and switch between them from the sidebar or Settings at any time. Each added domain goes through its own DNS verification.
• Transfer to another device — Settings → Show QR code → scan it on the other browser. Codes are single-use and valid for 5 minutes; the new device gets its own, separately revocable session. Prefer this over re-verifying: it keeps your identity period and fingerprint.
• QR sign-in — the reverse direction: the new browser shows the QR (login page → Log in with a QR code) and a signed-in browser approves it by scanning. Same clone, same guarantees — single-use code, 5 minutes, own revocable session.
• Active sessions — Settings shows every browser where your domain is verified: device, last seen, and a Revoke button.
• If a domain's DNS record changes, that domain is stripped from every session that held it — a new owner inherits nothing, not even the other domains in those browsers.

Which domains can join? Any registrable domain in any zone — gTLD, ccTLD, IDN (punycode is fine), even twtr.dev itself if its owner connects it. DNS control is the only gate; we maintain no whitelist and no reserved names.

Must I keep the TXT record? Yes — it's your login. Keep the current record in place; re-verify whenever you want to rotate the token.

What if I lose the domain? Then you lose the identity — honestly, by design. The domain's next owner starts a new identity period; your old posts remain, with your fingerprint.

Images? Video? Never. Text only.

What does it cost? Nothing today. Paid subdomains — your own _twtr record on a subdomain — are planned as a Pro feature.