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

API overview

How the HTTP API works: base URL, response format and good practices.

The My IP API is plain HTTP. Every tool on the site has a GET route you can call from any language, script or automation.

Base URL

https://meuip.juk.re/api

No API key and no sign up.

Format

  • Every route uses GET, with parameters in the query string.
  • Responses are JSON, except ping (real time text) and /api/ip?format=text (plain text).
  • Errors come with an error field explaining what happened.

Message language

Send the x-lang header (pt, en, es or fr) or Accept-Language to get error messages in the language you prefer.

Good practices

  • Cache what rarely changes, like DNS and WHOIS.
  • When you get a 429, wait the time in the Retry-After header before trying again.
  • Set a timeout in your client: some lookups depend on the target server.
  • Identify your service with your own User-Agent.

On the Developers page you can see examples in 8 languages and run each call right away.

Developers
PreviousSSL/TLS certificatesNext API reference

On this page

  • Base URL
  • Format
  • Message language
  • Good practices