high high likelihood
R-001: Financial and marketplace economics are opaque
Valuation and public pricing are visible, but GMV, take rate, revenue, gross margin, burn, and cap table are not public.
Diligence request: Request audited statements, marketplace GMV/take-rate bridge, revenue by product, churn, cash runway, cap table, and financing terms.
high medium likelihood
R-002: Domain abuse, trademark, and ICANN compliance exposure
Registrar and marketplace operations face phishing, malware, brand-impersonation, takedown, refund, and trademark dispute risk.
Diligence request: Request ICANN compliance history, abuse-response metrics, UDRP/URS/litigation schedule, and registry agreements.
medium high likelihood
R-004: Competitive pressure from scaled registrars and aftermarket networks
GoDaddy, Namecheap, Sedo/Afternic and other registrars can compete on price, liquidity, brand trust, and distribution.
Diligence request: Request win/loss analysis, pricing elasticity, supplier/registry terms, and marketplace liquidity metrics.
medium medium likelihood
R-003: Strategic repositioning may pressure legacy Web3 identity economics
Current pages emphasize DNS registrar/domainers and AI domain tooling, requiring validation of revenue mix versus earlier blockchain-domain demand.
Diligence request: Request product revenue history, cohort retention by legacy/web3/DNS users, and roadmap investment plan.
medium medium likelihood
R-005: Payment, KYC, and crypto refund complexity
Terms reference KYC vendors, ACH/wire/crypto payouts, crypto refunds, and blockchain-fee caveats.
Diligence request: Review payment processor agreements, fraud losses, chargebacks, KYC procedures, and crypto treasury/refund controls.
medium medium likelihood
R-006: Developer/API reliability and security risk
API, MCP, AI assistant, and registrar automation create reliability/security obligations not testable from public pages.
Diligence request: Request architecture, uptime, incident history, penetration tests, API SLA metrics, and SOC reports.