Battle for the Brand: weddings.io Formal Complaint Letter Against aiweddings.io

July 2026 — Formal Complaint Letter Against aiweddings.io / Weddings.io Inc.

On July 2, 2026 we filed a formal Statement of Objection with the Ontario Ministry of Public and Business Service Delivery under Section 32 of the Business Names Act, targeting a company operating in Ontario under the registered name 'Weddings.io Inc.' and connected to the aiweddings.io conflict.

For the record: we have owned the weddings.io domain continuously since May 13, 2015. We have no affiliation with 'Weddings.io Inc.' The registration of a business name that mirrors our trademarked domain — nine years after our public, continuous, WHOIS-verifiable ownership began — is the kind of dilution the Business Names Act was written to remedy.

This filing is the escalation of the same defensive doctrine that has protected the brand since 2015: hold publicly, document everything, and use every legitimate legal instrument available when a copycat crosses the line from lookalike domain into registered business impersonation.

May 13, 2015 — the day the brand was claimed

Weddings.com had been locked up by a legacy directory since the late 1990s and quietly abandoned as an editorial property. Every serious wedding tech operator we spoke to in 2014 assumed the category-defining .com was the only domain worth fighting for. That assumption is exactly why we filed weddings.io instead.¹

The .io TLD signalled modern tech, ranked identically for high-intent searches like ‘weddings vancouver’ and ‘weddings toronto’, and — critically — was uncontested. ICANN WHOIS confirms continuous ownership from May 13, 2015 through the current registration period ending 2027. No lapse. No reseller flips. One owner, eleven years.

That single act — picking the right TLD on the right day — is the first chapter of the battle for the brand. Every later attack, every copycat, every directory middleman that tried to dilute the slot, traces back to a decision that was free to make in 2015 and is now impossible to undo.

2016–2023 — the quiet build, captured 78 times by the Internet Archive

Between 2016 and 2023, weddings.io ran as a deliberately quiet placeholder while the surrounding pieces of the IAM stack — territory locking, EyeSpyR verification, TALC.tv content generation, the $10 flat-slot pricing model — were prototyped on smaller trade domains.²

The Internet Archive has 78 separate Wayback Machine captures of weddings.io across that window, with the earliest crawl on May 17, 2013 against the prior placeholder page. That capture history matters: it is the public, third-party proof that the domain was held, actively served, and continuously evolved — not parked.

The quiet years were the work. Nine cultural pilots, 1,018 city pages prepared in the staging environment, and 24 country-level translations were drafted long before launch. None of that ships without a stable domain underneath it. The 2015 registration bought us the runway.

2024 — the copycat wave (yes, aiweddings.io, we see you)

Once generative AI made the ‘AI + category’ naming pattern trendy, the copycats arrived. The most aggressive was aiweddings.io — a domain registered nine years after ours, on a brand we had already trademark-defended, trying to ride coattails into a category we had been quietly building since 2015.

We responded with the long version of this argument in a separate post: ‘You Built Your Tower on Our Land.’[^ailand] The short version is simpler. Eleven years of continuous ownership, public WHOIS, 78 Wayback captures, and a documented build pipeline are not erasable by registering a similar string in 2024.

The lesson generalises beyond weddings. Every IAM domain — gasfitter.ca, plowwow.com, kongtractors.com, hamiltonhomeservices.com — was acquired or registered with the same defensive posture: get there first, hold it publicly, document everything.

The receipts extend across the whole network

Weddings.io is not the only domain with a paper trail. gasfitter.ca was registered through CIRA in 2007 — an 18-year continuous hold on the category-defining Canadian gasfitting domain.⁵ Hamiltonhomeservices.com has Wayback captures dating to 2004, making it one of the oldest continuously-indexed home-services properties in the country.⁶

Both are part of the same defensive doctrine: register the category-defining domain early, hold it through the quiet years, document the hold with third-party public records, and ship the platform on top of it once the technology catches up to the strategy.

When a contractor asks why a $10 listing on gasfitter.ca outperforms a $2,000 custom site on a brand-new domain, the answer is in those Wayback captures. Topical authority compounds over decades, not quarters.

2025–2026 — the AI-enabled relaunch

Two things changed in late 2024 that made the original 2015 vision finally shippable at the scale we always wanted: generative AI made per-city, per-trade content economically viable at $10 instead of $10,000, and answer engines (ChatGPT, Perplexity, Google AI Overviews) replaced ten-blue-links as the discovery surface for high-intent search.

Weddings.io now runs the full IAM stack: one verified planner per metro, EyeSpyR physical verification, TALC.tv content generation, WhatsApp lead routing, $10 flat slot pricing, and schema-first markup engineered to be cited by answer engines rather than ranked by classical PageRank alone.

The relaunch is not a pivot. It is the original 2015 thesis, finally executable. Eleven years of holding the brand was the precondition — not the project.

What this means for every IAM territory partner

Every contractor who locks a $10 IAM slot inherits the same posture weddings.io has been building since 2015. The domain is older than the competitor. The schema is engineered for answer-engine citation. The territory is exclusive. The receipts are public.

The battle for the brand is not a one-time event. It is the daily practice of registering early, holding publicly, building quietly, and shipping when the technology finally clears the runway. Weddings.io is the most documented example. It is not the only one.

Timeline

The receipts, in order

1. May 17, 2013

   First Wayback capture

   Internet Archive begins indexing the weddings.io placeholder under prior ownership.

2. May 13, 2015

   Registration

   weddings.io registered through ICANN. Continuous ownership begins.

3. 2016–2023

   Quiet build

   78 Wayback captures across eight years. IAM stack prototyped on adjacent trade domains.

4. 2024

   Copycat wave

   aiweddings.io and other lookalikes register on the AI-naming trend. Brand defense begins publicly.

5. 2025

   Stack convergence

   EyeSpyR, TALC.tv, WhatsApp routing, and $10 flat-slot pricing reach production parity.

6. 2026

   Relaunch

   weddings.io ships as the wedding industry's exclusive-territory disruptor on the full IAM stack.

Footnotes

1. ICANN WHOIS lookup for weddings.io — registration date May 13, 2015, current expiry 2027. ↩
2. Internet Archive Wayback Machine — 78 captures of weddings.io since May 17, 2013. ↩
3. Master pricing chart — The 250 Scale. $10 per slot per month, slot counts step with city population. ↩
4. Weddings Ecosystem — cost stack, ROI vs. directories, IPO roadmap, and 3–10 slot availability per metro. ↩
5. CIRA WHOIS lookup for gasfitter.ca — registered 2007, continuous Canadian ownership. ↩
6. Internet Archive Wayback Machine — hamiltonhomeservices.com first crawl 2004. ↩