Skip to content
NETMETRİKDocumentation

DocumentationServer requirements

Server requirements

The requirements your server must meet to be accepted into the HIZTESTI Servers Network and to stay live. Checking them before you apply saves time for both you and the review process.

Last updated: 14 July 2026

Network

RequirementDetail
BandwidthAt least a 1 Gbps dedicated connection. Speed-test traffic is bursty; shared or metered lines degrade measurement quality and are filtered out during review.
Traffic shapingThere must be no rate limiting, prioritization or packet filtering on test traffic — it distorts measurement results and blocks acceptance.
AvailabilityThe server must be reachable from the internet 24/7. Health checks run continuously; an unreachable server is automatically removed from rotation.
PortsThe test port (in the default install, 443 TCP and UDP — TLS + HTTP/3) must be open to all sources in the firewall. A plain-HTTP mode behind a reverse proxy is also supported; see Linux installation.
IPv6Not mandatory, but recommended. IPv6 support is treated as a positive signal in server selection.

Domain name (DNS)

  • A fully qualified domain name that resolves over public DNS (e.g. hiztesti.kurum.com) is required; a bare IP address is not accepted.
  • The A (and, if present, AAAA) record must point directly to the test server.
  • If the server's IP changes, updating the DNS record is enough — registration is tied to the domain name.
  • Test traffic is carried only over HTTPS; the installer obtains the required TLS certificate automatically (see below).
Who provides the TLS certificate?
NETMETRİK Server obtains and renews the certificate itself: during installation a free certificate is issued for your domain from Let's Encrypt and is renewed automatically before it expires — no certbot or manual step is needed (ports 80 and 443 just need to be open to the internet). Alternatives: you can point to your own certificate in the configuration, or run the server behind a reverse proxy (nginx, Caddy, Cloudflare) that terminates TLS — the script detects the reverse proxy on its own. Details: Linux installation.

Hardware

  • Recommendation: at least a 2-core CPU and 8 GB of memory. On lines of 10 Gbps and above, more cores and up-to-date NIC drivers are recommended.
  • The CPU/memory/bandwidth profile you declare in the application is compared against the inventory the server self-reports after installation — declare accurately.
  • An accurate system clock (NTP synchronization) is required.

Operating system

  • Linux x86_64 / aarch64 (recommended: a current Ubuntu LTS or Debian), macOS and FreeBSD are supported.
  • The install script provides a systemd unit; on distributions without systemd you take on process management yourself.

Organizational requirements (for the public network)

  • A public website with a valid organization name and contact details — the sponsor link on the result card points to this site.
  • The server's real location (province/district) must be declared accurately; nearest-server selection for the user relies on this information.
  • The same organization may not have more than one server in the public network in the same city (geographic diversity rule). HIZTESTI Custom servers that only serve your own widgets are not subject to this rule.
Have a borderline case?
If you meet the requirements, continue with the Quick start. If you have a borderline case — a line below 1 Gbps or a special network topology — write to our support team and we will assess it together.