scanned May 24, 2026

Doma

doma.xyz

blockchainVisit site →

Doma is a blockchain network for tokenizing and trading domain assets

60/100

Tier 4 · Agent-Ready

Content answers59/100
Protocol plumbing63/10010 of 16 checks pass
Re-audit3364h ago· 1 credit

Scored by asking 15 questions a buyer of a blockchain product asks, then grading this site’s own pages: answered, hedged (partial or vague), or silent (no page answers it). How scoring works

15 buyer questions · graded against the site’s own pages

5 of 15 come back answered. 7 get a hedge. 3 meet silence.

5 answerable7 half-answers3 silent

Goes silent · operations · high importance

When I sell a tokenized domain on the Doma Marketplace, what percentage royalty does the original minter receive on secondary sales, and can this be configured per domain?

Goes silent · technical · medium importance

I'm building a registrar integration and need to know: what are the rate limits on the MPP /register API, and is there a paid tier with higher throughput?

This report is public. Own doma.xyz? Claiming is free: crawl every page, re-audit as you fix, and track your score over time.

Sign in to claim

The fix queue

40 points sit between doma.xyz and 100: 10 open questions and 6 missing protocol checks, ordered by estimated payoff.

Point estimates are per fix under scoring v2. They are not additive to a promised total.

01operations · importance highGoes silent+7 content pts est.

When I sell a tokenized domain on the Doma Marketplace, what percentage royalty does the original minter receive on secondary sales, and can this be configured per domain?

What the pages say

No page on the site addresses this.

The fix

Add documentation on royalty rates for original minters on secondary sales and whether they can be configured per domain.

Where we looked: /agentic-commerce/skills/secondary-sales, /.well-known/skills/secondary-sales/SKILL.md, /api-reference/doma-fractionalization, /api-reference/doma-fractionalization.md, /fractionalization-unlocking-domain-ownership-for-all, /domainfi-explained-how-domain-buyouts-work-on-doma, /domainfi-explained-how-domain-buyouts-work-on-doma, /doma-weekly-buyouts-in-action-46m-volume-and-first-dominion-2026-speakers-announced

confidence high · grounding synthesized · weight 0.00 · Absent

02technical · importance mediumGoes silent+7 content pts est.

I'm building a registrar integration and need to know: what are the rate limits on the MPP /register API, and is there a paid tier with higher throughput?

What the pages say

The retrieved chunks do not specify rate limits for the MPP /register API, nor do they mention a paid tier with higher throughput.

The fix

Add rate limit specifications and any tiered throughput or paid-plan options to the MPP /register API documentation (e.g., in the doma-mpp SKILL.md or a dedicated MPP API reference page).

Where we looked: /.agents/skills/doma-mpp/SKILL.md, /agentic-commerce/skills/mpp.md, /api-reference/authentication-and-rate-limits

confidence high · grounding synthesized · weight 0.00 · Absent

03getting-started · importance mediumGoes silent+7 content pts est.

I'm trying to tokenize a two-character domain like 'x.io' — does Doma enforce any minimum character length for domains to be eligible for tokenization?

What the pages say

No page on the site addresses this.

The fix

Add documentation clarifying whether there are minimum or maximum character length requirements for domains to be eligible for tokenization, including short second-level domains like 'x.io'.

confidence high · grounding world-knowledge · weight 0.00 · Absent

Hedged · 7 of 15 questions

A buyer gets something, then has to guess the rest. Expand any row for the evidence and the fix.

04I own a .ai domain and a .io domain — does Doma support tokenization for all gTLDs and ccTLDs, or is there a published list of supported extensions?getting-startedHedges+4 pts est.

I own a .ai domain and a .io domain — does Doma support tokenization for all gTLDs and ccTLDs, or is there a published list of supported extensions?

What the pages say

The chunks do not confirm that Doma supports all gTLDs and ccTLDs, nor do they provide a comprehensive published list of every supported extension. However, your specific domains are explicitly mentioned in multiple places: the Doma FAQ states that on Testnet, “only Web2 domains (like .com, .ai, .io, .xyz) can interact with the Doma Testnet,” a blog post lists .com, .ai, .io, .xyz, and .cc as valid TLDs, and the getting-started guide demonstrates searching for an .io name. This confirms .ai and .io are supported examples, but the site does not provide a definitive, exhaustive list of all supported gTLDs and ccTLDs.

The fix

Publish a dedicated ‘Supported TLDs’ or ‘Domain Requirements’ page that explicitly lists all supported gTLDs and ccTLDs, or clearly states the scope of supported extensions.

Where we looked: /faq.md, /inside-domas-first-tokenized-domains-software-ai-brag-com-and-more, /getting-started.md

confidence medium · grounding world-knowledge · weight 0.40 · Vague

05When using the Doma Trade Tokens skill to swap domain tokens, what slippage tolerance options are available, and is there MEV protection built into the routing?technicalThin on specifics+4 pts est.

When using the Doma Trade Tokens skill to swap domain tokens, what slippage tolerance options are available, and is there MEV protection built into the routing?

What the pages say

The skill lets users set a custom slippage tolerance in basis points (bps) via the `--slippage` flag. Defaults vary by venue: Uniswap V3 trades default to 50 bps (0.5%), launchpad bonding-curve buys default to 100 bps (1%) with the skill suggesting 200–500 bps when `fillPercent < 20%` or warning when `fillPercent > 95%`, and `sellOnFail` refunds have no slippage setting because the rate is fixed. None of the retrieved chunks mention MEV protection.

The fix

Add documentation on whether the trade-tokens skill or doma swap routing includes MEV protection (e.g., private mempool, MEV-blocker integration, or none).

Where we looked: /.well-known/skills/trade-tokens/SKILL.md, /.well-known/skills/trade-tokens/SKILL.md, /agentic-commerce/doma-cli/commands, /.agents/skills/doma-protocol/SKILL.md, /.well-known/skills/trade-tokens/SKILL.md

confidence high · grounding world-knowledge · weight 0.40 · Absent

06For the Doma Secondary Sales skill, can the original domain owner set a custom royalty percentage, or is there a fixed platform fee regardless of the token contract?operationsHedges+3 pts est.

For the Doma Secondary Sales skill, can the original domain owner set a custom royalty percentage, or is there a fixed platform fee regardless of the token contract?

What the pages say

The retrieved chunks do not specify whether the original domain owner can set a custom royalty percentage, nor whether there is a fixed platform fee regardless of the token contract. The secondary-sales skill documentation states that all flows are powered by Seaport NFT primitives and cross-references the Doma Marketplace page for protocol-level fees, but no retrieved chunk details royalty configuration or fee structure.

The fix

Document the royalty and fee model directly in the Secondary Sales skill page or the Doma Marketplace page, explicitly stating whether sellers can set custom royalty percentages and what platform fees apply.

Where we looked: /agentic-commerce/skills/secondary-sales.md, /agentic-commerce/skills/secondary-sales

confidence low · grounding synthesized · weight 0.55 · Vague

07For the Doma Prime liquidity unlocking feature, what's the maximum loan-to-value ratio I can get against a premium domain, and does it vary by domain extension?operationsHedges+2 pts est.

For the Doma Prime liquidity unlocking feature, what's the maximum loan-to-value ratio I can get against a premium domain, and does it vary by domain extension?

What the pages say

The chunks confirm that Doma Prime lets you borrow against premium domains, but they do not state a maximum loan-to-value ratio or whether LTV terms vary by domain extension.

The fix

Publish specific underwriting criteria on the Doma Prime page, including the maximum LTV percentage and whether it varies by domain extension.

Where we looked: /prime, /introducing-doma-prime-liquidity-for-premium-domains, /introducing-doma-prime-liquidity-for-premium-domains

confidence high · grounding synthesized · weight 0.70 · Vague

08The Forge page mentions earning rewards — is there a mandatory lockup period for staked DOM tokens, and are there early unstaking penalties?operationsPage missing+2 pts est.

The Forge page mentions earning rewards — is there a mandatory lockup period for staked DOM tokens, and are there early unstaking penalties?

What the pages say

The retrieved chunks mention that staking domain tokens earns Season 0 points (Doma Leaderboard blog) and that tokenized domains can earn yield through DeFi staking (Doma Prime), but none of the retrieved chunks specify whether there is a mandatory lockup period for staked tokens or any early unstaking penalties. No substantive content from the Forge page was retrieved.

The fix

Publish a dedicated Forge or staking mechanics page that clearly states token lockup terms and any early unstaking penalties.

Where we looked: /launching-season-0-of-the-doma-leaderboard, /prime

confidence medium · grounding synthesized · weight 0.65 · Page missing

09Your privacy notice mentions collecting wallet addresses — how long does Doma retain on-chain transaction metadata versus off-chain KYC data after I delete my account?securityHedges+2 pts est.

Your privacy notice mentions collecting wallet addresses — how long does Doma retain on-chain transaction metadata versus off-chain KYC data after I delete my account?

What the pages say

According to Doma's Privacy Notice, on-chain transaction metadata — including domain asset transactions and DomainFi activities — is retained permanently on the blockchain and cannot be deleted or modified due to the immutable nature of blockchain technology. For off-chain personal information (which covers wallet addresses, names, email addresses, and other data you provide), Doma states it retains such data "for as long as necessary to fulfill the purposes outlined in this Privacy Notice, unless a longer retention period is required or permitted by law." However, the notice does not specify how long off-chain KYC data is retained after you delete your account.

The fix

Add a dedicated sentence or subsection to the Privacy Notice's Data Retention clause specifying retention periods or deletion procedures for off-chain personal/KYC data after a user deletes their account.

Where we looked: /privacy, /privacy, /privacy

confidence medium · grounding synthesized · weight 0.65 · Vague

10What's the target block time for the Doma blockchain, and how many confirmations are recommended before considering a domain transfer final?technicalHedges+2 pts est.

What's the target block time for the Doma blockchain, and how many confirmations are recommended before considering a domain transfer final?

What the pages say

The retrieved pages identify Doma Chain as the protocol's own blockchain and note that domain transfers are "confirmed and finalized on-chain," but they do not state the target block time or specify how many confirmations are recommended before a transfer is considered final.

The fix

Publish a technical specifications or architecture page for Doma Chain that includes target block time and the recommended confirmation count for domain transfer finality.

Where we looked: docs.doma.xyz, /faq

confidence high · grounding synthesized · weight 0.70 · Vague

What the pages already answer cleanly

5 of 15. Answered with enough specificity for a buyer to act on. This is the bar the queue above is chasing.

technicalAnswered

What token do I need to pay gas fees with when executing transactions on the Doma protocol — is it a native DOM token, or do you accept ETH or stablecoins?

What the pages say

Gas fees on Doma Chain are paid in ETH, the chain’s native token. The site does not mention a native DOM token for gas, and stablecoins like USDC are not accepted for gas (they are only for marketplace purchases). DNS record updates and nameserver rotations are exceptions because they use sponsored gas and do not require ETH.

Source: /faq.md, /agentic-commerce/doma-cli, /.well-known/skills/secondary-sales/SKILL.md, /.well-known/skills/secondary-sales/SKILL.md

confidence high · grounding synthesized · weight 0.95 · Answered

integrationAnswered

I'm building in Rust — does Doma provide official SDKs or client libraries beyond JavaScript/TypeScript, or do I need to generate bindings from your OpenAPI spec?

What the pages say

Doma only documents official JavaScript/TypeScript SDKs. The `@doma-protocol/orderbook-sdk` npm package and the `@doma-protocol/cli` TypeScript tool are the only client libraries mentioned. No Rust SDK or other non-JS/TS client libraries are referenced. However, Doma exposes several HTTP and GraphQL APIs, and the Orderbook API is documented with an OpenAPI 3.0 spec, which you could use to generate Rust bindings for marketplace operations. For other protocol interactions you would need to use the Smart Contracts API or Subgraph directly.

Source: /doma-marketplace, /agentic-commerce/doma-cli, /agentic-commerce/doma-cli.md, /.well-known/skills/secondary-sales/SKILL.md, /api-reference/orderbook-api.md, /building-on-doma

confidence high · grounding synthesized · weight 0.95 · Answered

integrationAnswered

Your DNS meets ENS page mentions programmable records — which specific DNS record types (A, AAAA, MX, TXT, etc.) can I actually set on-chain for my tokenized domain?

What the pages say

Doma’s Programmable DNS documentation states that on-chain domain capabilities include control over A records, CNAME records, MX records, TXT records, and other DNS configurations, plus NS and DS records under Records Update. The docs also explain that Programmable DNS lets users create the required DNS entries for ENS claims fully on-chain, enabling a seamless, programmable ENS claim flow without visiting a registrar.

Source: /programmable-dns, /programmable-dns.md

confidence high · grounding synthesized · weight 0.95 · Answered

integrationAnswered

Do I need to be an ICANN-accredited registrar to integrate with Doma's protocol, or can non-accredited domain resellers also use the registrar tools?

What the pages say

You must be an ICANN-accredited registrar to use Doma’s Registrar Modules (the registrar toolkit and integration APIs); they are explicitly restricted to “ICANN accredited registrars that have gone through Doma Certification.” Non-accredited domain resellers cannot use those registrar tools. However, non-accredited entities do have an alternative integration path: the Custodian Module provides Reseller APIs that enable non-ICANN-accredited entities to register and tokenize domains.

Source: /readme/core-modules, /readme/core-modules.md, /readme/core-modules.md

confidence high · grounding synthesized · weight 0.95 · Answered

securityAnswered

If there's a dispute over a high-value domain token transaction, which jurisdiction's laws govern the Terms of Service — and is arbitration mandatory or can I sue in court?

What the pages say

The Terms of Service are governed by the laws of the Cayman Islands, without regard to its conflict of law principles. Any dispute arising out of or relating to these Terms or the Services must be finally settled by mandatory binding arbitration administered by the International Chamber of Commerce in accordance with its arbitration rules; the arbitration shall take place in the Cayman Islands and the language shall be English. This means you cannot sue in court for disputes covered by these Terms.

Source: /terms

confidence high · grounding stated · weight 1.00 · Answered

Protocol plumbing · 63/10010 of 16 checks pass · each fix +6 protocol pts est.

The other half of the score: 16 checks for the files and headers agents look for. The 6 below are installs, not judgment calls, and most are an afternoon. Expand any for the snippet and the standard it follows. They sit after the queue because none of them changes what your pages say.

Markdown negotiationRendering+6 pts est.

StandardRFC 9110 + 7763IETF RFC

MCP cardInteraction+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardModel Context ProtocolCommunity spec

OpenAPI specInteraction+6 pts est.

StandardOpenAPI SpecIndustry standard

WebMCP widgetInteraction+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardW3C WebMCP draftW3C / WHATWG

Canonical URLsHygiene+6 pts est.
Install snippet
<link rel="canonical" href="https://doma.xyz/" />

StandardRFC 6596IETF RFC

Organization schemaIdentity+6 pts est.

Sitedex generates this file from your crawl. Grab it in Files from this audit below.

StandardSchema.org + JSON-LDIndustry standard

Already passing 10 of 16: robots.txt, sitemap.xml, llms.txt, AI crawler access, Content signal, Clean crawl, Server-rendered content, Meta descriptions, HTML lang attribute, Sitemap lastmod.

Ask this site’s index

Sitedex already serves doma.xyz as an MCP endpoint. Ask doma.xyz anything an AI agent might ask, and see what its index returns. (To score your own site, use the form below.)

Snippets & configs

For developers and the engineer-on-call: copy these into your tools or your site.

Files from this audit

Built from this crawl. Download or copy each, then install it at the path noted.

llms.txt

Built from this crawl. Install at /llms.txt so agents start here.

organization.json

Organization JSON-LD, pre-filled from this crawl. Wrap in a ld+json script.

server-card.json

MCP server card built from this crawl. Host at /.well-known/mcp/server-card.json.

webmcp.json

WebMCP discovery manifest built from this crawl. Host at /.well-known/webmcp.json.

MCP endpoint

https://mcp.sitedex.dev/s/doma-xyz/mcp

The URL anyone's agent points at. Read-only; safe to share.

Claude Code

claude mcp add doma --transport http https://mcp.sitedex.dev/s/doma-xyz/mcp

One command, then the agent has it.

Cursor / Continue

{
  "mcpServers": {
    "doma": {
      "url": "https://mcp.sitedex.dev/s/doma-xyz/mcp"
    }
  }
}

Drop into mcp.json.

WebMCP: two parts

WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.

1 · Widget script

<script async src="https://sitedex.dev/widget.js"></script>

Drop in <head>. In browsers with WebMCP, this script registers your site's tools with navigator.modelContext.registerTool().

2 · Discovery manifest

{
  "schema_version": "2026-04",
  "name": "Doma",
  "description": "Doma is a blockchain network for tokenizing and trading domain assets. WebMCP tools served by Sitedex.",
  "homepage": "https://doma.xyz",
  "documentation": "https://app.sitedex.dev/sites/doma.xyz",
  "source": "navigator.modelContext",
  "tools": [
    {
      "name": "search_site_content",
      "description": "Ask about this site in plain language and get the most relevant passages from its pages, each with the source URL and a relevance score. Searches the site's published text, not live inventory or accounts."
    },
    {
      "name": "get_site_info",
      "description": "This site's profile: name, description, category, who it is for, page count, and AI Visibility Score. Use it to learn what the site is before you search it."
    },
    {
      "name": "list_site_pages",
      "description": "The pages indexed on this site, with title, URL, and path. Use it to see what the site covers, or to find the path to pass to get_site_page."
    },
    {
      "name": "get_site_page",
      "description": "The full markdown of one page on this site, by path. Use it after search_site_content points you at a page and you want all of it."
    }
  ]
}

Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.

Your turn

See which of these questions your site goes silent on.

Free, about 5 minutes. We crawl your site, test it against the buyer questions your category asks, and name what’s vague, contradictory, or missing, plus the files AI agents look for.

ComingEmbeddable grade badgeScore history and deltasOpt-in public board