MISSION DARKNESS™ TITANRF FARADAY FABRIC

Mission Darkness™ TitanRF™ Faraday Fabric offers the next generation of faraday shielding and is certified to military standards MIL-STD-188-125.

Are you intersted in this product?

1300 55 33 24

contact@cdfs.com.au

Quote Request

Download Product Brochure

Use TitanRF Faraday Fabric to Create Your Own RF Shielding Enclosure

Mission Darkness™ TitanRF™ Faraday Fabric offers the next generation of faraday shielding and is certified to military standards MIL-STD-188-125. This compliance measure not only ensures that the fabric shields against high-altitude electromagnetic pulses (HEMPs) and related occurrences, such as coronal mass ejections (CMEs), electrostatic discharges (ESDs), and solar flares, but provides concrete proof to the shielding ability and effectiveness of the fabric.

TitanRF Faraday Fabric uses a copper and nickel composition to achieve an average attenuation of 80dB-120dB from 10MHz-5GHz. This is the same fabric that is used by military and law enforcement forensics investigators to block all wireless signals, including cell phone, WiFi, Bluetooth, and GPS. It is also used by civilians for EMP protection, personal data and identity protection, signal isolation in secure facilities, RF isolation for hardware and software testing, harmful EMF reduction, anti-credit card skimming, digital privacy, and more.

The fabric can be easily cut, sewn, or taped to surfaces for creating DIY faraday cages or RF shielding enclosures. The fabric comes with a sample of TitanRF Faraday Tape which can be used to tape together layers of TitanRF Faraday Fabric. Once the faraday enclosure is constructed, you can use our faraday testing apps to confirm your design is properly shielding (see below). Read our TitanRF Faraday Fabric FAQ for usage tips and answers to commonly asked questions regarding using the material for faraday cages and RF shielded enclosures. *Contact us if you need custom dimensions or a full roll or fabric.

/* Omit closing PHP tag at the end of PHP files to avoid "headers already sent" issues. */