Independent iPerf engines
iPerf360 uses independent iPerf2 and iPerf3 command-line engines. Those projects are not affiliated with and do not endorse iPerf360. Their names identify interoperable tools only.
Binary provenance
The current Windows Desktop release uses bundled iPerf engines. The iPerf3 Windows amd64 package is pinned to the documented upstream community build used by the Desktop release process; its archive SHA-256 is verified and the executable is exercised before compilation and again from the final packaged payload. The iPerf2 binary remains the validated bundled baseline documented in the Desktop package.
Third-party engine provenance, hashes, licenses, and applicable source/redistribution obligations must be preserved for every published release. The Desktop package binary-provenance record is the authoritative release-specific source.
Included notices are authoritative
The desktop package contains the applicable third-party notice and binary-provenance files, including SHA-256 hashes used to detect accidental binary replacement. This webpage is a public summary and does not replace the files distributed with the software.