MY IP
DocumentationDevelopers
GuidesDevelopers

Getting started

  • Introduction

Tools

  • What is my IP address
  • Port checker
  • DNS lookup
  • SSL/TLS checker
  • WHOIS lookup
  • Fetch
  • Network location
  • Ping

Guides

  • Public IP, private IP and CGNAT
  • Port forwarding
  • DNS records
  • SSL/TLS certificates

For developers

  • API overview
  • API reference
  • Real time responses
  • Recipes
  • Limits and errors

A project by

Free network tools, no sign up. Lookups run from our server and we don't keep what you search for.

Tools

  • My IP
  • Ports
  • DNS
  • SSL/TLS
  • WHOIS
  • Fetch
  • Location
  • Ping

Project

  • About
  • Documentation
  • Developers
  • GitHub

© 2026 JUK.re, developed by Juca

For developers

Real time responses

How to read ping, which arrives line by line without waiting for the end.

Ping at /api/ping answers a little at a time: each line arrives as soon as the server gets it, in the same format as the terminal's ping.

How to read it

  1. Make the request as usual.
  2. Read the response body in chunks (a stream), without waiting for the end.
  3. To stop, cancel the request. The server ends the ping right away.

Browser example

const res = await fetch("/api/ping?host=1.1.1.1");
const reader = res.body.pipeThrough(new TextDecoderStream()).getReader();

for (;;) {
  const { done, value } = await reader.read();
  if (done) break;
  console.log(value);
}

Output format

PING 1.1.1.1 (1.1.1.1)
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=14.4 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=14.7 ms

Ping stops on its own after 30 packets. If the server has no ICMP, the test uses TCP connect time instead.

Behind a proxy like nginx, turn off buffering for this route, otherwise the lines only show up at the end.

PreviousAPI referenceNext Recipes

On this page

  • How to read it
  • Browser example
  • Output format