What an IP rating actually promises, and what it quietly does not

Both digits explained, and the conditions the rating does not cover.

An IP rating promises that an enclosure has passed one specific, narrowly defined laboratory test against solid objects and water, and it quietly does not promise anything at all about how that same enclosure behaves under chemicals, pressure washing, sustained submersion, repeated flexing, or any condition the standard's particular test procedure did not happen to include.

Why two digits promise less than they sound like they do

The IP Code reduces a great deal of real-world protection down to just two numbers, and each one answers a single, separate question. The first digit describes protection against solid objects and dust, running from no protection at all up through a rating that keeps out dust fine enough that a person could not see it settling on a surface. The second digit describes protection against water, running from no protection up through resistance to powerful jets and, at the top of the common scale, temporary submersion to a stated depth. A rating like IP67 answers both questions at once, dust-tight and safe against brief submersion to a metre, and it is genuinely useful shorthand for comparing two enclosures against the same fixed tests. What the two digits do not do is describe the enclosure in general, because each digit only reports the result of the one specific test procedure behind it, and any condition the test procedure did not include is simply outside what the rating speaks to at all, in either direction.

The water-resistant-wristwatch comparison

A wristwatch stamped water resistant to fifty metres will usually survive an accidental dunk in a sink without complaint, yet the same manufacturer will often warn against wearing it in a hot shower or a swimming pool, which sounds contradictory until the actual test behind the number is understood. The rating describes one specific static test, a fixed pressure applied under controlled, unmoving conditions in a laboratory, and it says nothing about what happens when a warm shower's temperature swings expand and contract the watch's seals, or when swimming strokes flex the strap and stress the case in ways the static test never modelled. The number on the case is completely honest about what it tested, and completely silent about everything it did not, and a wearer who reads "fifty metres" as "safe in any wet situation up to fifty metres deep" has extended a specific, narrow promise well past the point where the manufacturer actually stood behind it.

Why the second digit hides more assumptions than the first

The water-resistance digit in particular carries more hidden assumptions than most people reading a rating ever notice, because the standard behind the highest common ratings does not fix a single universal test the way the lower ratings do. IP67's test is genuinely standardised, one metre of water for thirty minutes, so any two products both rated IP67 have actually survived the identical test. IP68 has no such fixed depth or duration written into the standard at all; instead, the manufacturer states whatever depth and duration they chose to test and declare, subject only to it exceeding IP67's own baseline. Two components can both be marketed as IP68 and have been proven under genuinely different conditions, one tested to a metre for an hour and another tested to several metres for a full day, with nothing in the bare rating itself distinguishing between them unless a buyer goes looking for the manufacturer's own stated test parameters behind the label.

One figure worth keeping in mind

IP67's water-resistance test is fixed at one metre of depth for thirty minutes by the standard itself, while IP68, the rating one step above it, leaves both figures entirely to the manufacturer's own declaration, meaning two IP68 products can differ from each other by a wide margin in actual proven capability while sharing the identical two digits on their datasheets.

What this does not explain

Beyond the ambiguity hiding inside the higher water-resistance digits, the IP Code as a whole is silent about an entire category of conditions that have nothing to do with dust or plain water at all. It says nothing about resistance to oils, solvents, or cleaning chemicals, which can soften or crack a seal that handles plain water perfectly well, since the standard's test liquid is water and nothing else. It says nothing about the pressure and temperature of a jet from an industrial pressure washer, a genuinely different and much harsher hazard than the standard's own water-jet test, which is why a separate rating exists specifically for that case rather than being folded into the ordinary scale. It says nothing about how a seal ages under years of ultraviolet exposure, repeated temperature cycling, or the countless small flexes a cable entry absorbs over a working life, since the standard's test is a single pass-fail event performed once on a new, unused sample rather than a measure of how that same protection holds up over time. An enclosure can leave the factory genuinely rated to a demanding standard and still fail years later for reasons the rating was never designed to predict, because the rating describes a moment, not a lifetime.

What follows from this

The practical response is to treat an IP rating as the start of a supplier conversation rather than the end of one, particularly at the higher end of the water-resistance scale where the standard itself leaves room for genuinely different real-world performance behind an identical label. Reading past the two digits to the manufacturer's actual declared test depth and duration, and checking whether the intended application involves anything the test never modelled, chemical exposure, sustained rather than brief immersion, high-pressure cleaning, or repeated flexing at a cable entry, is the only way to know whether a rating that looks sufficient on paper is actually sufficient for the job it is being asked to do. None of this makes the IP Code a poor standard, since a shared, repeatable test that lets two enclosures be compared fairly is genuinely valuable, it only makes the two digits a smaller promise than the confidence they tend to inspire, and treating them as a starting question rather than a finished answer is what keeps that confidence honest.