Namecheap is suing their customers 🔗 **Source:** [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo&list=WL&index=4) > [!note]+ Document Notes > tags: [domains, registrars, namecheap, trademark, startup-risk, open-source-governance] > author: Theo Browne > source: YouTube (Theo - t3.gg) > reference: [https://www.youtube.com/watch?v=gPcB2VdzeKo] > date created: > > # 🏷️ Title: Namecheap is suing their customers > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Audit GoDaddy domain registrar risk profile for DevRel messaging — [Theo video](https://www.youtube.com/watch?v=gPcB2VdzeKo) #articleseed - [H3] Draft registrar selection guide for WordPress hosting partners — domain risk surface area #articleseed - [H5] Research Cloudflare/Vercel domain integration for contributor tooling — registrar alternatives #xref - [H7] Brief The WPOCC on SLAPP-style litigation patterns in tech — Scientology/Namecheap parallel #share - [H8] Evaluate DNS Simple SDK for WordPress ecosystem documentation — developer-first registrar #xref - [H10] Add domain registrar risk section to OSPO governance templates — registry vs registrar separation #addendum - [H12] Write article on domain infrastructure as single points of failure — XKCD dependency model #articleseed - [H14] Share Porkbun accountability example with WordPress community governance discussions — ownership culture #share ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Snigdha Sur's original X/Twitter thread](https://x.com/snaborsa) — primary account of events - [Garry Tan's response](https://x.com/garrytan/status/2015117068962849104) — YC president amplification - [DomainGang coverage](https://domaingang.com/domain-law/thejuggernaut-com-a-domain-name-caught-in-a-trademark-war/) — legal analysis of trademark dispute - [SpicyIP jurisdiction analysis](https://spicyip.com/2019/09/websites-the-virtual-juggernauts-continue-to-question-jurisdiction-and-enforcement-in-online-trademark-disputes.html) — Delhi High Court ruling context - [The Juggernaut](https://www.thejuggernaut.com/about) — company background - [Hacker News discussion](https://news.ycombinator.com/item?id=46746242) — community debate on both sides - [XKCD Dependency comic](https://xkcd.com/2347/) — referenced infrastructure fragility analogy ## 📝 Summary - Namecheap shut down thejuggernaut.com globally after an Indian trademark ruling by Juggernaut Books. Founder Snigdha Sur obtained a US temporary restraining order. Namecheap then counter-sued her personally, not her company InkMango. - This matters because domain registrars hold asymmetric power over businesses. A registrar can disable a domain "at any time for any reason" per ToS. Startups face existential risk from registrar disputes. - Key stakeholders include Snigdha Sur (founder, InkMango/The Juggernaut), Namecheap (registrar, $1.5B valuation), Juggernaut Books (Indian trademark holder), the Delhi High Court, and the Arizona state court. - Risks include cross-jurisdiction trademark enforcement colliding with US business operations, SLAPP-style personal litigation against founders, SEO destruction, investor confidence loss, and spam-list false flagging as a censorship vector. - Bottom line: founders should register domains with companies that make money elsewhere (Cloudflare, Vercel), care about public reputation, and admit mistakes. Margin-dependent registrars create perverse incentives. ## 📖 Main Content - Theo Browne presents the Namecheap vs. Snigdha Sur case as a cautionary tale about domain infrastructure fragility. Sur founded The Juggernaut, a subscription media company covering South Asian stories. Her company InkMango registered thejuggernaut.com via Namecheap. In 2019, Indian publisher Juggernaut Books filed a trademark claim in the Delhi High Court. The Indian court ruled the domain infringed on their mark within India. - Namecheap responded by suspending the domain globally, not just in India. Sur obtained a temporary restraining order from an Arizona court compelling Namecheap to restore the domain with geo-fencing for India. Namecheap counter-sued Sur personally rather than her company. Their ToS claims "broad discretion" to suspend domains "at any time for any reason." - Theo draws a parallel to the Church of Scientology's strategy against the IRS: filing thousands of individual lawsuits against employees to force capitulation through process burden rather than legal merit. The 1993 IRS settlement followed approximately 2,500 lawsuits. Personal lawsuits against founders serve a similar function — the legal process itself is the punishment. - The video also covers Theo's own experience: competitors false-flagged his domains to spam trackers (including Spamhaus), damaging SEO and causing European ISPs to block his CDN domain for UploadThing. This illustrates how third-party spam-reputation lists create additional fragility in the domain stack. - The domain ecosystem has multiple failure points: the registry (TLD operator), the registrar (reseller), governing bodies for ccTLDs, and spam-reputation aggregators. Any single layer can destroy a business unilaterally. - Theo recommends registrars that (1) make money from other products so domains aren't a profit center, (2) care about public reputation on social media, and (3) admit mistakes publicly. He recommends Vercel, Cloudflare, and DNS Simple. He warns against GoDaddy, Namecheap, and Tucows. He gives a conditional endorsement to Porkbun, citing their public accountability when they made errors. ### 🗒️ Notes #### ⏱️ [00:00:00](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=0) Domain registration pain points and personal experience - Theo recounts recurring domain issues including ccTLD surprise fees. - Country-code TLDs require renewal over a month before expiration or incur steep penalties. - Sets up the Snigdha Sur / Namecheap story as the worst case he has seen. #### ⏱️ [00:00:42](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=42) The Juggernaut domain shutdown — core facts - Snigdha Sur's domain thejuggernaut.com was taken offline by Namecheap. - Namecheap then sued her personally. - The Juggernaut is a startup telling South Asian stories; its business depends entirely on web presence. #### ⏱️ [00:01:45](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=105) Sponsor: Graptile AI code reviewer - Open-source projects receive 100% discount; startups receive 50% discount. - Example: PostHog bug caught by Graptile, NVIDIA repo review. #### ⏱️ [00:03:19](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=199) Reading Snigdha Sur's thread — timeline and court ruling - January 2025: Namecheap shut down the company's website globally. - Sur filed a temporary restraining order in Arizona. - Arizona court granted the TRO — domain belongs to Sur. #### ⏱️ [00:04:13](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=253) Business impact of domain loss - Lost paying subscribers during peak acquisition month. - Years of SEO destroyed. - Investors suspended conversations; one asked if the business had shut down. - Web presence vanished: articles, customer access, word-of-mouth growth all halted. #### ⏱️ [00:05:24](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=324) Theo's own domain false-flag experience - Competitors false-flagged T3 Chat domains to Spamhaus and other spam trackers. - T3 Chat placed on spam/scam filter; Google search rankings still damaged. - UploadThing CDN domain blocked by European ISPs after false flags. - Demonstrates how easy it is to weaponize spam-reputation systems. #### ⏱️ [00:07:00](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=420) Domain infrastructure stack as fragility model - Registry, registrar, TLD governing body, and spam lists each represent independent failure points. - References XKCD dependency comic — the spam/reputation layer is the thinnest. - Any single layer can break and destroy a business. #### ⏱️ [00:08:07](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=487) First Amendment and censorship concerns - Shutting down a news organization raises free speech issues. - Domain weaponization functions as censorship. - Theo recounts his own experience: criticized an open-source library's governance, faced retaliation via domain false-flagging. #### ⏱️ [00:09:17](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=557) Investor impact and personal lawsuit details - Namecheap claims the domain was registered in Sur's personal name, not the company. - They sue her personally, not her LLC — a deliberate strategy. - Parallel drawn to Church of Scientology suing individual IRS employees (approx. 2,500 lawsuits leading to 1993 settlement). #### ⏱️ [00:11:52](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=712) Namecheap's ToS and counter-claim details - Namecheap ToS claims "broad discretion" to shut down domains "at any time for any reason." - After losing the TRO, Namecheap counter-sued Sur and sought legal fees. - Former CEO Richard Kirkendall proposed geo-fencing India as a workaround. - Gary Tan (YC president) publicly challenged Namecheap's position. #### ⏱️ [00:12:38](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=758) The Juggernaut Books trademark dispute origin - Juggernaut Books: Indian publisher with registered "JUGGERNAUT" trademark in publishing/media. - The Juggernaut: US-based South Asian news/stories site (InkMango, Inc.). - Delhi High Court ruled in 2019 that the domain conflicted with Indian trademark rights. - US courts found the entities sufficiently distinct under American trademark law. #### ⏱️ [00:14:07](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=847) Arizona court order language - Namecheap enjoined from "preventing or frustrating" Sur's use of the domain. - Only restriction: geo-fence India access. - Namecheap also enjoined from "indirectly causing the expiration" of the domain. #### ⏱️ [00:16:16](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=976) Namecheap legal threat against going public - Namecheap's legal firm threatened Sur and her attorneys for stating intent to "go to Twitter." - Letter characterized public speech about the case as "improper, unprotected" and threatened civil liability. - Former CEO Kirkendall posted legal documents to Google Drive that Theo argues undermine Namecheap's position. #### ⏱️ [00:18:28](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1108) Registrar selection framework - Avoid registrars that make majority income from domain margins. - GoDaddy and Namecheap criticized as margin-dependent. - Gas station analogy: registrars are resellers from the same 3–4 registries. Low-margin businesses resort to aggressive upselling and fee structures. #### ⏱️ [00:20:20](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1220) Recommended registrars — Vercel, Cloudflare - Both make money from other products (hosting, CDN, edge compute). - Vercel absorbed thousands of dollars in fees for four users affected by a .gg registry issue. - Cloudflare offers .AI and other TLDs but not all ccTLDs. - Warns against ccTLDs broadly — "evil and you should avoid them at all costs." #### ⏱️ [00:22:06](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1326) Reputation sensitivity as a customer lever - Companies that care about Twitter/social reputation give customers recourse. - Example: a developer with under 50 followers caused a major Vercel incident via a viral post about a $400 billing error. Vercel CEO responded personally; Astro and Vercel both shipped patches. - Reputation sensitivity functions as accountability infrastructure. #### ⏱️ [00:24:07](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1447) DNS Simple recommendation - Small Florida-based team; husband-and-wife founders. - Higher margins offset by developer-first SDK and control plane. - All support staff are engineers. - Used by the Linux Foundation. #### ⏱️ [00:25:55](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1555) Porkbun conditional endorsement - User Joshua reported $15K in domains past expiration despite auto-renew settings. - Porkbun publicly acknowledged the error and committed to fixes. - Ownership of mistakes is the key differentiator — Namecheap has not demonstrated this. #### ⏱️ [00:26:19](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1579) GoDaddy domain front-running allegation - A user reported that a domain they searched on GoDaddy was purchased and resold to them during the search session. - Theo calls this a "classic rugpull" that should be illegal. #### ⏱️ [00:28:28](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1708) Registry vs registrar distinction and Porkbun accountability - Registry suspended a domain; Porkbun locked the entire account — a cascading failure. - Porkbun publicly apologized and committed to preventing recurrence. - Theo's criteria for trustworthy registrars: (1) money made elsewhere, (2) reputation-sensitive, (3) admits mistakes. - GoDaddy, Tucows, and Namecheap fail these criteria. ## 📚 References - [Theo - t3.gg YouTube](https://www.youtube.com/@t3dotgg) — source channel - [Snigdha Sur](https://www.snigdhasur.com/) — founder, The Juggernaut / InkMango - [The Juggernaut](https://www.thejuggernaut.com/about) — media company - [DomainGang: TheJuggernaut.com trademark war](https://domaingang.com/domain-law/thejuggernaut-com-a-domain-name-caught-in-a-trademark-war/) - [SpicyIP: Jurisdiction and enforcement analysis (2019)](https://spicyip.com/2019/09/websites-the-virtual-juggernauts-continue-to-question-jurisdiction-and-enforcement-in-online-trademark-disputes.html) - [Hacker News discussion](https://news.ycombinator.com/item?id=46746242) - [Vercel Domains](https://vercel.com/domains) - [Cloudflare Registrar](https://www.cloudflare.com/products/registrar/) - [DNS Simple](https://dnsimple.com/) - [Porkbun](https://porkbun.com/) - [XKCD 2347: Dependency](https://xkcd.com/2347/) - [Church of Scientology IRS settlement (1993)](https://en.wikipedia.org/wiki/Tax_status_of_Scientology_in_the_United_States) ## 🗣️ Paraphrase - Domain registration carries hidden systemic risk. A registrar, registry, TLD governing body, or spam-reputation list can each independently destroy a business's web presence. Founder Snigdha Sur experienced this when Namecheap suspended her domain globally based on an Indian trademark ruling that only applied in India. - After a US court ruled in Sur's favor, Namecheap counter-sued her personally — not her company — echoing SLAPP-style litigation designed to exhaust opponents through process costs. Namecheap's legal team also threatened Sur's attorneys for indicating she would discuss the case publicly. - The recommended defense strategy is structural: register domains with companies that don't depend on domain margins for revenue, that respond to public accountability pressure, and that own their mistakes. Vercel, Cloudflare, and DNS Simple meet these criteria. Porkbun earns a conditional pass for public error accountability. GoDaddy and Namecheap fail on multiple criteria. ## 📰 Newsletter **🌐 Your Domain Is Not as Safe as You Think** Theo Browne just dropped a deep dive into how Namecheap suspended a YC-backed startup's domain over an Indian trademark dispute — then personally sued the founder after she won a US court order to get it back. The takeaway for WordPress builders: your domain is a single point of failure with multiple parties that can break it. Registrar ToS clauses claiming "any time, any reason" shutdown rights should concern anyone running a business on the web. **What to do:** Consider registering domains with providers that make money elsewhere — Vercel and Cloudflare both offer at-cost domain registration. DNS Simple offers a developer-first SDK approach. And avoid ccTLDs (.gg, .io, .co) unless you understand the governing body's rules. **Worth watching:** The full video covers spam-list false flagging as a censorship tool, the Church of Scientology's IRS litigation playbook, and why "admitting mistakes" is the most important trait in a registrar. 📺 [Watch the full breakdown](https://www.youtube.com/watch?v=gPcB2VdzeKo) ## ✅ Action Items #### DevRel - Developer advocacy: Create a "Domain Risk for Developers" talk or blog post covering registry/registrar separation, spam-list false flagging, and registrar selection criteria. Cite this case as a real-world example. - Education: Develop a workshop module on DNS infrastructure resilience for WordPress developers. Include registrar comparison matrix. - Developer experience: Document domain configuration best practices for WordPress hosting. Cover geo-fencing, DNSSEC, and registrar transfer procedures. - Developer marketing: Consider content series on "infrastructure you don't think about" — domains, SSL, spam lists. This video demonstrates strong audience engagement on the topic. - Community management: Monitor for domain-related censorship attempts in open-source communities. The false-flagging vector Theo describes applies to WordPress projects. #### OSPO - Policy & Governance: Add domain registrar selection criteria to OSPO governance templates. Include registry vs. registrar distinction. Require documented domain ownership separate from individual contributors. - License Compliance: Note that trademark disputes can cascade into domain seizures even across jurisdictions. Include cross-border trademark risk in compliance training. - Security Management: Domain infrastructure is an attack surface. False-flagging to spam lists is a demonstrated censorship vector. Include domain reputation monitoring in security posture. - Community Engagement: Share this case study with upstream communities as a governance discussion starter. The registrar power asymmetry parallels other infrastructure concentration risks. - Strategic Alignment: Domain risk should appear in business continuity planning. Recommend multi-registrar strategies for critical domains. #### Community - Contributors: Include domain setup guidance in contributor onboarding for projects that require custom domains (WordCamps, community sites). - Ecosystem: The registry/registrar/spam-list stack is a shared dependency. Cross-project coordination on domain resilience would benefit the broader WordPress ecosystem. #### WordPress - Core: No direct action, but the web platform depends on functional domain infrastructure. Worth monitoring. - Community: Share domain risk awareness at WordCamps. The false-flag censorship vector is relevant to community organizers. - Hosting: Cross-host checklists should include registrar selection guidance. GoDaddy's own domain front-running allegation is relevant here. - Meta: .org domain infrastructure should have documented registrar risk mitigation. #### The WPOCC - Programs: Consider a microgrant or resource guide for startups navigating domain disputes. This case demonstrates how domain issues disproportionately affect small/early-stage companies. - Projects: Governance clinics could include domain ownership best practices — register under company entities, not personal names. - Funding experiments: Domain resilience infrastructure (multi-registrar, DNSSEC, domain monitoring) could be a fundable community resource. ### FAIR - Technical independence: Domain registrar concentration is an anti-pattern. FAIR principles support multi-registrar strategies and documented ownership provenance. - Policies and covenants: Registrar ToS clauses claiming "any time, any reason" shutdown rights are incompatible with sustainable open-source infrastructure. Document this as a governance risk. - Productized governance artifacts: Create a domain registrar evaluation scorecard based on Theo's three criteria: revenue diversification, reputation sensitivity, and error accountability. ## 🧪 Hypotheses - **H1:** Startups that register domains under personal names rather than corporate entities face higher risk of personal litigation in domain disputes. - **H2:** Domain registrars with revenue concentrated in domain margins are more likely to enforce third-party takedown requests without due process than registrars with diversified revenue. - **H3:** Cross-jurisdiction trademark enforcement via domain registrars creates a de facto global injunction that exceeds the issuing court's intended scope. - **H4:** False-flagging domains to spam-reputation lists is an unregulated censorship vector with no meaningful recourse for affected parties. - **H5:** Companies that publicly acknowledge errors in domain management have lower customer churn than those that respond with litigation. - **H6:** ccTLD domains carry systematically higher operational risk than gTLD domains due to less predictable governing-body behavior. ### 📊 Methodology - **H1:** Analyze UDRP and court filings for domain disputes. Compare outcomes for personal vs. corporate registrations. Sample: WIPO UDRP database. - **H2:** Survey registrar ToS and correlate with takedown compliance rates. Use ICANN transparency reports and registrar revenue disclosures. - **H3:** Legal case analysis: compare the scope of court orders with the actual enforcement actions by registrars. Sample: cross-border trademark cases involving domain suspensions. - **H4:** Track false-flag reports to Spamhaus, SURBL, and similar lists. Measure time-to-resolution and downstream ISP propagation. Interview affected parties. - **H5:** Customer satisfaction surveys (Trustpilot, G2) correlated with public incident response patterns. Longitudinal analysis. - **H6:** Compare domain incident rates (suspension, expiration disputes, fee surprises) across ccTLDs vs. gTLDs using registrar support ticket data. ### ❓ Questions - What legal frameworks exist to prevent SLAPP-style domain litigation against individual founders? - Should ICANN establish mandatory due process requirements before registrars can suspend domains based on foreign court orders? - How can open-source projects protect their domain infrastructure from false-flag spam-list attacks? - What insurance products exist for domain seizure risk, and are they accessible to early-stage startups? - Does GoDaddy's alleged domain front-running constitute fraud, and has any regulatory body investigated it? - How does the Delhi High Court's "purposeful availment" test interact with globally accessible websites? ### 🔮 Future Research - Mapping the domain infrastructure dependency graph for the top 10,000 WordPress sites — identifying single-point-of-failure registrar concentration. - Developing an open-source domain health monitoring tool that tracks spam-list status, DNSSEC validity, and registrar ToS changes. - Comparative legal analysis of registrar liability across US, EU, and Indian jurisdictions for domain disputes. - Quantifying SEO recovery timelines after domain suspension events — this case and Theo's own experience suggest permanent damage. - Studying the effectiveness of social media pressure as a customer recourse mechanism across different registrar types. ### 💡 Implications - **Practice:** Founders should register domains under corporate entities, use multi-registrar strategies for critical domains, and prefer registrars with diversified revenue models. - **Policy:** Registrar ToS granting "any time, any reason" suspension power should face regulatory scrutiny. ICANN could mandate minimum due process standards. - **Security:** Domain reputation monitoring belongs in security operations. False-flag attacks on spam lists are a demonstrated threat. - **Education:** Developer education should cover DNS infrastructure as a risk surface, not just a configuration task. - **Funding:** Domain resilience tools and legal defense funds for open-source projects represent an underserved funding category. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade Level ~10 (conversational YouTube transcript with technical and legal terms). Accessible to a general developer audience. #### 👀 Visual learners - Present: None — audio/video transcript only. - Improve: Add a diagram of the domain infrastructure stack (registry → registrar → DNS → spam lists → ISPs). Add a timeline graphic for the Sur/Namecheap dispute. Before/after screenshots of domain resolution failures. #### 🔊 Aural learners - Present: Full video available at source URL. Conversational delivery with narrative structure. - Improve: Extract a 3-minute audio summary of the three registrar selection criteria. Create a podcast-format discussion of the legal issues. #### 🗣️ Verbal learners - Present: Strong narrative with analogies (gas station, XKCD dependency comic, Scientology IRS comparison). Terms explained inline. - Improve: Add a glossary defining registry, registrar, TLD, ccTLD, WHOIS, UDRP, geo-fencing, SLAPP. Include a comparison table of registrar types. #### 🧩 Kinesthetic learners - Present: Implicit call to action (switch registrars). - Improve: Step-by-step domain transfer checklist. Lab exercise: check your domain's spam-list status using MXToolbox. Registrar comparison worksheet. #### 🧠 Logical learners - Present: Clear causal chain (trademark suit → registrar action → business damage → counter-litigation). XKCD dependency model as systems thinking framework. - Improve: Decision tree for registrar selection. Cost-benefit analysis of multi-registrar strategies. Risk matrix for domain infrastructure. #### 🧑‍🤝‍🧑 Social learners - Present: YouTube live chat interaction. References to community figures (Gary Tan, former Namecheap CEO). - Improve: Discussion guide for meetups on domain risk. Peer review exercise: audit each other's domain registrations. #### 🧘‍♀️ Solitary learners - Present: Thread-style narrative invites individual reflection. - Improve: Self-assessment checklist: "Is your domain at risk?" Journal prompt: "What would happen to your business if your domain went down tomorrow?" #### 🌿 Naturalistic learners - Present: Ecosystem thinking — the domain stack as a fragile ecosystem with predators and parasites. - Improve: Lifecycle diagram of a domain from registration to renewal to dispute. Analogy to monoculture farming (single-registrar risk). ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Transcript is plain text — fully accessible to screen readers. - Improve: If published as HTML, add proper heading hierarchy. Video source lacks captions authored by creator (auto-generated via Merlin AI). #### Keyboard navigation - Present: YouTube player supports keyboard navigation. - Improve: Ensure any published article version has skip links and logical heading order. #### Contrast and readability - Present: Text transcript has no contrast issues. - Improve: Any visual summaries should meet 4.5:1 contrast ratio. Use sufficient line height for readability. #### Text resizing and reflow - Present: N/A for transcript. - Improve: Published versions should reflow at 200% zoom without horizontal scrolling. #### Media and captions - Present: Auto-generated captions via Merlin AI. Transcript available. - Improve: Human-reviewed captions for accuracy (the transcript contains multiple errors: "NameCheep" for "Namecheap," "Verscell" for "Vercel," etc.). Provide downloadable transcript. #### Forms and interactions - Present: N/A. - Improve: N/A. #### Standards reference - WCAG 2.2 AA: 1.2.2 (Captions) — auto-generated captions need human review. 1.2.3 (Audio Description) — no audio description of on-screen content. 2.4.1 (Bypass Blocks) — N/A for transcript. ### 🌍 DEIB Assessment #### Cultural breadth - Present: The case centers a South Asian founder and an Indian trademark dispute. Theo acknowledges the gendered dynamics ("some amount of it's just sexism"). The Juggernaut itself serves the South Asian diaspora. - Improve: Explore how cross-jurisdiction domain disputes disproportionately affect founders from countries with aggressive trademark enforcement. Include perspectives from Indian tech/legal community. #### Inclusive language - Present: Casual YouTube tone with profanity. Generally inclusive terminology. - Improve: The transcript contains several instances of strong language that would need editing for professional republication. Define technical terms (registry, registrar, ccTLD) for non-developer audiences. #### Neurodiversity support - Present: Clear narrative structure with timestamps. One topic per segment. - Improve: Add section summaries. Use consistent heading patterns. Reduce tangential asides for written versions. #### Representation - Present: Centers a woman of color (Snigdha Sur) as the affected party. Acknowledges sexism in community response. References Gary Tan (YC, Asian American). References multiple companies of varying sizes. - Improve: Include perspectives from domain law practitioners and registrar employees. Acknowledge the Indian court's perspective more fully. #### Psychological safety - Present: Theo is openly biased ("I want to watch them burn") but flags this upfront. - Improve: When resharing, add content warning for SLAPP-style litigation patterns that may be triggering for founders who have experienced similar disputes. ### ✅ Logical Validity #### Strong reasoning - **Causal reasoning (strong):** [00:04:13–00:05:24] — The chain from domain suspension → SEO loss → subscriber loss → investor suspension is well-evidenced by Sur's account and Theo's parallel experience. The business impact of domain loss is concrete and measurable. - **Analogical reasoning (strong):** [00:10:30–00:11:50] — The Church of Scientology / IRS analogy effectively illustrates SLAPP-style litigation strategy. The mechanism (process-as-punishment) maps cleanly. - **Inductive reasoning (moderate):** [00:18:28–00:20:20] — The gas station analogy for registrar margins is useful but oversimplifies. Some registrars (like DNS Simple) operate on margins while providing good service through differentiation. #### Fallacies - **Hasty generalization** [00:18:46]: "I would not trust GoDaddy particularly more than I would trust Namecheap" — groups all margin-dependent registrars as equivalently untrustworthy without evidence specific to GoDaddy's dispute handling. GoDaddy's scale and public company status create different incentive structures. *Fix: specify which GoDaddy behaviors parallel Namecheap's.* - **Anecdotal evidence** [00:22:22–00:23:06]: The Vercel billing incident (under-50-follower developer) is presented as evidence that reputation pressure works for everyone, but this is a single case. Survivorship bias — we don't hear about complaints that went nowhere. *Fix: acknowledge this is illustrative, not systematic.* - **False dichotomy** [00:21:48–00:22:00]: "I would argue if they're not offered on Cloudflare or Vercel, you probably shouldn't buy them" — reduces registrar choice to two providers. DNS Simple, Porkbun, and Gandi also meet his stated criteria. *Fix: frame as "prefer" rather than "shouldn't buy."* #### Tone of voice - Passionate and confrontational. Theo uses profanity, personal anecdotes, and emotional language ("horrifying," "insanity," "I want to watch them burn"). This serves engagement but may undermine credibility with risk-averse audiences. The tone shifts to more measured analysis when discussing the court documents and registrar recommendations. ### 🛡️ DARVO Analysis - **Deny:** Namecheap's former CEO Richard Kirkendall characterized Sur's public account as "public lies and manipulation of the truth." This denies the substance of her claims without addressing the Arizona court's ruling in her favor. - **Attack:** Namecheap's legal firm sent a letter threatening Sur and her attorneys with "civil liability" and "ethical consequences" for stating an intention to discuss the case publicly. This reframes protected speech as a threat, attacking the accuser's right to speak. - **Reverse victim/offender:** Namecheap counter-sued Sur personally after losing the TRO. The legal letter frames Sur's intent to speak publicly as the aggressive act, positioning Namecheap as the threatened party despite being the entity that suspended her domain. Kirkendall's statement "Things aren't going to get any easier" functions as an implicit threat while maintaining the posture of the aggrieved party. - **Emotional cues:** Kirkendall's tone is dismissive and threatening. The legal letter uses formal language to amplify intimidation. The gap between Namecheap's $1.5B valuation and Sur's pre-Series A resources makes the power asymmetry explicit. - **Related fallacies:** Appeal to authority (ToS as justification), tu quoque (claiming Sur is the one being aggressive), and red herring (personal registration vs. company registration as grounds for personal lawsuit). ## 🎯 Conclusion - Domain infrastructure is a business-critical dependency with multiple unregulated failure points. Registrars, registries, TLD governing bodies, and spam-reputation lists can each independently destroy a company's web presence. - Founders should register domains under corporate entities, prefer registrars with diversified revenue, prioritize registrars that demonstrate public accountability, and monitor domain reputation proactively. - The Namecheap/Sur case is a template for how SLAPP-style litigation and ToS overreach can weaponize infrastructure against small companies. The WordPress and open-source communities should treat domain resilience as a governance concern, not just a technical one. - For OSPO and DevRel: domain risk belongs in business continuity planning, governance templates, and developer education materials. The parallels to open-source governance (concentrated power, lack of accountability, process-as-punishment) make this a valuable case study. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Domain registrars hold asymmetric shutdown power over businesses > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "Namecheap also claims that it had broad discretion to shut down your domain at any time for any reason." ToS clauses granting unilateral shutdown power create existential risk for domain-dependent businesses. No due process required. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=712) #articleseed #aphorisms ID:rw_[MISSING] ### [H2] Cross-jurisdiction trademark enforcement exceeds issuing court scope > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "The India courts firmly stated that this domain cannot be owned by her." Namecheap enforced an Indian ruling globally despite a US court ordering restoration. Registrar compliance with foreign courts creates de facto global injunctions. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=758) #articleseed #xref ID:rw_[MISSING] ### [H3] Personal lawsuits against founders serve as SLAPP-style intimidation > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "They are suing her personally." Namecheap sued Sur individually, not her LLC. Process cost itself is the weapon. Parallels Church of Scientology IRS strategy. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=557) #articleseed #xref ID:rw_[MISSING] ### [H4] Spam-list false flagging functions as unregulated censorship > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "People were falsely flagging our domains to these different spam collectors." Third parties can weaponize spam-reputation systems to block competitors. No verification required. ISP propagation extends damage beyond initial listing. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=324) #articleseed ID:rw_[MISSING] ### [H5] Revenue-diversified registrars align incentives with customers > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "Every domain I've personally registered in the last three years has been either on Vercel or Cloudflare." Registrars that profit elsewhere (hosting, CDN) don't squeeze domain margins. Vercel absorbed thousands in fees for four affected users. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1220) #xref ID:rw_[MISSING] ### [H6] Public accountability pressure creates customer recourse > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "A lot of actual things changed as a result of this random developer complaining on Twitter." Social media reputation sensitivity functions as informal accountability infrastructure. Even low-follower accounts can drive systemic changes. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1326) #aphorisms ID:rw_[MISSING] ### [H7] Admitting mistakes predicts registrar trustworthiness > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "If they can't admit that they screwed up, the likelihood that they fix the thing is much lower." Error accountability is the strongest signal of registrar reliability. Porkbun demonstrated this; Namecheap did not. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1708) #aphorisms #articleseed ID:rw_[MISSING] ### [H8] Domain infrastructure has multiple independent failure points > [!quote] [Namecheap is suing their customers](https://www.youtube.com/watch?v=gPcB2VdzeKo) by [[Theo Browne]] via [[YouTube]]. Published 2026-02-09. Accessed . > "The fact that there are so many layers here where any one of them can destroy your whole business is horrifying." Registry, registrar, TLD governing body, and spam-reputation lists each represent independent single points of failure. XKCD dependency model applies. [view highlight](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=420) #articleseed #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] Registrar ToS clauses grant unilateral domain shutdown power - Namecheap ToS claims "at any time for any reason" shutdown discretion. Arizona court pushed back. - [00:11:52](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=712) - Links: [[Domain-Risk-Surface-Area]] [[Registrar-Selection-Framework]] [[ToS-Power-Asymmetry]] #### [Z2] Personal lawsuits weaponize legal process against resource-constrained founders - Namecheap ($1.5B) sued Sur personally (pre-Series A). Parallels Scientology IRS strategy (~2,500 suits, 1993 settlement). - [00:09:17](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=557) - Links: [[SLAPP-Litigation]] [[Founder-Legal-Risk]] [[Power-Asymmetry-in-Tech]] #### [Z3] Spam-list false flagging operates as unregulated censorship infrastructure - No verification for spam-list submissions. ISP propagation extends damage. Theo's domains false-flagged by critics; Spamhaus listed as "phishing." - [00:05:24](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=324) - Links: [[Domain-Reputation-Systems]] [[Censorship-Vectors]] [[Open-Source-Governance-Retaliation]] #### [Z4] Revenue diversification aligns registrar incentives with customer interests - Gas station analogy: margin-dependent registrars resort to aggressive fee structures. Vercel/Cloudflare domains are loss leaders. - [00:18:28](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1108) - Links: [[Registrar-Selection-Framework]] [[Business-Model-as-Incentive]] [[Platform-Lock-in]] #### [Z5] Error accountability predicts service provider trustworthiness - Porkbun: public apology + fix commitment. Namecheap: denial + counter-litigation. Theo's strongest recommendation signal. - [00:28:28](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1708) - Links: [[Accountability-Culture]] [[Governance-Signals]] [[Trust-Frameworks]] #### [Z6] Cross-jurisdiction trademark enforcement creates de facto global injunctions - Delhi court order → Namecheap global suspension → Arizona court reversal. Registrar compliance with foreign courts exceeds original ruling scope. - [00:12:38](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=758) - Links: [[Trademark-Jurisdiction]] [[Domain-Governance]] [[Cross-Border-Enforcement]] #### [Z7] Social media reputation sensitivity creates informal accountability infrastructure - Developer with <50 followers caused major Vercel incident via viral complaint. CEO and engineers responded; patches shipped. - [00:22:06](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1326) - Links: [[Reputation-Driven-Accountability]] [[Customer-Leverage]] [[Platform-Governance]] #### [Z8] Domain infrastructure dependency stack mirrors XKCD 2347 - Registry → registrar → DNS → spam lists → ISPs. Each layer is an independent failure point. Spam lists are the thinnest dependency. - [00:07:00](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=420) - Links: [[Infrastructure-Fragility]] [[Dependency-Models]] [[Single-Points-of-Failure]] #### [Z9] ccTLD domains carry systematically higher operational risk - .gg renewal required >1 month before expiration. Registry governing bodies have unpredictable rules. Theo: "evil and you should avoid them." - [00:00:00](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=0) and [00:22:00](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1320) - Links: [[ccTLD-Risk]] [[Domain-Risk-Surface-Area]] [[Registrar-Selection-Framework]] #### [Z10] Threatening public speech about disputes reveals institutional defensiveness - Namecheap legal team characterized Sur's stated intent to tweet as "improper, unprotected" and threatened civil liability for her and her attorneys. - [00:16:16](https://www.youtube.com/watch?v=gPcB2VdzeKo&t=976) - Links: [[SLAPP-Litigation]] [[DARVO-Pattern]] [[Free-Speech-in-Tech-Disputes]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Research Arizona anti-SLAPP statute applicability to domain registrar disputes — https://www.youtube.com/watch?v=gPcB2VdzeKo #fleeting #inbox - [F2] Check GoDaddy domain front-running allegations for DevRel messaging risk — https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1579 #fleeting #inbox - [F3] Add Spamhaus false-flag monitoring to OSPO security checklist — https://www.youtube.com/watch?v=gPcB2VdzeKo&t=324 #fleeting #inbox - [F4] Draft "Domain Risk for WordPress Builders" talk proposal for WordCamp — https://www.youtube.com/watch?v=gPcB2VdzeKo #fleeting #inbox - [F5] Evaluate DNS Simple SDK for WordPress plugin scaffolding — https://dnsimple.com/ #fleeting #inbox - [F6] File FAIR governance artifact: domain registrar evaluation scorecard — https://www.youtube.com/watch?v=gPcB2VdzeKo&t=1708 #fleeting #inbox --- ## 🏷️ Tag Coverage #articleseed: 6 • #xref: 4 • #share: 2 • #aphorisms: 3 • #addendum: 1 • #bmf: 0 --- <!-- deep-read:sections end --> ## 📺 Video  --- # 📝 Full Notes (Deep-Read Analysis) # 🏷️ Title: Namecheap is suing their customers ## 🧰 Action Inbox - [H1] Choose registrars that make money elsewhere, not just domain margins — avoid GoDaddy/Namecheap #domains - [H2] Use services sensitive to Twitter reputation for leverage when problems arise — Vercel/Cloudflare #strategy - [H3] Avoid country code TLDs due to unpredictable rules and governance issues — stick to .com/.org #risk-management ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Theo's Channel](https://www.youtube.com/@t3dotgg) - [Grapile AI Code Review](https://graptile.com) ## 📝 Summary - Namecheap shut down startup founder Sanga's domain (thejuggernaut.com) due to an Indian trademark dispute, then sued her personally when she obtained a US court order to restore it - US court ruled in her favor with temporary restraining order, but Namecheap countersued and threatened legal fees despite losing - Demonstrates how domain vulnerabilities can destroy businesses through multiple attack vectors: registrars, registries, spam lists, and bad actors - Recommends using registrars that make money elsewhere (Vercel, Cloudflare) and are reputation-sensitive rather than margin-focused domain sellers - Highlights systemic risks in domain infrastructure that can enable censorship and business destruction ## 📖 Main Content The case involves The Juggernaut, a startup focused on South Asian stories, whose domain was suspended by Namecheap due to a trademark dispute with Juggernaut Books in India. Despite a US court ruling that Namecheap must restore the domain (with geo-blocking for India), the company countersued the founder personally and threatened additional legal fees. This exposes critical vulnerabilities in domain infrastructure. Multiple layers can fail: registrars (companies you buy from), registries (who control TLDs), governing bodies for country codes, and spam reputation services. Each represents a single point of failure that can destroy businesses overnight. The domain ecosystem resembles the XKCD dependency comic - everything relies on increasingly fragile infrastructure. When Theo's own domains were false-flagged as spam, it damaged SEO rankings and blocked European users from accessing UploadThing assets, demonstrating how easy it is to weaponize these systems. Namecheap's behavior mirrors tactics used by organizations like Scientology, who overwhelmed the IRS with personal lawsuits against individual employees until the agency granted tax-exempt status in 1993. Suing individuals rather than companies creates disproportionate pressure and distraction. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/gPcB2VdzeKo?t=0) — [H1] Domain vulnerability introduction - Key idea: Multiple domain failures from skill issues and external factors beyond control - Evidence: "domains get taken from me for reasons that I had no control or oversight over just to be held ransom for thousands of dollars" #### ⏱️ [02:15](https://youtu.be/gPcB2VdzeKo?t=135) — [H2] Sanga's case overview - Key idea: Namecheap sued their own customer personally after losing in court - Evidence: "NameCheep sued her personally. I've never seen anything quite like this" #### ⏱️ [04:30](https://youtu.be/gPcB2VdzeKo?t=270) — [H2] Business impact of domain loss - Key idea: Website unavailability destroys startup momentum and investor relations - Evidence: "One investor even messaged me on LinkedIn asking if I had shut down my business" #### ⏱️ [06:45](https://youtu.be/gPcB2VdzeKo?t=405) — [H3] SEO and reputation damage - Key idea: False spam flagging causes lasting damage to search rankings and accessibility - Evidence: "T3 Chat does not place properly in Google search results, primarily because we were incorrectly placed on a filter for spam and scam sites" #### ⏱️ [09:20](https://youtu.be/gPcB2VdzeKo?t=560) — [H2] Multiple failure points in domain infrastructure - Key idea: Registry, registrar, governing bodies, and spam lists all represent single points of failure - Evidence: "any one of them deciding they don't like you or failing you can destroy your whole business is horrifying" #### ⏱️ [12:10](https://youtu.be/gPcB2VdzeKo?t=730) — [H1] First Amendment and censorship concerns - Key idea: Domain takedowns can be weaponized for censorship of legitimate speech - Evidence: "People were unhappy about my takes around a specific open source library's governance and decided that I should not be allowed to run a business" #### ⏱️ [15:45](https://youtu.be/gPcB2VdzeKo?t=945) — [H2] Court ruling details - Key idea: US court specifically ordered Namecheap to restore domain with India geo-blocking only - Evidence: "enjoined from preventing or frustrating plaintiffs use of its registered domain, provided that the primary domain is geo-fenced to prevent access from users in India" #### ⏱️ [18:30](https://youtu.be/gPcB2VdzeKo?t=1110) — [H1] Scientology lawsuit parallel - Key idea: Personal lawsuits against individuals mirrors cult tactics to overwhelm opposition - Evidence: "Church of Scientology would personally reach out to people that were working for the IRS and sue them as individuals" #### ⏱️ [21:15](https://youtu.be/gPcB2VdzeKo?t=1275) — [H3] Legal threats for social media posts - Key idea: Namecheap threatened additional lawsuits if founder discussed case publicly - Evidence: "If you actually go to Twitter like you said you will, we will sue you for threatening us" #### ⏱️ [24:00](https://youtu.be/gPcB2VdzeKo?t=1440) — [H1] Registrar business model analysis - Key idea: Companies making money primarily from domain margins engage in predatory practices - Evidence: "any business that makes the majority of their income through fees and margins on domains is probably not the best place to register your domains" #### ⏱️ [26:45](https://youtu.be/gPcB2VdzeKo?t=1605) — [H1] Recommended registrar criteria - Key idea: Choose registrars that make money elsewhere and care about Twitter reputation - Evidence: "Vercel loses money because they've been too generous about weird disputes... they refunded all four of us those fees" #### ⏱️ [29:30](https://youtu.be/gPcB2VdzeKo?t=1770) — [H2] Twitter reputation as customer leverage - Key idea: Social media sensitivity provides recourse when normal support fails - Evidence: "random developer with under 50 followers... caused one of the most hellish days in the history of Vercel... got refunded, got personal support from the CEO" #### ⏱️ [32:20](https://youtu.be/gPcB2VdzeKo?t=1940) — [H3] Domain registrar recommendations - Key idea: Vercel, Cloudflare, DNSimple, and Porkbun offer better service models - Evidence: "Every domain I've personally registered in the last three years has been either on Vercel domains or Cloudflare's domains" #### ⏱️ [35:10](https://youtu.be/gPcB2VdzeKo?t=2110) — [H2] Porkbun accountability example - Key idea: Good registrars admit mistakes and take ownership of problems - Evidence: "We're sorry that we lost your trust... we screwed this up... what happened will not be able to happen again" ## 📚 References - [Grapile AI Code Review](https://graptile.com) - [DNSimple](https://dnsimple.com) - [Scientology IRS Settlement 1993](https://en.wikipedia.org/wiki/Tax_status_of_Scientology_in_the_United_States) ## 🗣️ Paraphrase - Domain infrastructure has multiple critical failure points that can destroy businesses overnight, including registrars, registries, spam reputation services, and bad actors filing false reports - Namecheap demonstrated predatory behavior by personally suing a customer who successfully obtained a court order against them, using legal harassment tactics similar to those employed by cults - Businesses should choose domain registrars that make money from other services rather than domain margins, and prioritize companies that are sensitive to public reputation for leverage when problems arise ## 📰 Newsletter **Domain Security: A Critical Blind Spot for WordPress Businesses** This week's cautionary tale involves a startup whose entire business was destroyed when Namecheap suspended their domain due to a frivolous trademark claim. Despite winning in US court, the founder is now facing personal lawsuits and legal fee demands. **Key Takeaway**: Your domain registrar can make or break your business. Choose wisely. **Recommended Registrars for WordPress Sites**: - **Cloudflare**: At-cost pricing, strong reputation management - **Vercel**: Developer-focused, excellent dispute resolution - **DNSimple**: Engineer-run support, API-first approach **Red Flags to Avoid**: Registrars making money primarily from domain margins (GoDaddy, Namecheap) often engage in predatory practices like surprise renewal fees and poor dispute resolution. **Action Item**: Review your domain registrar's terms of service and transfer to a more reliable provider if needed. Your business depends on it. Resources: [WordPress Hosting](https://wordpress.org/hosting/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create domain security workshop content for developer conferences - Education: Develop "Domain Infrastructure 101" curriculum covering registrar vs registry - Developer experience: Document domain transfer processes and backup strategies - Developer marketing: Partner with reliable registrars for developer-friendly domain content - Community management: Monitor domain-related support requests and escalations #### OSPO - Policy & Governance: Establish domain ownership and transfer policies for open source projects - License Compliance: Review domain registrar terms for compliance with open source license requirements - Security Management: Implement domain monitoring and reputation tracking systems - Software Inventory: Catalog all organizational domains and their registrars - Developer Support: Provide guidance on domain security best practices - Community Engagement: Support open source projects affected by domain disputes - Strategic Alignment: Track domain security metrics and incident response times #### Community - Maintainers: Provide domain security templates and governance frameworks - Contributors: Create guides for protecting project domains from attacks - Sponsors: Fund domain security tools and services for critical open source infrastructure - Ecosystem: Coordinate response to domain-based attacks on community projects #### WordPress - Core: Evaluate domain validation and verification improvements for WordPress.org services - Meta: Strengthen domain verification processes for WordPress.org accounts and services - Hosting: Develop domain security guidelines and recommendations for hosting providers - Community: Create domain security workshops for WordCamps and meetups - Documentation: Add domain security section to WordPress security documentation - Support: Train support volunteers on domain-related issues and escalation procedures ## 🧪 Hypotheses - Companies that derive primary revenue from domain margins engage in more predatory practices than those with diversified revenue streams - Public reputation sensitivity on social media platforms correlates with better customer dispute resolution - Domain infrastructure centralization creates systemic risks that can be exploited for censorship and business destruction - Personal lawsuits against business owners create disproportionate pressure compared to corporate litigation ### 📊 Methodology - Survey registrar pricing models and correlation with customer satisfaction scores - Analyze social media response times and resolution rates across different registrars - Map domain infrastructure dependencies and identify single points of failure - Compare litigation patterns between corporate and personal defendant cases ### ❓ Questions - How can domain infrastructure be made more resilient to false flagging and bad actor attacks? - What regulatory changes could prevent registrars from weaponizing personal lawsuits against customers? - How can businesses better protect themselves from domain-based censorship and retaliation? ### 🔮 Future Research - Investigate decentralized domain systems as alternatives to traditional DNS infrastructure - Analyze the effectiveness of different legal frameworks for protecting domain ownership rights - Study the impact of domain reputation systems on small business accessibility ### 💡 Implications - Practice: Businesses must carefully evaluate registrar selection as a critical infrastructure decision - Policy: Need for stronger consumer protections against predatory domain practices and personal lawsuit harassment - Security: Domain security requires multi-layered defense including backup domains and reputation monitoring - Education: Developers and business owners need better education about domain infrastructure risks - Funding: Critical open source infrastructure needs dedicated funding for domain security and protection ### 🧠 Learning Styles Assessment Reading level estimate: 9th Grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Screenshots of legal documents, court orders, and registrar interfaces - Improve: Infrastructure diagrams showing registry vs registrar relationships, attack vector flowcharts #### 🔊 Aural learners - Present: Video format with clear narration and examples - Improve: Audio summary of key legal concepts and registrar comparison criteria #### 🗣️ Verbal learners - Present: Clear definitions of technical terms, analogies to gas stations and convenience stores - Improve: More analogies for complex legal and technical concepts #### 🧩 Kinesthetic learners - Present: Step-by-step registrar evaluation process - Improve: Hands-on domain transfer checklist, interactive registrar comparison tool #### 🧠 Logical learners - Present: Clear business model analysis and decision framework - Improve: Quantitative risk assessment matrix, cost-benefit analysis templates #### 🧑‍🤝‍🧑 Social learners - Present: Community discussion and shared experiences - Improve: Peer review system for registrar recommendations, collaborative risk assessment #### 🧘‍♀️ Solitary learners - Present: Detailed case study analysis and self-directed research - Improve: Self-assessment questionnaire for domain security readiness #### 🌿 Naturalistic learners - Present: Ecosystem analogies and infrastructure dependencies - Improve: Environmental impact considerations of different registrars ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Good heading structure and logical content flow - Improve: More descriptive link text, better alt text for legal document screenshots #### Keyboard navigation - Present: Standard video player controls - Improve: Timestamp navigation, transcript integration #### Contrast and readability - Present: High contrast video with clear narration - Improve: Transcript formatting with proper heading structure #### Text resizing and reflow - Present: Responsive video player - Improve: Scalable transcript interface #### Media and captions - Present: Automated captions available - Improve: Professional captions with legal terminology accuracy, downloadable transcript #### Forms and interactions - Present: Standard YouTube interface - Improve: Interactive registrar comparison tool with proper form labels #### Standards reference - Transcript needs proper heading hierarchy (WCAG 2.2 1.3.1), improved link context (2.4.4) ### 🌍 DE --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=gPcB2VdzeKo)* **[00:00]** I'm going to be real with you guys. I have had so many problems with domains. A significant number of them are admittedly skill issues, but even more of them weren't. The amount of times I've had domains get taken from me for reasons that I had no control or oversight over just to be held ransom for thousands of dollars in fees because some provider from some random country that happens to operate the.gg decided that this day they wanted to charge me more money. And that one was, did you know you have to renew those domains over a month before they're going to expire or you have to pay this crazy fee? **[00:31]** I've been through it with country code TLDDS and domain registration in general. Almost every domain I have I've had some issue with at some point, but none of them go quite as far as the story I'm here to tell you guys today. Because poor Sna had her domain taken from her by NameCheep and then got sued for it. Yes, NameCheep sued her personally. I've never seen anything quite like this. And the story is as frustrating as it is heartbreaking. It has massively impacted her business and the work that she is doing. And I think **[01:02]** it is a good showcase of how risky domains are as a surface area and what you have to be considerate of as you build a business nowadays. There's a lot to think about here and honestly I hope you never have to. In an ideal world, you'll never have any problems like this and as such you'll never have to worry about it. But if you are building real products that have real websites, there's a chance you'll have to worry about this. And hopefully going through the story here will make you less likely to get screwed the way that this poor **[01:32]** founder was. As someone who's personally had bad experiences with namecheep, I'm going to be a bit biased here because I want to watch them burn. So know that going in. Do you know what? I've never had any problems with though today's sponsor. We're shipping way more code than ever. That also means we're probably shipping more bugs than ever. Unless we use today's sponsor to catch them, Grapile, the best AI code reviewer. Graptile deeply understands your codebase and it uses that understanding to catch mistakes that almost nothing else can. I'm regularly surprised that it found bugs that not only other tools couldn't, but I **[02:03]** couldn't. It has personally prevented me from shipping many bugs and regressions to users. I saw it on a ton of open- source repos, so I went to grab examples. But when I told them I was doing this, they went and did it for me and made a whole Grapile in action page for all the open- source projects using Grapile. By the way, open source projects get a 100% discount and startups get a 50% discount. So, if you are doing meaningful open source work, you should probably be using these guys. There are literally dozens of examples of big open source projects from companies like Nvidia that had bugs prevented because of Reptile. Here's a **[02:33]** bug where Post Hog almost broke sorting by using the same variable twice instead of comparing the two different variables that Grapile caught. This would have shipped otherwise. Here's a real PR in a real NVIDIA repo that it gave a three out of five confidence score because it caught a bunch of potential bugs and risks, even flagging down which specific files these concerns are coming from. The author made the changes, said it was a good catch, and then it re-reviewed with a perfect score. Do you know how convenient this is? Do you know how good it feels to bump a three or a two out of five to a five out of five? It's so much more rewarding and less grindy than **[03:05]** traditional code review processes. Instead of putting up a PR, waiting a day for a review, making some changes, then waiting another day for feedback. It's such a tight loop. Grabs changed how I ship code. I bet it will for you, too. Check them out now at sidv.link/grapile. [ __ ] fammy. This feels like a bad time to own billgates.exy. Yeah, [laughter] let's dive in. Cautionary tale for fellow startup founders. Namechep just sued her personally. There's a community note because there are people who are **[03:36]** upset. Some amount of it's real, some amount of it's just sexism. We'll get to all of that, don't worry. But first, we need to actually read what she has to say. In January of 2025, NameCheep shut down my company's website globally. I was forced to file a temporary restraining order against them to get our site back. An American court ruled in my favor. This is a state of Arizona court motion. The court having considered ink mango in this case to the plaintiff's motion pursuant to this litigation for temporary restraining order and good cause appearing. It is hereby ordered that plaintiff's motion **[04:06]** is granted. So this is you can keep the domain temporary restraining order means that's yours. The domain is for her business the juggernaut on the juggernaut.com. As she's puts it she runs a juggernaut. It's a startup that tells powerful South Asian stories. When name took them offline the business came to a screeching halt. growth, usage, and word of mouth is a startup's lifeblood. They lost all of it in a few weeks. That is so hard for any business, but especially something like this where it's so deeply tied to the website. There are so many businesses that I only know how to interface with via the **[04:37]** website and like typing in the URL. I'll use my Helium browser because this is what I use for this type of stuff. But like when I want to go see what's going on in music, I type in PI and it goes to Pitchfork. When I want to go check on in on some code, I type GI and I go to GitHub. When I want to ask a question about something going on in the world or just general intelligence stuff, I type T3 and I go to T3 chat. The best AI chat ever made. Highly recommend it if you haven't checked it out. So, losing the thing that people autocomplete their brains to and their browsers to is really, really painful. I don't know how we would bounce back if we lost the T3 **[05:08]** chat domain. Our entire web presence vanished overnight. People couldn't read articles. Customers were furious. We lost paying subscribers and couldn't acquire any new ones, especially in one of our biggest acquisition months. We lost years of SEO that we had painstakingly built. That one is really, really bad, too. We've been [ __ ] with this with stuff like T3 Chat. To this day, T3 Chat does not place properly in Google search results, primarily because we were incorrectly placed on a filter for spam and scam sites because some **[05:39]** haters of mine during a specific drama with a specific media encoding library decided to go false flag all of our domains. It took multiple days and many a string poll for me to get our sites unlisted from these spam sites. It was horrible. even like spam house and ones that are meant to be the good ones ruined our ability to be able to do [ __ ] And we were at the point where users of upload thing, our file upload service, which if you're not familiar with, one of the coolest things we built, it's the easiest way to do file upload. Our CDN domain for where assets are resolved, got hit by one of those **[06:10]** filters because again, people were falsely flagging our domains to these different spam collectors and providers that give these lists to companies like ISPs and whatnot. And even though we got it pulled within 24 hours, there were multiple ISPs in Europe that kept blocking upload thing URLs. So a handful of our users that had customers in Europe couldn't resolve assets like PDFs, images, whatever they were hosting because some random [ __ ] reported us to some random [ __ ] company that got us flagged. It's actually insane how **[06:41]** easy it is to ruin a company by doing weird [ __ ] to their domain. Here's the story from when this happened back in October. Spam House false flagged us. Specifically, our domain was listed as being for fishing and criminal activity. Obviously, a false flag. And RSEO to this day is [ __ ] because of this one thing. There are all of these players in the domain space. Be it your registry and your registar, which are two different things that own different parts of the process. Be it the governing body for the TLD, if you have **[07:12]** a TLDD that's like aggi.uk, UK. The governing entities for those is a whole separate thing. And then you have these spam lists that are published and sold to companies to determine which websites should or shouldn't be autoblocked. The fact that there are so many layers here where any one of them deciding they don't like you or failing you can destroy your whole business is horrifying. You know the XKCD dependency comic where it's like here's everything that we're building on top of stuff and on here is like a solid wellunded thing like Linux and then here is something **[07:42]** that's smaller and less wellunded that we rely on. Every website is this but on this bottom section you have the registry the registar and this tiny little thin one is more like a toothpick. spam house and other spam and site like reputation lists and these pieces can break and destroy your life at any point in time if you run a company as happened to sniga here. Shutting down a news organization also raises serious first amendment and free speech concerns. Absolutely agree the **[08:13]** fact that you can use this as a method of censorship as is what happened to me. People were unhappy about my takes around a specific open source library's governance and decided that I should not be allowed to run a business. People went as far as saying I deserved it and I knew what I was asking for for daring to say that a specific open-source library probably shouldn't be dunking on random contributors and funders for it on Twitter. Crazy take, I know, but the fact that I donated five grand to a library's development and then had issues with how they dunked on people on Twitter should not cost me my company. **[08:44]** That is censorship. And the funniest part with that one was that people were accusing me of censoring the project for having an opinion and then went off to legitimately try and censor me using weird levers and power grabs that should absolutely be illegal. I am fullon okay with the idea of criminal prosecution for anyone who does [ __ ] like this. Be it the name person who's trying to sue this poor girl, be it the company that is abusing copyright law to cause this, or be it the individuals knowingly filing false flags to harm businesses. **[09:14]** That should be criminal. Period. Back to this poor situation. When this happened, they were in mid-con conversation with investors and they had to suspend that because the investors would go check the site and it wasn't even [ __ ] there. One investor even messaged me on LinkedIn asking if I had shut down my business because he couldn't find it online anymore. Yeah. Do [snorts] you know how hard that conversation must be to explain to an investor who's possibly put millions of dollars into your business? Yeah. Sorry you can't see our website right now. I'm actually in the middle of a lawsuit. That's not what they invested into you for. They didn't invest into you so you could win lawsuits. They invested in you so you **[09:45]** could win period. Despite multiple messages to name support, the company was unresponsive. So she, poor thing, had to sue NameCheep personally to recover the domain. Now, because of that, NameCheep is suing her back. NameCheep's claim is that the domain was registered in her name even though it was used for her company. This is very, very common. Also, I'm pretty sure most domains require that you have a personal business contact as one of the parts of the IK registration process. like you have to have a name registered. The fact that her name is a name registered to **[10:16]** this domain that is not just the company is their excuse for suing her instead of the company is absurd. And it's not like they're suing her LLC or some entity. They are suing her personally. I've already been saying things that can get me in trouble. I'm going to say one more. This is a strategy that has been weaponized by a lot of religious cults, in particular the Church of Scientology. The only reason the Church of Scientology is a taxexempt organization in the United States is because they would personally sue every single person they found working for the IRS. They **[10:47]** would instruct members of the cult, sorry, Church of Scientology to personally reach out to people that were working for the IRS and sue them as individuals. None of the lawsuits ever succeeded, but all of them wasted enough time for the IRS employees that the IRS was going to collapse under the weight of half their employees being busy in these [ __ ] court cases. So, the IRS gave up and gave the church their [ __ ] taxexempt status. And they did it by doing this [ __ ] Using the **[11:17]** courts to crush your competition, not by beating them with the law, but by distracting them with the process is horrifying. And if you have any doubt about anything I just said, you can look it up. This is very wellnown. In 1993, the Church of Scientology and the IRS reached a landmark secret settlement ending decades of intense legal battles granting the church taxism status as a religion in exchange for dropping over 2500 lawsuits against the agency, most of which were against individual employees of the agency. Actual insanity. So, I guess that NameCheep and **[11:48]** the Church of Scientology have more in common than I would have guessed. Crazy. NameCheep also claims that it had broad discretion to shut down your domain quote at any time for any reason. That's part of their terms. They claim they have the right to do that at any point. Horrifying. And that creates massive uncertainty for founders. And now NameCheep is trying to win exorbitant legal fees from her despite the court saying that they deserve the domain back. So again, the court said she deserves the domain. NameCheep declined that and is now counter suing her and trying to squeeze legal fees out of her. **[12:21]** The original CEO of NameCheep had tweeted previously saying that he'll get the domain back primarily because Gary Tan jumped in and asked questions. In the meantime, probably geoence India from your core domain and do not work around this as a redirect to another domain from your core domain and she can and he'll temporarily bring it back. So specifically what it seems like happened was that in India the [ __ ] trademark case about Juggernaut because another company claimed to own the Juggernaut trademark sued her and forced NameCheep to remove the domain from her even though that ruling was only applicable **[12:51]** in India and other courts specifically the court that both her company and NameCheep are incorporated in the United States went against that ruling. The India courts firmly stated that this domain cannot be owned by her. So the workaround was that the CEO personally said as long as you don't use this domain in India, we'll give it back to you. And then Gary Tan jumped in. This sounds like what you're demanding is even beyond what the New Delhi courts and the plaintiff advocated for. This idea that the the domain should not work at all within India is not what the **[13:22]** original court case pushed for in New Delhi. But NameCheep just wants to wipe their hands clean and technically speaking, they can do whatever they want. But again, name is a company. They can choose if and how they provide you services. And it seems in this case they decided to just put the work on the founder instead of make a service work well for the specific details of this ruling. And it was significantly easier for them to just remove the domain or force her to apply one rule to the domain. That makes the experience a lot worse because technically speaking, there's no reason she shouldn't be able **[13:52]** to redirect the juggernaut.com domain in India to something else that is within her trademark rights there. But again, an American court operating against two American companies ruled that NameCheep needs to do things a certain way and they overrode that. NameCheep's valued at 1.5 billion and Porsa hasn't raised the series A yet. So, she has way less than 3 mil almost certainly, probably less than a mill in the bank for this. So, that's like you can't deal with that. I'm going to keep fighting in court. I refuse to be intimidated. As a YC alum, it feels like it's my responsibility to warn others. This can **[14:23]** happen to you. If you'd like to help, please amplify this thread. Then the old CEO came in and claimed that this is public lies and manipulation of the truth. Things aren't going to get any easier. That's a threat. That's a threat from the CEO of a billion-doll company. The case started in 2019 and ruling after ruling has been made against you. You even stopped responding at some point because you thought you could ignore your responsibility. Settled means you faced the facts and gave into the demands. You've made this whole situation worse for yourself now. So the party suing is Juggernaut Books. **[14:54]** Juggernaut books does online publishing of digital books and also has started doing physical books afterwards. Whereas the juggernaut is South Asia stories you know like clearly a news site. Is there some overlap between a book publisher and a news site? Yeah. But in American courts this would never stand. These are obviously distinct enough entities that no one's going to reasonably confuse the two which is the general litmus test for trademark law here. The juggernaut is the news site. Juggernaut Books is a different entity that is the company **[15:25]** doing the lawsuit. I think personally it's a bit absurd that you can prevent the use of a generic term like juggernaut for things that aren't even in competition with you. Absurdity. This is a very clear order from the US courts. It is further ordered that defendant name Inc., its officers, agents, directors, affiliates, servants, employees, and all persons acting in concert with them hereby enjoined from preventing or frustrating plaintiffs use of its registered domain, the juggernaut.com, provided that the primary domain is geoence to prevent access to the primary domain from users in India. That was the only restriction. **[15:56]** I even think this is stupid that like the American court is making rulings on other courts like this, but that's the only counterargument that NameCheep had. more call outs here that they are specifically enjoined from restricting access to the domain or indirectly causing the expiration of the domain which is another thing NameCheep loves to do is make it too easy to let your domain expire so they can charge you crazy fees I've experienced that many others have too and here is a US counter claim let's see how this one went this is filed by the attorneys this isn't a court document this is the attorneys let's see how the courts responded to **[16:26]** that though oh huh weird name took the time to include their counter claim where they did not take the time to include the court's response by the looks of it. I wonder why. It's also sus that this is only the lawsuit name sheep filed against the company and not the separate one they filed against her. This is a great one. This is the legal mail that was sent from the legal firm for NameCheep to these guys. This letter follows Mr. Bryer's November 6, 2025 **[16:58]** telephone call with my partner Eugene Rome during which Mr. Bryer expressly communicated on behalf of your client, listening to sir, that one, Inc. Mango has made a settlement demand. Two, Miss sir does not appreciate being personally named. Three, Miss sir demands that namecheep dismiss its counter claim within 10 days. And four, if we do not, Miss sir intends to quote go to Twitter to talk about the case. Because this threat was affirmably conveyed by council as part of your settlement communication, the conduct is attributed to council as well. For the reasons **[17:30]** below, the threat is improper, unprotected, and exposes Miss Sir to potential civil liability and your firm to both civil and ethical consequences. This is them sending their lawyers after her and her lawyers, saying, "If you actually go to Twitter like you said you will, we will sue you for threatening us." Insanity. How the [ __ ] did the CEO post this Google Drive thinking this would clear him in any way? I was actually expecting to like see some stuff and you're like, "Okay, that's fair. I see the other side." No, I'm gonna go [ __ ] yell at him for this. **[18:01]** It is done. So, like that last bit here to be very clear, for the reasons below, the threat is improper, unprotected, and exposes Miss Sir to potential civil liability and your firm to both civil and ethical consequences. That is the name legal firm threatening Miss Sir and her legal firm. Because they see we will go public as a threat, they now feel in the right making their own. Are you joking? So the next question you have and it's the right one. Where do you go now? Great **[18:31]** question. I am going to drop the hot take that any business that makes the majority of their income through fees and margins on domains is probably not the best place to register your domains. I would not trust GoDaddy particularly more than I would trust NameCheep. If these margins are how you make your money, then you're going to squeeze every [ __ ] penny you can. And I've seen this a lot with these registars, even like GoDaddy. I guarantee I haven't been to this website in a minute. I'll put money on it. The word AI occurs in **[19:02]** the first two sentences or the header because they're going to do anything they can to make money. Oh, huh. They actually haven't. Oh, there we go. Build your site at the speed of AI. I was wondering where it would be hidden on the page. The point I want to make here is that like they have to do dirty things to win because there isn't much margin to be had because the domain registars like the places we go to to buy domains, those are not the lower level registry. They're effectively resellers. Think of domain registars less like a Walmart or a Trader Joe's **[19:35]** and more like a gas station. Like there's only so many suppliers and everyone's buying from it. It's really, really hard to make a profit off of just gas, which is why most gas stations make their money by selling other things like in their little convenience stores and whatnot. That's like essential for them to make meaningful margins. Domains are very similar because all of these domain companies are buying from the same three or four registries. The ones that make all of their money off of that margin can't really be trusted and they'll always do crazy stuff like if you see a **[20:05]** crazy deal like your first year is only 1 cent. like here a.com for only 1 cent for the first year. The reason they do that is because they charge 20 to 30% more than everybody else for the second year, the third year, and the fourth year. And the math works out that it ends up being profitable over time. Personally, I only like working with registars that have two specific traits. One, they make their money elsewhere. And two, they're sensitive to the reputation on Twitter. So, starting with this point, what am I referring to? When I mention Cloudflare or Versel, what **[20:36]** comes to mind? It's probably not the domains product. Every domain I've personally registered in the last three years has been either on Verscell domains or it has been on Cloudflare's domains. Neither of these companies make money off of their domain selling. If anything, I'm pretty certain that Verscell loses money because they've been too generous about weird disputes. Like I had problems with my.gg domain on Versel because they didn't set up the registry process properly for that specific TLD at the time. That's all been fixed and then some. At the time it was bad and cost some fees and Verscell **[21:07]** just ate the fees for me. And that's not just because I'm Theo. That's because I was one of four people who were affected by this particular implementation failure and they refunded all four of us those fees that were in the thousands of dollars. So that just was a raw cost they ate because Verscell is not trying to make money off the domains. It's not like, oh, we lost this money off of these domains. Now we have to go sell 5,000 domains to make up for it. For them, it's much more so we lost the money on these domains, but we'll probably make the money back on these customers over time because these same customers are buying other things on our **[21:38]** service. Somebody said, "What about country TLDDS though? Cloudflare don't offer those." They don't. Looks like GG isn't offered because GG is an evil one. I would argue if they're not offered on Cloudflare or Versel, you probably shouldn't buy them because they're full of catches. I cannot tell you how many problems I've had with my.gg domain. They do have.AI AI even though that's a country TLD. So you have some options there. But CCTLDs are evil and you should avoid them at all costs. The other reason I'm mentioning Verscell though is point two. They care about their reputation. Specifically on **[22:10]** Twitter. I am now at the point where it's really hard for me to justify using a product or service that doesn't care about their reputation because it's such a strong lever to have. Oh, Theo, you just have that cuz you have followers. No. In fact, earlier today, someone came into my chat that I remember specifically because despite having under 50 followers on Twitter, he caused one of the most hellish days in the history of Verscell because he had a bug in his code that caused Astro Code to redirect loop and do thousands of server **[22:41]** calls before it would eventually die. That caused him to get a random like $400 bill on Versel. And then Verscell's default support didn't refund him because they didn't understand it. So then he posted on Twitter about it. It blew the [ __ ] up and he got refunded. He got personal support from the CEO and from Lero when he was still there. He got patches in Astro. He got patches in Verscell. A lot of actual things changed as a result of this random developer complaining on Twitter in a digestible way because Verscell cares a lot about how people feel about them on Twitter. Believe me, I know better than anyone. Verscell cares too much about these **[23:12]** things. And as much as that sucks that they care too much about Twitter, it's a lever you have as a customer. And with things as important as your domains, you need levers because there's so many against you. The fact that a random hater can go false flag you to a bunch of spam trackers is enough a reason that you need leverage back. You need ways to, for better or worse, exploit the other party here because they will be quick to do the same to you and others will be even quicker to use them against you. So, who would I recommend based on these things? I know we don't all love **[23:42]** Versel, but Versel for domains is pretty solid. They have annoying rules around CNAs that makes it stupid, but for the most part, Versell is good here. Cloudflare can be too, but I've had some weird issues with Cloudflare in particular. It's very hard to take a subdomain from a domain you have on Cloudflare and have that subdomain go somewhere else. Very unreliable. So, for those reasons, I personally lean forcel between these two, but there are lots of other really good options. One that I am really fond of that is a sponsor, not of today's video or any of the content now, but they've sponsored in the past and I hope they continue in the future, Dian **[24:13]** Simple. D and simple. Yes, they make their money on margins for domains, but they have slightly higher margins because they have a very different service. It's their goal to make it as easy as possible to manage everything to do with your domains via your code. And they are selling their control plane and their SDK as much as they're selling domains. But more importantly, they're just a small team of people based out of Florida. If I recall, I did a call with the founders cuz they wanted to sponsor. And it was the husband and wife, founders of the company, wearing their **[24:45]** branded t-shirts, really excited to beat me because they've watched my videos and like them. Every employee at the company is an actual engineer. So when you go to support, you're talking to real engineers. You can just tell when you read the SDK, it's like, okay, they're devs. They get it. They understand. And since they're smaller, they're inherently going to be much more sensitive to their reputation. If the first time you hear about D and Simple, it's because someone had a bad experience, they're screwed. So, as much as I hate to say you should make my sponsor feel bad if they screw you, you should. If any of my sponsors make your **[25:16]** life harder or screw you or hurt your business, tell me about it and be loud about it publicly. I don't want sponsors that cause problems for my viewers. If anyone in my audience has an issue with any of my sponsors, please tell me so that I can rethink my relationship with them and use my leverage to pressure them because it's important. It's really important. So, for all of those reasons, DN Simple's a very good bet. I also know a ton of people who have been using them heavily, including but not limited to the Linux Foundation, so they seem like a reliable bet. I wouldn't worry about them. And while Diannle didn't sponsor, use soy.link/dnsimple **[25:47]** to make sure they know you came from me. It helps. Thank you. Anyways, there's one last name that I've been hearing come up a lot, and if I look at my chat right now, it's half of it. It's a little scary to me, but I think they're fine. Pork bun. I have a couple domains on Pork Bun. I've had no problems. From what I have heard, most people haven't. And they also, the very least, in terms of reviews, seem to care a lot about how much people like them and use them. So, I would bet that if you had a problem and you went and complained on Trust Pilot or on Twitter, there's a good chance they'll hop in and deal with it. This is a fun back and forth that **[26:17]** happened related to all of this. A few days later, someone had their domain that they were searching for on GoDaddy get purchased as they were searching and then resold to them. Like a a classic rugpull. Insanity. And it should absolutely be illegal. I agree with Britain there, but I don't agree with Britain saying that you should always use namecheep because Google domains is dead. I said use Versel Cloudflare or some company that doesn't make their income off upcharging for domains. Pork bun is fine, too. Joshua community came in and said careful with pork bun if you have any valuable domains. He had a problem which she links to here. So, got **[26:49]** an email that $15,000 of domains is past expiration that shouldn't be auto renews on credit cards attached. Get this error. Uses 15k of domains. He's not going to be happy. So he said that and Porkbun hopped in. We try to make it right, but sometimes you can't fix a wrong. We're humans trying to do our best and although we strive for perfection, haven't quite gotten there yet. We obviously have many tens of thousands of valuable domains used and owned by many thousands of users who trust us with their assets every day. So they linked to their tweets replying to these issues here. Registry suspended domains are done at the registry level by the registry and not the registar. **[27:20]** Again, the separation between these two is confusing to people. The registry is who determines what is allowed on a given TLD and then they sell that to a registar like pork bun, namecheep or any of these that can then sell it to you. So the registar is the company that works with the registry to get your domain made but the registry has to be okay with it. And the registry can have all sorts of weird rules, regulations and things they want to do. And occasionally if the registry doesn't like you or the thing about what you did or how your registar is working with them, then you get screwed because there's all of these layers. But a **[27:52]** registar blocking your account from renewing other domains because a tldd registar suspended a domain with an invalid information request happens at the registar level and tldd are what he means is a registry. So registry at the bottom requested that pork bun suspend one of his domains and in the process they locked his whole account which sucks. That was on an unused domain and it blocked his ability to renew other domains. We're sorry that we lost your trust. It was a series of unfortunate events but what happened will not be able to happen again. As a builder and business owner yourself, I'm guessing you can appreciate that things sometimes **[28:23]** can and do go wrong. We'll fix what caused your issue and will do better. But it's unfortunate that it happened to you and I apologize that it did. This type of ownership is why I'm okay with recommending them still. It's clear they care. It's clear they're trying. I have a lot of respect for that. And the the ownership of we did this wrong, we screwed this up is also really rare. I've never seen NameCheep admit that they [ __ ] something up before. You know what? I I'll put that as a point here. This is possibly the biggest most important point because if they can't admit that they screwed up, the likelihood that they fix the thing is much lower and the likelihood that they **[28:53]** sue you is much higher. So, as Maria put it, Apple would never do something like this. I agree. I would never register a domain through Apple. I'm thankful they don't offer that product. But as long as they make money other ways, they care about their reputation, and they admit when they're mistaken and they screw up, you're probably good. So, everything in this list is totally fine for me. There's probably others that meet these requirements and are solid. GoDaddy does not, Two Cows does not, and sure as [ __ ] NameCheep does not. So yeah, I think I've said all I have to here. Be careful with your domains and make sure they **[29:24]** register with somebody you can actually trust. And until next time, peace nerds.