FreeGuard Testing Methodology

마지막 확인: 2026-04-15

This page describes how FreeGuard tests VPN performance, security, and reliability across all server regions. Our testing methodology is transparent and reproducible.

Tools We Use

iperf3
Measures raw TCP/UDP throughput between the test client and a controlled iperf3 server placed at each target location.
ping / mtr
Measures round-trip latency and hop-by-hop packet loss using ICMP echo requests over a 60-second window.
DNS 유출 테스트
이 검사는 freeguardvpn.com의 A 쿼리를 표시된 각 공용 DNS-over-HTTPS 제공업체에 보내고 응답 메타데이터만 표시합니다. 기기의 재귀 DNS 확인자나 요청의 VPN 터널 사용 여부는 확인할 수 없습니다.
WebRTC leak checker (headless Chromium)
Automates a headless Chromium session to capture local and public ICE candidates and compares them against the expected VPN IP.
IPv6 유출 테스트
이 단일 듀얼 스택 엔드포인트만으로 IPv6가 터널링되거나 차단되었는지 증명할 수 없습니다. 실제 확인에는 각 네트워크에서 관리하는 IPv6 전용 프로브가 필요합니다.
Wireshark / tshark
Captures live traffic during each test run to confirm all packets flow through the encrypted tunnel and none bypass it.

Test Environment

Hardware
Dedicated bare-metal test machines with 8-core CPUs, 32 GB RAM, and 1 Gbps NIC — ensuring the client is never the bottleneck.
Network Conditions
Tests are run across multiple ISPs per source location, covering fiber, cable, and 4G/LTE connections to capture real-world variance.
Geographic Distribution
Tests are executed from 10+ source countries across Asia, Europe, and North America to reflect global user conditions.

Test Protocol

Each server location follows this standardized step-by-step procedure:

Connect to target VPN server
Establish the tunnel using the FreeGuard client. Wait 10 seconds for routing tables to stabilize.
Verify tunnel IP
Confirm the public IP matches the expected VPN server egress address before any measurements begin.
Run speed test (iperf3)
Execute a 30-second bidirectional iperf3 test. Record download, upload, and jitter.
Measure latency (ping/mtr)
Send 100 ICMP packets to the target. Record min, avg, max RTT and packet loss percentage.
DNS 유출 테스트
DNS 유출을 조사하려면 실제 네트워크에서 OS, 브라우저, VPN의 DNS 설정을 패킷 캡처 또는 확인자 로그와 비교하세요.
Run WebRTC leak test
Launch headless Chromium, collect ICE candidates, and assert no real IP is exposed.
IPv6 유출 테스트
이 단일 듀얼 스택 엔드포인트만으로 IPv6가 터널링되거나 차단되었는지 증명할 수 없습니다. 실제 확인에는 각 네트워크에서 관리하는 IPv6 전용 프로브가 필요합니다.
Disconnect and reset
Tear down the tunnel, flush routing tables, and wait 30 seconds before the next run.
Repeat 3× and average
Perform the full sequence 3 times per session. Compute the mean for speed and latency; treat any single leak as a failure.

Test Schedule

Tests are conducted monthly across all server regions. Results are updated on corresponding tool, gaming, and streaming pages within 48 hours of completion.

Sample Size

Each server location is tested a minimum of 3 times from at least 2 different source locations. Final metrics are the arithmetic mean of all runs, with outliers (±2σ) discarded.

How to Reproduce Our Results

You can verify our results independently using the same open-source tools. Here is the minimal setup:

마지막 확인: 2026-04-15