Cloudflare Speed Test written in Rust, for my practice.
| OS | File to download |
|---|---|
| Windows | cloudflare-speed-test-rust_[Version]_x86_64-pc-windows-gnu.zip |
| Linux | cloudflare-speed-test-rust_[Version]_x86_64-unknown-linux-musl.tar.xz or cloudflare-speed-test-rust_[Version]_x86_64-unknown-linux-musl.tar.gz |
| Mac OS | cloudflare-speed-test-rust_[Version]_x86_64-apple-darwin.zip |
git clone https://github.com/lixiang810/cloudflare-speed-test-rust
cd cloudflare-speed-test-rust
cargo build -r
sudo ./target/release/cfst # sudo if you're using Linux
173.245.48.0/20
141.101.64.0/18
131.0.72.0/22
...
2606:4700:3000::/48
2606:4700:3001::/48
2606:4700:3002::/48
2606:4700:3003::/48
2606:4700:3004::/48
...
sudo cfst -c <FILE>
cfst.exe -c <FILE>
This program will and will only communicate with the Cloudflare server with HTTPS and ICMP Protocol.
Do anything with it at your own risk.
There are two copies of IPv4 IPs built into the program, one of which will be consistent with Cloudflare's IP list. The other one was sent to me by a user, and may be of higher quality than Cloudflare's official list, but its access and security are not yet clear, so use at your own risk.
As with IPv4, the project supports getting available IPs from Cloudflare's IP list, but the vast majority of IPs in this IPv6 list are not available.
I got a list from CloudflareSpeedTest and hardcoded it into the program. This list is very available, but its access and security are not clear.
If you are concerned about IP address security, you can let the program get IPs from Cloudflare (recommended test rounds are set to 20 or more), and if you want to be more efficient, you can let the program use the built-in IP list.
AGPL-3.0
$ claude mcp add CloudflareSpeedTest-Rust \
-- python -m otcore.mcp_server <graph>