IP defense strategy for digital-native assets.
IPLaw is the intellectual-property strategy layer for the eCorp network. It turns a domain's history — registration date, continuous use, archive record, brand-family context — into a documented, defensible position, and routes matters that require legal judgment to licensed counsel. The premise is simple: a senior, operated digital asset is property, and property is defended on the record.
Why this exists
A domain registered and used for decades is not a string. It is an asset class with provenance.
Most domain disputes are not close cases on the merits — they are contests of organization. A later-arriving brand sends a demand; the senior holder, if unprepared, scrambles. IPLaw inverts that. Every eCorp asset carries its chronology, its evidence, and its posture before any demand arrives, so the response is a documented record rather than an improvisation.
For partners and investors, that discipline is the point: it is what converts a portfolio of names into a portfolio of defensible, governed, value-bearing assets.
What IPLaw organizes for every asset
Provenance. Registration and WHOIS history, creation date, and continuous-use record.
Chronology. A factual timeline of use, claimant first-use, trademark filing dates, and demand sequence.
Brand-family context. The portfolio relationships that show coherent strategy, not isolated holding.
Posture. A non-admission response position, reserved rights, and a clean handoff to counsel.
The senior-rights doctrine, in plain terms
United States trademark priority generally turns on first use in commerce, not on who registered a mark first. A domain that was registered and continuously used before a claimant existed reflects senior rights; the claimant's later mark is junior. Junior rights do not extinguish senior rights. This is the spine of nearly every digital-asset defense.
Senior holder
Junior claimant
This is general doctrine for positioning, not legal advice. The facts of each matter control, and legal judgment is routed to licensed counsel.
The domain-defensibility framework
Every eCorp asset is graded against the same factors. Strong signals compound; weak signals flag where evidence or strategy needs work before a matter escalates.
| Factor | Strong signal | Weak signal |
|---|---|---|
| Priority of use | Registered and used years before claimant's first use | Adopted after the claimant was established |
| Continuity | Unbroken ownership and active use across the record | Long dormancy or parking with no operation |
| Independent evidence | Wayback captures and third-party records predating the claim | No archival footprint |
| Brand-family coherence | Part of a documented portfolio with a shared thesis | An isolated name with no surrounding strategy |
| Claimant conduct | Prior purchase attempts or written acknowledgment of the holder's use | No prior contact; clean first demand |
| Distinctiveness context | Generic or descriptive term no party can monopolize | A coined mark uniquely tied to the claimant |
| Demand integrity | Demand misstates facts (dates, colors, history) on its face | Accurate, narrowly-scoped, well-supported demand |
A defensibility read is an internal assessment, not a legal opinion. It informs whether to hold, document further, or escalate to counsel.
UDRP — the three prongs
A UDRP complaint must prove all three of the following. Senior, good-faith use typically defeats the second and third before the first is even reached.
Reverse domain name hijacking
RDNH is a finding that a complainant abused the process — using a trademark demand or UDRP in bad faith to try to take a domain from its rightful senior holder.
It is supported by the same record that defeats the underlying claim: documented prior use, the claimant's own prior acquisition attempts, written acknowledgments, and demands that misstate the facts. Reserving the RDNH posture early is part of how IPLaw raises the cost of a casual or coercive demand.
Likelihood of confusion is contextual — not a color match
Demands often lead with surface similarity ("same word," "same color"). Trademark analysis is more demanding than that. The relevant question is the overall commercial impression in context, assessed across multiple factors — and senior use weighs heavily.
Strength & distinctiveness
Generic and descriptive terms receive thin protection. No party owns a common word, a single letter, or a ring of dots.
Actual context
Markets, channels, audiences, and disclaimers shape whether confusion is plausible at all.
Actual confusion
Evidence cuts both ways. A claimant's own complaint that mail meant for them reached the senior domain can establish the claimant adopted into a pre-existing identity.
The provenance evidence stack
Provenance is what turns an assertion of ownership into a record. IPLaw assembles, for each asset:
Why provenance is value
For an investor or partner evaluating the network, provenance is the difference between a speculative name and a documented asset. A domain with a deep, verifiable record:
Is materially harder to challenge, and cheaper to defend.
Carries a credible, defensible valuation.
Compounds in value as the record lengthens.
The eCorp IP posture
What a demand asks to transfer is rarely just a domain string. In the eCorp model, each asset is an operated entity with identity, machine interfaces, governance, and a documented purpose — constructed value, not a parked page.
A documented Soul
A public, versioned statement of mission, purpose, and value for each asset — human- and machine-readable.
A public agent card
A standardized profile at /.well-known/agent.json that lets other systems discover and call the entity.
Operated, not parked
Each asset runs under a defined operating model with a standing commitment to defend network assets on the record.
2% to impact
A structural 2% impact commitment is attached to every venture — value created beyond the asset itself.
When a matter needs a lawyer
IPLaw is a strategy and evidence layer, not a substitute for counsel. When legal judgment is required — a UDRP filing, litigation threat, or a close question on the merits — the matter is routed, with its record already assembled, to licensed attorneys and experts through EsquireNet.
What counsel receives is not a blank slate. It is a packet: chronology, provenance, the demand and its defects, a non-admission position, and reserved rights — prepared for review, not as advice.
The handoff packet
Asset identification: owner/controller, registrar, creation date, current use.
Factual timeline: prior use, claimant first-use, filing dates, demand sequence.
Evidence index: registration records, Wayback captures, correspondence, USPTO records.
Posture: reserved rights, RDNH/bad-faith preservation, requested factual support.
Prepared for licensed counsel. Not legal advice.
Questions, answered
Can a later trademark force transfer of an older domain?
Generally not on registration alone. Priority turns on first use; senior, continuous use is the holder's strongest ground. Facts control, and legal questions go to counsel.
Does removing a disputed design element admit anything?
No. Voluntarily adjusting a visual element to remove a surface concern can be done expressly without admission as to the merits.
What if the claimant tried to buy the domain first?
Prior purchase attempts are a voluntary acknowledgment of the holder's rights and a hallmark of the reverse-domain-hijacking fact pattern.
Is IPLaw.com legal advice?
No. It is IP strategy and evidence positioning. It does not create an attorney-client relationship and does not replace counsel.
The IPLaw defense brief
A periodic brief for operators, partners, and counsel: senior-rights playbooks, RDNH and bad-faith case notes, and provenance checklists for digital-asset disputes. Operational materials for review by licensed counsel — not legal advice.
For an active matter, route it through LawyerBot intake to open a defense record.
Not a law firm. Not legal advice.
IPLaw.com is an intellectual-property strategy, evidence-management, and digital-asset defense positioning property within the eCorp network. It is not a law firm, does not provide legal advice, does not create an attorney-client relationship, and does not replace licensed counsel. Doctrine described here is general and for positioning; the facts of each matter control, and matters requiring legal judgment are routed to qualified attorneys in the relevant jurisdiction through EsquireNet.com.
All rights reserved. Every statement should be validated against the specific matter record before publication or transmission.