Fragrance avoidance
Not a strong fit for fragrance avoidance because it carries Fragrance.
The ingredient itself is a fragrance-linked signal, so it is better treated as an avoid case when fragrance exposure is the main concern.
Benzene, 2-methoxy-1-(1-methoxyethoxy)-4-(2-propen-1-yl)-
EPA CPDat observed this chemical in 0 composition records across product categories including unclassified products.
Research docs0Claims0Sources5FunctionFragranceIdentifierDTXSID50867529
Concern score
Not assessed — no hazard data yet.
How we scored this
The concern value reflects this ingredient's chemical identity — its hazard profile from the published classifications and regulatory status below — not the safety of a product it appears in. A score near 40 is the baseline for ingredients with no specific signal (water scores 40 by design), so a mid-range value is not a safety verdict.
Concern score 5/100 · limited confidence.
Where it appears
Prevalence of Benzene, 2-methoxy-1-(1-methoxyethoxy)-4-(2-propen-1-yl)- in our catalog (epa_cpdat).
Brands
1
Typical roles
Fragrance
Suitability
Context-specific fit derived from published classifications and the current ingredient evidence profile.
Avoid
Evidence read
The published evidence profile currently shaping this ingredient record.
No evidence profiles are attached to this ingredient yet.
Linked research
Primary documents currently linked to this ingredient record.
No linked research documents are attached to this ingredient yet.
Extracted claims
Structured claim signals pulled from linked ingredient research.
No extracted claims are attached to this ingredient yet.
Regulatory status
Published jurisdiction-level classifications and regulatory designations for this ingredient.
US
EPA
EPA CPDat observed this chemical in 0 composition records across product categories including unclassified products. EPA CPDat classifies this chemical for functional uses including Fragrance.
Effective: 2019-12-20View source →
US
FDA
openFDA substance registry classifies this ingredient as chemical.
Effective: 2026-05-24View source →