It supports a dust-tight claim for the tested configuration, not lifetime immunity to abrasion, damaged cables, or open ports.
Factory ingress protection guide
What an IP67 Sensor Test Actually Checks at the Factory
IP67 checks an enclosure against dust and temporary water immersion under defined conditions. It does not certify every environmental risk, every installed connector, or every sensor function.
Short answer
6 means dust-tight under the applicable IP6X test. 7 means temporary immersion under the applicable IPX7 test. The rating alone does not say whether every shipped sensor was immersed or how production conformity is controlled.
Background photo: Sergey Sergeev / Pexels.
It asks whether harmful water ingress occurs under the specified test. It is different from jets, hot washdown, and continuous submersion.
Type tests, sample audits, 100% leak screens, and final functional tests are separate assurance layers.
Use four questions to turn IP67 into a usable requirement.
A buyer does not need to become a test-lab specialist. The goal is to identify the exact assembly, the evidence level, and the real exposure before accepting a broad “waterproof” statement.
Ingress protection of the enclosure against dust and temporary immersion in the tested state.
Ask for the standard and exact IP designation.Confirm integral cable, mated M8/M12 connector, cap, gland, O-ring, housing revision, and assembly instructions.
Match the report to the ordered model.The rating does not answer this. Separate design qualification, periodic samples, leak screening, and functional testing.
Request a written coverage matrix.Pressure wash, hot water, chemicals, continuous immersion, vibration, and cable flex need separate evidence.
Describe the actual exposure in the RFQ.An IP code is an enclosure rating, not a complete reliability certificate.
What IP67 can tell you
The enclosure design has been evaluated or declared for dust protection and temporary water immersion under specified conditions. The claim must still be tied to a defined product and assembly state.
IEC 60529 classifies degrees of protection provided by enclosures. For sensor buyers, that makes IP67 useful but narrow. A sensing face can be damaged, a cable can be cut, a seal can be attacked by cleaner, or a plug can be left loose even when the product family carries an IP67 declaration.
The practical question is not only “Is this sensor IP67?” Ask: Which exact assembly was tested? Which IEC 60529 edition is referenced? Was the evidence a type test, a sample audit, or a 100% line screen? What happened after exposure?
Plain-language boundary: IP67 does not automatically prove pressure-wash resistance, permanent submersion, chemical compatibility, EMC immunity, cable-flex life, sensing accuracy, or correct PLC operation.
For a broader explanation of the complete code, read the industrial sensor IP-code guide. This page focuses on what factory evidence sits behind an IP67 claim.
Primary reference: IEC 60529 consolidated Edition 2.2, Degrees of protection provided by enclosures (IP Code).
Why this matters: IP67 is not one “waterproof score.” Dust and water are tested differently. A missing digit shown as X, such as IPX7, must not be invented or assumed.
IP6X dust protection
What the dust test actually asks
The IP6X portion challenges a defined enclosure with controlled fine dust. The purpose is to determine whether dust enters in a way that conflicts with the stated protection level. It does not recreate every quarry, flour room, battery plant, or metal-powder process.
1
Identify the specimen
Record model, housing, cable or connector, unused ports, caps, orientation, and revision.
2
Prepare the declared assembly
Install seals and closures according to the controlled procedure. Pressure conditions depend on the applicable method.
3
Apply the standardized dust challenge
Use a controlled chamber, dust, exposure time, and specimen condition rather than an undefined workshop dust test.
4
Inspect and record the result
Document ingress observations and any visual, electrical, or functional assessment that the product plan requires.
Not covered automatically: abrasive wear, conductive powder behavior, sticky dust, damaged jackets, loose glands, chemical attack, or sealing life after vibration.
IPX7 temporary immersion
The outside gets wet. The test checks for harmful ingress.
IPX7 evaluates a configured enclosure during temporary immersion under prescribed conditions. It is often summarized as approximately 1 m for 30 minutes, but this shorthand is not a universal field-use allowance. The detailed setup depends on IEC 60529 and the enclosure dimensions.
The report should make clear how the specimen was installed, how long it was exposed, and how the result was assessed. A visual inspection, opening, insulation check, or functional test must be documented if it was performed; do not assume it from the IP mark alone.
Product-specific example only: some manufacturer manuals state a 1 m / 30 minute condition for a particular product. That wording cannot be copied automatically to every sensor or installed connector.
Further context: TÜV SÜD ingress-protection testing and a Siemens manual example.
Simplified test concept, not a dimensional test drawing
Defined water condition
ExposureTemporary immersion, not continuous operation.
Pass questionDid ingress cause harmful effects under the stated assessment?
Do not rank water digits as one simple ladder: IPX5/IPX6 jets, IPX7 temporary immersion, IPX8 manufacturer-defined continuous immersion, and high-pressure/high-temperature cleaning represent different exposures. Read the exact declared ratings and test conditions.
Factory evidence ladder
“Factory tested to IP67” can describe four different activities.
Each layer has value. The mistake is treating one layer as proof of all the others.
Design or type test
Defined samples and configuration are tested during product qualification or after a relevant design change.
Supports the qualified design, not proof that every unit was immersed.Periodic or lot audit
Samples are checked to monitor continuing production or a particular review period.
Supports sampled consistency, not a 100% shipment pass record.100% production leak screen
Air pressure, vacuum, or pressure-decay methods can detect assembly leaks quickly when validated and controlled.
Unit-level screening is not automatically a full IEC dust-and-immersion test.Final functional test
Power, output, indicator, communication, or sensing behavior is checked according to the production plan.
Electrical function is separate from ingress protection unless both are documented.Useful supplier wording is precise: “100% air-leak screened to defined limits” is different from “100% IEC 60529 IP67 immersion tested.” Ask for method, limits, validation basis, equipment control, and serial or lot traceability.
Controlled manufacturing
A robust supplier controls the sealed design before and after the laboratory test.
A test certificate is useful only when production keeps making the same controlled assembly.
Approve the sealed design
Lock housing, cable/connector, seal, resin, potting, adhesive, cap, and process revision.
Control critical inputs
Manage approved seals, molded parts, cables, connectors, compounds, and suppliers.
Control assembly
Define cleanliness, positioning, cure, weld, torque, potting volume, and inspection limits.
Screen production
Use visual, dimensional, torque, process-signal, or validated leak checks where appropriate.
Qualify and audit
Run IP6X/IPX7 testing at release, after key changes, or according to a risk-based schedule.
Release with traceability
Connect lot or serial identity to configuration, inspection status, test records, and deviations.
What buyers should verify
The qualified sample and the shipped sensor need a controlled connection.
Ask how xsz sensor or any supplier links the approved design to production. The answer should be about records and controls, not only a logo on a certificate.
- Which model codes and connection variants are covered?
- Which changes trigger reassessment or requalification?
- How are failed or reworked units identified and retested?
- Can the outgoing lot be linked to final inspection records?
- Which ingress checks are 100%, sampled, or design-level only?
The tested assembly matters
A sealed sensor body can still become a leaking installation.
Industrial sensors may include a cable overmold, potted rear end, M8 or M12 connector, protective cap, cable gland, indicator window, teach button, or lens. Each interface can change what the rating means.
Integral cable
Record cable material, length, strain relief, bend conditions, pull, temperature, and chemical exposure.
M8 / M12 plug
Confirm compatible cordset, gasket, mating state, tightening torque, and treatment of unused ports.
Cable gland
Check approved cable diameter, insertion, torque, clamp condition, and whether assembly occurs at the factory or in the field.
Housing features
Window, button, seam, weld, adhesive, label, and potting changes may require technical review or requalification.
Procurement implication: A connectorized sensor may simplify maintenance, but the sealing result depends on a compatible, correctly assembled connection. Compare M8 and M12 sensor connectors and review the M12 pinout guide before finalizing the cordset.
Do not over-read IPX7
Temporary immersion is not high-pressure washdown.
A washdown lance creates dynamic pressure at seams and connectors. Hot water, detergent, rapid temperature change, repeated cycles, and operator distance add stresses that a temporary static immersion claim does not answer.
Pressure and nozzle
State pressure, distance, angle, and flow pattern.
Water temperature
Include hot-water exposure and thermal shock.
Chemistry
Name detergents, concentration, dwell, and rinse.
Frequency
One test does not predict thousands of wash cycles.
For continuous or deeper immersion, compare IP67 and IP68 conditions. IPX8 conditions are manufacturer-defined, so depth, time, liquid, temperature, cable state, and post-test criteria must be recorded.
Close the evidence gaps
Use the real exposure to decide what else must be tested.
Many failures blamed on “waterproofing” actually begin with chemistry, pressure, cable damage, mechanical load, or electrical noise.
| Actual exposure | Why IP67 alone is not enough | Better sourcing or validation action |
|---|---|---|
| High-pressure or hot washdown | IPX7 immersion is not a dynamic jet, rotating spray, steam, or hot-cleaning test. | Specify nozzle pressure, distance, temperature, cycle, detergent, and relevant declared water ratings. |
| Continuous immersion or flooded pit | IPX7 is temporary immersion. It does not define continuous operating depth or time. | Request a documented IPX8 condition or a product-specific submersion validation. |
| Coolant, oil, disinfectant, salt, or solvent | The water-ingress test does not establish material compatibility with process chemicals. | Provide chemical name, concentration, temperature, contact time, and cleaning cycle. |
| EMC noise and PLC faults | Ingress protection does not measure electrical immunity, grounding quality, or controller compatibility. | Review EMC evidence, wiring, shielding, supply, output type, and machine-level testing. |
| Impact, vibration, cable flex, and abrasion | A seal can pass initially and fail after mechanical damage or repeated movement. | Define shock, vibration, bend radius, flex cycles, pull, mounting stiffness, and collision risk. |
Ingress protection and electromagnetic compatibility answer different questions. See why EMC matters in industrial sensors, and review sensor cable length and routing before installation.
Buyer evidence checklist
What a useful IP67 report should let you verify
The document should connect the tested specimen to the model you will receive. The evidence depth can scale with application risk, but the identity and scope should never be vague.
Names IEC 60529 and the edition or test basis used, rather than only saying “waterproof.”
Shows model, housing, cable/connector, cap, revision, photos, and any family-coverage logic.
States whether the connector was mated, ports capped, seals installed, and entries assembled as instructed.
Separately records the dust and water portions, key conditions, observations, and outcome.
Explains visual inspection, opening, insulation, electrical, or functional checks actually performed.
Allows the report source, sample identity, date, and connection to the current design to be checked.
Separates type testing, periodic samples, 100% leak screening, and final function testing.
States what variants are covered and which material, connector, seal, process, or tooling changes trigger review.
Warning signs: an undated certificate, a different supplier identity, no exact model or connector state, only one IP digit tested, no way to verify the laboratory, or one old report claimed to cover every housing and connection variant.
Ready-to-use RFQ language
Write the environmental requirement so a supplier can answer it.
“IP67 required” leaves open the assembly state, evidence, production coverage, and real exposure. Add these details before comparing quotations.
For broader supplier qualification, use the industrial sensor supplier selection guide.
Example specification
Required assembly: The quoted sensor shall be declared IP67 under IEC 60529 for the exact model, housing, and named cable or mated connector configuration. Identify the standard edition, approved cordset or cap, sealing element, tightening instruction, and unused-port condition. Before first shipment, provide the current data sheet, installation instructions, manufacturer declaration or available type-test evidence, and a written matrix showing design qualification, periodic audit, 100% leak-screen, and final functional-test coverage. Separately state suitability for the specified washdown, liquid, chemical, temperature, vibration, and cable-flex conditions.
Factory audit questions
Questions that reveal the real test program
Use these during supplier qualification or a critical wet-environment project. A strong answer names controlled documents, coverage, limits, and traceability.
Which exact model codes and connection states does the IP67 evidence cover?
Ask to see the configuration list, report identity, photos, caps, cordsets, and revision.
Which tests are internal, external-laboratory, sampled, or 100%?
Separate formal ingress qualification from end-of-line function and non-destructive leak screening.
How is a production leak-screen limit established and maintained?
Review correlation to the sealed design, gage control, calibration, master parts, and reaction plan.
Which changes trigger requalification?
Include seal source, cable supplier, resin, potting, weld settings, connector, color, housing tool, and molding process.
How are failures, rework, and retest controlled?
Verify containment, rework authorization, retest method, first-pass status, and lot traceability.
What application limits remain outside IP67?
Request written limits for jets, chemicals, UV, temperature cycling, flex, impact, vibration, and continuous immersion.
Avoid expensive assumptions
Eight common IP67 purchasing mistakes
Most are easy to prevent when the PO names the assembly, evidence, and application.
Name the IP code, tested assembly, exposure, and required evidence instead.
Immersion and jet exposure stress the enclosure in different ways.
Define depth, time, liquid, temperature, cable path, and the manufacturer-stated condition.
Connector geometry, sealing ring, torque, cap, and compatibility can change the installed result.
Match model, housing, cable, connector, revision, and both IP digits to the order.
A 100% electrical test is not automatically a 100% ingress test.
Those risks require separate standards, material evidence, or application validation.
Confirm configuration, production coverage, and change control before release.
Application review
Is a standard IP67 sensor enough for your machine?
Send the complete model need, connection state, mounting, liquid exposure, washdown or immersion details, temperature, quantity, destination market, and required document set. xsz sensor can review whether a standard declaration is suitable or whether sample testing is needed.
Request an ingress-protection review
Include these details
- Target and sensing requirement
- Integral cable or exact connector/cordset
- Water depth, time, pressure, and frequency
- Chemical name, concentration, and temperature
- Mounting drawing and cable route
- Evidence, sampling, and traceability requirement
Frequently asked questions
Common questions about IP67 sensor testing
Does IP67 mean every sensor is water tested before shipment?
No. IP67 states an enclosure-protection level, not production-test coverage. The claim may be supported by design testing, periodic samples, a 100% non-destructive leak screen, or another documented control plan. Ask what is performed on every finished unit.
What does the IP6X test check on a sensor?
IP6X checks dust ingress protection for the enclosure under the applicable standardized dust test. It supports a dust-tight assembly in the tested configuration, but it does not prove resistance to abrasion, chemicals, damaged cables, open connectors, or long-term mechanical wear.
What does IPX7 mean in practical terms?
IPX7 is temporary immersion under defined conditions. It is commonly summarized as approximately 1 m for 30 minutes, but the detailed setup follows IEC 60529 and the enclosure dimensions. It is not a pressure-jet, hot-washdown, or permanent-underwater rating.
Is IP67 better than IP66 for washdown?
Not automatically. IPX6 and IPX7 address different water exposures, so they should not be ranked as one simple scale. Specify the actual washdown pressure, nozzle distance, temperature, cycle, and cleaning chemistry, then choose the relevant declared ratings and evidence.
Can an IP67 sensor be used underwater permanently?
Do not assume so. IPX7 covers temporary immersion. Continuous immersion needs a manufacturer-stated IPX8 condition or product-specific evidence defining depth, duration, liquid, temperature, cable configuration, and operating limits.
Will an IP67 M12 sensor remain IP67 with a third-party cordset?
Only when the sensor manufacturer permits the mating component and the complete connection is installed as instructed. Plug geometry, sealing ring, torque, cable, and unused-port treatment can affect the result. Confirm compatibility in writing for critical service.
Does IP67 test sensor detection accuracy?
No. IP67 is an enclosure-ingress classification. A supplier may run a separate function check, but the IP rating itself does not define sensing distance, switching accuracy, repeatability, response time, output logic, or PLC compatibility.
Can an air-leak test replace an IP67 test?
An air-leak or pressure-decay screen can be a strong production control, but it is not automatically equivalent to the full IEC IP6X and IPX7 procedures. The supplier should state its method, limits, coverage, validation or correlation basis, and traceability.
What documents should I request before buying IP67 sensors?
Request the current data sheet, installation instructions, complete IP designation, tested configuration, standard and edition, type-test report or manufacturer declaration, production-test coverage statement, connector and cable compatibility, and any additional evidence for washdown, chemicals, UV, flex, or continuous immersion.
Technical references
Standards and independent test context
Use the current standard and the exact product documentation for final engineering decisions.
- IEC 60529:1989+AMD1:1999+AMD2:2013 CSV, Edition 2.2, Degrees of protection provided by enclosures (IP Code).
- TÜV SÜD ingress-protection testing, overview of solid-object and water ingress test services.
- TÜV SÜD ingress-protection laboratory, separate dust, jet, high-pressure/high-temperature, and immersion capabilities.
- UL Solutions enclosure and component certification, IP evaluation context for enclosures and accessories.
- UL Solutions watertightness verification, why application-specific water exposure can require evidence beyond a baseline IP claim.
- Siemens product-manual example, product-specific IP67 immersion wording; not a universal sensor condition.
- ifm product documentation example, showing model-specific ingress and installation details.