Skip to main content
CAS 1 record

CAS 72963-72-5

CAS 72963-72-5 matches 1 EU annex record across Annex II–VI of Regulation 1223/2009.

Chemical identity and properties

PubChem 2D chemical structure for CAS 72963-72-5
CAS 72963-72-5PubChem CID 123622

Imiprothrin

Imiprothrin is mixture of 20% (1R)-cis- (CHEBI:39372) and 80% (1R)-trans- (CHEBI:39373) isomers. It has a role as a pyrethroid ester insecticide. It is a member of cyclopropanes and an imidazolidinone. It contains a (1R)-cis-imiprothrin and a (1R)-trans-imiprothrin. It is functionally related to a chrysanthemic acid. ChEBI

IUPAC name
(2,5-dioxo-3-prop-2-ynylimidazolidin-1-yl)methyl 2,2-dimethyl-3-(2-methylprop-1-enyl)cyclopropane-1-carboxylate
Molecular formula
C17H22N2O4
Molecular weight
318.4 g/mol
Exact mass
318.15795719 Da
XLogP3
2.1
Topological polar surface area
66.9 Ų
Hydrogen-bond donors
0
Hydrogen-bond acceptors
4
Covalent units
1
Defined stereocentres
0

Also known as

PrallePralle TS 4056F73OFA861WYCHEBI:39389S 41311Cyclopropanecarboxylic acid, 2,2-dimethyl-3-(2-methyl-1-propenyl)-, (2,5-dioxo-3-(2-propynyl)-1-imidazolidinyl)methyl esterRefChem:148020
16 more reported names
S-41311S-4056F428-790-6615-873-9Imiprothrin (>85%)UNII-73OFA861WYHSDB 7003Imiprothrin (JAN)EPA Pesticide Chemical Code 004006EC 428-790-6Tox21_112122(2,5-dioxo-3-prop-2-ynyl-imidazolidin-1-yl)methyl 2,2-dimethyl-3-(2-methylprop-1-enyl)cyclopropanecarboxylate[2,5-dioxo-3-(prop-2-yn-1-yl)imidazolidin-1-yl]methyl 2,2-dimethyl-3-(2-methylprop-1-en-1-yl)cyclopropane-1-carboxylateCAS-72963-72-5Imiprothrin, PESTANAL(R), analytical standardSBI-0654150.0001
External database identifiers

Retrieved from NIH PubChem on 2026-08-31 by checksum-valid CAS matching. Chemical properties do not replace the regulatory decision on this page.

Records for CAS 72963-72-5

1 total

How CAS 72963-72-5 is used on this site

CAS 72963-72-5 is the Chemical Abstracts Service identifier used to pin this page to a specific substance. In the current dataset, 1 EU annex record shares this identifier, which helps you cross-check whether the same substance appears under one regulatory context or several.

Use this page when a supplier specification, SDS or raw-material dossier gives you CAS 72963-72-5 and you need to see every linked Annex II–VI record in one place. The entry cards above are the quickest route to concentration limits, warnings, annex placement and product-type conditions.

Frequently asked questions

A substance identified by CAS 72963-72-5 may appear in multiple EU cosmetic regulation annexes when it is subject to different conditions in different contexts. For example, a substance might be restricted under Annex III with specific conditions, and the same CAS might also appear in Annex IV as an approved colorant under separate entry conditions. Each entry must be reviewed individually.

Cross-reference the CAS number against your raw material specification sheets and CoA documents. When a CAS appears in Annex II, verify absence. When it appears in Annex III, verify that concentration limits and product type conditions are met in your formulation. All annex entries sharing this CAS number are listed above.

A CAS number is assigned by the Chemical Abstracts Service (USA) and is globally recognised. An EC number is a European Commission identifier from inventories such as EINECS, ELINCS or the NLP list. Both identifiers may appear in EU cosmetic annex entries. Some substances have both, some have only one, and some older entries may have neither.

The INCI Checker accepts ingredient names, CAS numbers and EC numbers. Check this CAS number directly, then verify the result against supplier specification sheets and every linked annex condition.

Tools & next steps

Check your formula

Scan a full INCI list, then use CAS 72963-72-5 to cross-check any supplier documents behind the matched substances.

INCI Checker

Browse annexes

Browse all EU cosmetic regulation annexes by category.

All annexes

Search by name

Search for INCI names, aliases or related identifiers that sit alongside CAS 72963-72-5 in your documentation.

Search