Opposition · USPTO

Opposition 91305310

OtherUSPTO

Opposition 91305310 at USPTO between Salesforce, Inc. and Cyber Defense Center, over the mark FORCE LABS, filed Feb 18, 2026. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 18, 2026
Marks involved
33
Parties

Who is involved

The parties as named in the office record.

Opponent

Salesforce, Inc.

Respondent

Cyber Defense Center

Timeline

How the case has moved

Dates from the USPTO record and the FORCE LABS filing.

  1. FORCE LABS filed

    Application 98931402 filed at the USPTO.
  2. Opposition filed

    Salesforce, Inc. started opposition 91305310 at USPTO against FORCE LABS.
Marks

Marks involved

1 contested mark, 32 marks the challenger relies on.

MarkRoleApplicationOffice
FORCE LABSContested98931402USPTO
SALESFORCE.COMRelied on75836332USPTO
SALESFORCERelied on76575119USPTO
FORCE.COMRelied on77242437USPTO
DREAMFORCERelied on78509506USPTO
SALESFORCERelied on78713215USPTO
SALESFORCERelied on78713221USPTO
SALESFORCERelied on78713222USPTO
FORCERelied on85046219USPTO
SURVEY FORCERelied on85140341USPTO
VISUALFORCERelied on85166166USPTO
SCHOOLFORCERelied on85183487USPTO

+21 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

GET /v1/proceedings/{id}
ID=prc_578289a8-3d4d-4863-ac1e-52ce62b353fd
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_578289a8-3d4d-4863-ac1e-52ce62b353fd",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91305310",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-02-18",
  "parties": [
    {
      "name": "Salesforce, Inc.",
      "role": "opponent"
    },
    {
      "name": "Cyber Defense Center",
      "role": "respondent"
    }
  ]
}