Opposition · USPTO

Opposition 91239407

OtherUSPTO

Opposition 91239407 at USPTO between Assurant, Inc. and Dragnet Technologies LLC, over the mark SURRANTY, filed Feb 9, 2018. Status in the office record: other.

View SURRANTYGet this data via the API
Status
Other
Result
Other
Filed
Feb 9, 2018
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Assurant, Inc.

Company trademarks
Respondent

Dragnet Technologies LLC

Timeline

How the case has moved

Dates from the USPTO record and the SURRANTY filing.

  1. SURRANTY filed

    Application 87410317 filed at the USPTO.

  2. Opposition filed

    Assurant, Inc. started opposition 91239407 at USPTO against SURRANTY.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SURRANTYContested87410317USPTO
ASSURANTRelied on75769638USPTO
ASSURANT. ON YOUR TERMS.Relied on77452438USPTO
ASSURANT WORKSRelied on77629946USPTO
ASSURANT. EN SUS TÉRMINOS.Relied on77943700USPTO
ASSURANT SOLUTIONSRelied on78324828USPTO
ASSURANTRelied on78349997USPTO
ASSURANTRelied on78396894USPTO
ASSURANTRelied on78606596USPTO
ASSURANTRelied on78606598USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_99c2952e-0042-4684-83c8-16d13a6e9b76
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_99c2952e-0042-4684-83c8-16d13a6e9b76",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91239407",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-02-09",
  "parties": [
    {
      "name": "Assurant, Inc.",
      "role": "opponent"
    },
    {
      "name": "Dragnet Technologies LLC",
      "role": "respondent"
    }
  ]
}