MIL-STD-810 Explained: What 810G and 810H Testing Actually Means

A buyer's guide to environmental test standards from NCS Technologies

“MIL-STD-810 certified” appears on the spec sheet of almost every product sold as rugged. The phrase is doing a lot of work, and some of it is misleading. This guide explains what the standard actually is, what changed between 810G and 810H, which test methods matter for computing hardware, and what to ask a vendor before you accept the claim.

What MIL-STD-810 is — and what it is not

MIL-STD-810 is a U.S. Department of War standard titled Environmental Engineering Considerations and Laboratory Tests. It describes how to work out which environmental stresses a piece of equipment will see over its service life — temperature, humidity, altitude, vibration, shock, sand, salt fog, rain, and so on — and it defines laboratory test methods for reproducing those stresses.

Three things follow from that, and they matter when reading a data sheet:

It is not a certification. No agency or laboratory “certifies” a product to MIL-STD-810. A vendor tests (or has a lab test) the product against selected methods and reports the results. “810 certified” is a marketing phrase; “tested to MIL-STD-810H Method 514.8, Procedure I” is a fact you can verify.
It is a menu, not a checklist. The standard contains 29 test methods. Almost no product is tested to all of them, and the standard explicitly expects each program to tailor — to select the methods and severity levels that match the real deployment. A laptop tested for drop and dust and a shipboard server tested for vibration and salt fog can both truthfully say “MIL-STD-810 tested” while having nothing in common.
Severity is adjustable. Each method has procedures and parameters (temperature range, vibration profile, shock pulse, duration). Two vendors can both claim Method 501 (high temperature) with one tested at 40 °C operating and the other at 60 °C. The number of the method tells you very little without the levels.

The practical consequence: the value of a MIL-STD-810 claim lies entirely in the details behind it.

810G vs 810H: what changed

MIL-STD-810G was released in 2008 (Change 1 in 2014). MIL-STD-810H replaced it in January 2019 (Change 1 in 2022) and is the current revision. Buyers still write “810G” into specifications out of habit, and search for it more often than 810H, so it is worth being precise about the difference:

Same structure, same method numbers. Each method keeps its number and its revision suffix increments — vibration went from 514.7 (G) to 514.8 (H), shock from 516.7 to 516.8. A product tested to a G-revision method is not invalidated by H.
Refinements, not a new philosophy. 810H tightened test tailoring guidance, updated several vibration and shock profiles to reflect newer platform data, clarified climatic test procedures, and expanded guidance on multi-exciter vibration testing. For most computing hardware the practical test levels are similar between G and H.
What to specify today. New programs should reference 810H. If you have equipment qualified under 810G, ask whether the vendor has re-tested to H or can show that the G results envelop the H requirements for your methods.

The test methods that matter for rugged servers and workstations

Of the 29 methods, roughly a dozen are routinely relevant to computing equipment. The table below describes each in plain terms, with the failure it is designed to find.

Method (810H)	Test	What it finds in a server
500.6	Low pressure (altitude)	Cooling and drive behaviour at reduced air density; aircraft and high-altitude deployments
501.7	High temperature	Thermal throttling, component derating, fan margin; operating vs storage limits
502.7	Low temperature	Cold-start failures, LCD and battery behaviour, lubricant stiffening in fans and drives
503.7	Temperature shock	Solder-joint and connector fatigue from rapid transitions (e.g., hangar to flight line)
506.6	Rain	Water ingress through ports, seams and fan openings
507.6	Humidity	Condensation, corrosion, dielectric breakdown over extended exposure
509.7	Salt fog	Corrosion of connectors, fasteners and PCB finishes in maritime environments
510.7	Sand and dust	Abrasion, filter clogging, fan bearing wear, ingress into optical and connector surfaces
512.6	Immersion	Sealed-enclosure integrity (rarely relevant to rack servers; common for handhelds)
514.8	Vibration	Drive and card retention, connector fretting, fastener loosening on vehicle, ship and aircraft profiles
516.8	Shock	Survival of transit drops, handling shocks and operational impacts; functional vs crash-hazard procedures
521.4	Icing / freezing rain	Ice loading on exposed connectors and vents
528.1	Mechanical vibration, shipboard	Shipboard equipment vibration (Type I environmental, Type II internally excited)

For rack-mount servers the methods that most often decide pass or fail are 514 (vibration), 516 (shock), 501/502 (temperature extremes) and 510 (sand and dust). Vibration and shock are also the ones where the difference between “operating” and “non-operating” testing matters most: a server that survives a shock powered off but drops its drives when running has passed a very different test from one that keeps serving data throughout.

Reading a MIL-STD-810 claim: five questions

Which methods, which procedures? “Tested to 810H” means nothing on its own. Ask for the method numbers and the procedure within each (e.g., 516.8 Procedure I, functional shock).
At what levels? Temperature range, vibration profile and duration, shock pulse and g-level. Ask whether the levels were tailored to your platform or taken from the standard’s defaults.
Operating or non-operating? Was the system running and functional during the test, or just switched off and inspected afterwards?
Who tested it? In-house lab, or an accredited independent lab? Is the test report available under NDA?
Which configuration? The exact chassis, drives and cards tested. A result on a base configuration does not automatically cover a system with different drives, GPU cards or a different rail kit.

A vendor that can answer all five in writing has a real qualification. One that answers with the marketing phrase does not.

Related standards you will see alongside 810

MIL-STD-461G — electromagnetic interference and compatibility (emissions and susceptibility). Separate standard, separate testing; required on most DoD platforms.
MIL-S-901D — high-impact shock for shipboard equipment, tested on a lightweight or medium-weight shock machine or, for the heaviest equipment, on a floating barge with underwater explosive charges. Grade A means the equipment must remain operational after the shock, not merely survive it.
MIL-STD-1275 / MIL-STD-704 — power quality on military ground vehicles and aircraft respectively.
RTCA DO-160 — the civil-aviation counterpart to 810 for airborne equipment.
IP ratings (IEC 60529) — ingress protection against dust and water; often quoted together with 810 but a different standard with a simpler pass/fail structure.

How NCS tests

NCS designs and manufactures rugged servers and storage in its own facility in Manassas, Virginia, with in-house mechanical and integration labs for validation testing, and uses accredited independent laboratories, E-Labs and Element US Space & Defense, for formal environmental qualification: functional, performance, noise and radio emissions, shock, drop, pitch, roll and barge shock. The rugged mission server family has been tested to MIL-STD-810H Methods 501.7 (high temperature), 502.7 (low temperature), 507.6 (humidity) and 516.8 (shock); the procedures, levels and operating conditions for each test are documented in the test reports, which are available to customers under NDA. For shipboard shock, the 3U rugged server has passed MIL-S-901D Grade A heavyweight (barge) testing, the most demanding shock test in the shipboard family, and the other rugged servers are tested to 901D as part of a rack assembly. Configurations are available designed to meet MIL-STD-810H and MIL-STD-461G.

If you are writing an environmental specification for a program, or trying to compare two vendors’ 810 claims, talk to our engineering team — the five questions above are the ones we answer for our own products.