Generated by Python Test Suite | Date: Tue Sep 15 05:06:33 2026 | Debug Log
#
ip/host
port(range)
ping
IPv6
iperf3 -c (TCP)
--reverse (TCP)
iperf3 -c (UDP)
--reverse (UDP)
Congestion ⓘ
1
148.230.59.38
30002-30009
bbr/cubic
2
176.23.128.102
30002-30009
bbr/cubic
3
lg.gigahost.no
9205-9240
N/A
Select a server to view details
148.230.59.38 (FortiSASE)
Port
IPv6
iperf3 -c (TCP)
--reverse (TCP)
iperf3 -c (UDP)
--reverse (UDP)
30002
30003
30004
30005
30006
30007
30008
30009
Target: 148.230.59.38 Range: 30002-30009 Total Scanned: 668 Open Ports: 13
Note: Port scanning is an auxiliary tool and may not always be 100% accurate due to firewalls, network policies or other limitations.
A "CLOSED" status or missing port here does not guarantee the service is down.
The iperf3 tests (see the iperf3 Results tab) are always attempted on the configured ports regardless of these scan results.
Port
Status
443
OPEN
2000
OPEN
5060
OPEN
30000
OPEN
30002
OPEN
30003
OPEN
30004
OPEN
30005
OPEN
30006
OPEN
30007
OPEN
30008
OPEN
30009
OPEN
30100
OPEN
176.23.128.102 (FortiSASE)
Port
IPv6
iperf3 -c (TCP)
--reverse (TCP)
iperf3 -c (UDP)
--reverse (UDP)
30002
30003
30004
30005
30006
30007
30008
30009
Target: 176.23.128.102 Range: 30002-30009 Total Scanned: 668 Open Ports: 13
Note: Port scanning is an auxiliary tool and may not always be 100% accurate due to firewalls, network policies or other limitations.
A "CLOSED" status or missing port here does not guarantee the service is down.
The iperf3 tests (see the iperf3 Results tab) are always attempted on the configured ports regardless of these scan results.
Port
Status
443
OPEN
2000
OPEN
5060
OPEN
30000
OPEN
30002
OPEN
30003
OPEN
30004
OPEN
30005
OPEN
30006
OPEN
30007
OPEN
30008
OPEN
30009
OPEN
30100
OPEN
lg.gigahost.no (Gigahost)
Port
IPv6
iperf3 -c (TCP)
--reverse (TCP)
iperf3 -c (UDP)
--reverse (UDP)
9205
9206
9207
9208
9209
9210
9211
9212
9213
9214
9215
9216
9217
9218
9219
9220
9221
9222
9223
9224
9225
9226
9227
9228
9229
9230
9231
9232
9233
9234
9235
9236
9237
9238
9239
9240
Target: lg.gigahost.no Range: 9205-9240 Total Scanned: 660 Open Ports: 8
Note: Port scanning is an auxiliary tool and may not always be 100% accurate due to firewalls, network policies or other limitations.
A "CLOSED" status or missing port here does not guarantee the service is down.
The iperf3 tests (see the iperf3 Results tab) are always attempted on the configured ports regardless of these scan results.
Port
Status
80
OPEN
111
OPEN
443
OPEN
5060
OPEN
8080
OPEN
9202
OPEN
9203
OPEN
9204
OPEN
×
Test Explanations
1. Port Range & Scanning
This test verifies which ports are accessible on the target server. We use RustScan (via Docker) to quickly scan for open ports.
Why it fails/varies: A "Closed" result doesn't always mean the service is down. Many servers use firewalls that drop scan packets (stealth mode) or only allow traffic from specific IPs. Additionally, some network policies block the scanning behavior itself.
2. Ping (ICMP)
Ping measures the round-trip time (RTT) for a packet to reach the server and return.
Usage: It gives a quick estimate of network latency.
Reliability: Ping uses ICMP packets. Many modern servers and routers deprioritize or block ICMP to prevent flood attacks. Therefore, a "Timeout" or failure here does not prove the server is offline; it just means it's not replying to pings.
3. Server Busy
Receiving the "server busy" message confirms that the server is online and reachable, but the port is currently occupied by another test.
Unlike multi-port configurations, single-port iperf3 servers often reject connections because they lack concurrency, not because they are down.
4. IPv6 Connectivity
Tests connectivity using the IPv6 protocol via iperf3 -6 -c <host>.
If the server or your local network doesn't support IPv6, this test will be skipped or marked as failed.
5. iperf3 Modes (TCP/UDP)
iperf3 -c (TCP Upload): Sends data from your machine to the server. Tests your upload speed / server's download speed.
--reverse (TCP Download): The server sends data to your machine. Tests your download speed / server's upload speed.
UDP: Uses User Datagram Protocol. Unlike TCP, it doesn't verify delivery. Used to test packet loss and jitter at a specific target bandwidth.
6. Congestion Control
Congestion Control algorithms manage how TCP sends data to avoid clogging the network.
CUBIC: The standard algorithm. Loss-based - it slows down when packets are lost. Reliable and fair.
BBR (Bottleneck Bandwidth and RTT): Developed by Google. It models the network speed and latency instead of relying on packet loss. It is often faster on long-distance or slightly lossy connections.
Illinois / HTCP: Older algorithms optimized for high-speed, high-latency networks. They try to be more aggressive than standard TCP but are often outperformed by BBR today.
7. Symbols
Success / Passed: The test completed successfully.
Failed: The test failed.
Server Busy: The server is online but currently busy running a test.
Skipped (no IPv6): IPv6 tests are skipped when the server does not support IPv6.
?
Not Requested / Unknown: The test was not requested (e.g. UDP was not enabled) or no data is available.