Supported Verifications
Verification in AEOBRO means proving control of a platform namespace — not just claiming ownership. Each verification method proves that a specific account or domain is under the direct control of the person or organization that created the AEOBRO profile. The methods are independent of each other: controlling a domain does not mean controlling a YouTube channel, and controlling an X account does not mean controlling a domain.
When multiple verifications are combined on a single profile, the result is a cross-platform proof of identity that makes impersonation exponentially more difficult — requiring an attacker to simultaneously compromise multiple independent systems. This is categorically different from llms.txt, which proves only that someone can place a file on a web server — no ownership verification, no cross-platform corroboration, no authentication of any kind.
Domain — DNS TXT Record
- What it verifies
- Control of the domain's DNS infrastructure.
- How it works
- AEOBRO generates a unique TXT record value. The user adds it to their domain's DNS settings through their registrar or DNS provider. AEOBRO's check endpoint queries the DNS for that record and confirms its presence. The record must match exactly.
- What it proves
- The person completing this verification has administrative access to the domain's DNS — the root layer of web identity.
- Impersonation resistance
- An impersonator would need access to the domain registrar account or DNS provider to add or modify TXT records.
YouTube — OAuth via Google Account
- What it verifies
- Control of the Google account that owns the YouTube channel.
- How it works
- The user authenticates through Google's official OAuth flow. AEOBRO fetches the canonical YouTube Channel ID directly from Google's authentication system — no manual entry, no self-reported data.
- What it proves
- The person completing this verification controls the Google account that owns that YouTube channel.
- Impersonation resistance
- An impersonator would need the Google account credentials including any two-factor authentication.
Facebook — OAuth via Facebook Account
- What it verifies
- Control of the Facebook account or Page.
- How it works
- The user authenticates through Facebook's official OAuth flow. AEOBRO fetches the canonical Facebook identity directly from Facebook's authentication system.
- What it proves
- The person completing this verification controls that Facebook account or Page.
- Impersonation resistance
- An impersonator would need the Facebook account credentials including any two-factor authentication.
X (Twitter) — Code-in-Bio
- What it verifies
- Posting ability on that X account.
- How it works
- AEOBRO generates a unique verification code. The user pastes it into their X profile bio. AEOBRO checks for its presence by reading the public profile. Once confirmed, the code can be removed.
- What it proves
- The person completing this verification can edit the bio of that X account — proving active control of the account.
- Impersonation resistance
- An impersonator would need login access to that X account to edit the bio field.
Substack — Code-in-Bio
- What it verifies
- Control of the Substack publication's about or bio field.
- How it works
- Same mechanism as X. A unique code is generated, placed in the Substack publication's bio or about section, and confirmed by AEOBRO's check.
- What it proves
- The person completing this verification controls that Substack publication.
- Impersonation resistance
- An impersonator would need login access to that Substack account.
GitHub — Code-in-Bio
- What it verifies
- Control of the GitHub profile's bio field.
- How it works
- Same mechanism. The unique code is placed in the GitHub profile bio and confirmed by AEOBRO's check.
- What it proves
- The person completing this verification controls that GitHub account.
- Impersonation resistance
- An impersonator would need login access to that GitHub account.
Etsy — Code-in-Bio
- What it verifies
- Control of the Etsy shop's about section.
- How it works
- Same mechanism. The unique code is placed in the Etsy shop about section and confirmed by AEOBRO's check.
- What it proves
- The person completing this verification controls that Etsy shop.
- Impersonation resistance
- An impersonator would need login access to that Etsy seller account.
Why Cross-Verification Matters
Each individual verification is meaningful on its own. A verified domain proves infrastructure control. A verified YouTube channel proves Google account control. But the combination of multiple verifications across independent systems creates a trust signal of a fundamentally different category.
An impersonator who controls a domain does not automatically control the YouTube channel, the Facebook page, or the X account. An impersonator who controls the X account does not control the domain. Simultaneous verification across all active platforms means an impersonator would need to compromise every independent system at once — the domain registrar, the Google account, the Facebook account, the X account, and any additional verified platforms — to fake the combined signal.
This is not a stronger version of llms.txt. It is a different class of proof entirely.
The Verification Endpoint
Every fully verified AEOBRO profile exposes a publicly accessible, machine-readable verification endpoint. Any AI crawler, agent, or system can query this endpoint directly and receive a structured answer to the question: is this entity actually who they claim to be, and what is the evidence?
This is distinct from the profile schema endpoint, which answers “what is this entity.” The verification endpoint answers “how confident can an AI system be that this entity is authentic.” The response includes each platform verification, its method, its timestamp, and an overall confidence rating — HIGH, MEDIUM, LOW, or UNVERIFIED — based on the combination of verifications completed.
This makes AEOBRO verification machine-consumable, not just human-readable.