IP API Docs: Public IP, GeoIP & Network Tools

Build IP lookup, GeoIP, DNS, WHOIS, SSL, monitoring, and network diagnostic features with the IPMYP API. IPMYP provides two API options for different integration needs: a Public IP API that works without signup or an API key, and an Authenticated Network Tools API for advanced DNS, WHOIS, SSL, Ping, Traceroute, MTR, Port Check, and infrastructure diagnostics.

If you only need to detect a public IP address or retrieve IP geolocation and network information, use api.ipmyp.com. If you need advanced tools, API keys, account quotas, permissions, usage tracking, or production automation, use the authenticated IPMYP API.

Public IP API

Authenticated API

View API Plans

Public API vs Authenticated API

Feature	Public IP API	Authenticated Network Tools API
Primary URL	`api.ipmyp.com`	`ipmyp.com/wp-json/ipmyp/v1/`
Account required	No	Yes
API key required	No	Yes
Public IP detection	Yes	Available through IP tools
GeoIP lookup	Yes	Yes
DNS / WHOIS / SSL	No	Yes
Ping / Traceroute / MTR	No	Subject to plan and permissions
Port Check	No	Yes, subject to security policy
Account quota	No account quota	Yes
Rate limiting	Yes	Yes
Best for	IP detection and lightweight GeoIP	SaaS, automation, monitoring and diagnostics

Public IP API – No Signup or API Key Required

The IPMYP Public IP API provides a simple way to detect your current public IP address or retrieve structured GeoIP and network information. No IPMYP account, registration, or API key is required.

Public endpoints are protected by rate limits and abuse controls to maintain service availability. The unauthenticated public surface is intentionally limited to IP and GeoIP lookup endpoints.

Get Your Public IP Address

GET https://api.ipmyp.com/

Recommended cURL request:

curl https://api.ipmyp.com

For command-line convenience, the public root endpoint also supports a request without explicitly writing the URL scheme:

curl api.ipmyp.com

The response is plain text containing the public IP address visible to IPMYP:

203.0.113.25

This endpoint is useful for shell scripts, VPN diagnostics, firewall automation, dynamic allowlists, deployment jobs, servers, containers, and infrastructure checks that only need the caller’s public IP address.

Get Your IP Information as JSON

GET https://api.ipmyp.com/json

curl https://api.ipmyp.com/json

The JSON endpoint can return available information such as country, region, city, coordinates, timezone, ISP, organization, ASN, reverse DNS, hosting, proxy, mobile-network indicators, and the queried IP address.

{
  "status": "success",
  "continent": "North America",
  "continentCode": "NA",
  "country": "United States",
  "countryCode": "US",
  "region": "CA",
  "regionName": "California",
  "city": "Mountain View",
  "lat": 37.4,
  "lon": -122.1,
  "timezone": "America/Los_Angeles",
  "isp": "Example Network",
  "org": "Example Organization",
  "as": "AS12345 Example Network",
  "mobile": false,
  "proxy": false,
  "hosting": false,
  "query": "203.0.113.25"
}

The values above are illustrative. Actual fields and values depend on the queried address and available IP intelligence data.

Look Up Another IP Address or Hostname

GET https://api.ipmyp.com/json/8.8.8.8

curl https://api.ipmyp.com/json/8.8.8.8

The public endpoint also supports the convenient command-line form without explicitly specifying https://:

curl api.ipmyp.com/json/8.8.8.8

A supported hostname may also be supplied:

curl https://api.ipmyp.com/json/example.com

Request Only the Fields You Need

Use the optional fields query parameter to reduce response size when your application only needs specific values.

curl "https://api.ipmyp.com/json/8.8.8.8?fields=status,country,countryCode,isp,as,query"

Public API Endpoint Reference

Method	Endpoint	Description	Authentication
`GET`	`/`	Return the caller’s public IP as plain text.	None
`GET`	`/json`	Return the caller’s IP and available GeoIP/network data.	None
`GET`	`/json/{query}`	Look up another public IP address or supported hostname.	None

HTTP and HTTPS Support

The public / and /json endpoints are available over both HTTP and HTTPS, which allows commands such as curl api.ipmyp.com to work without explicitly typing a URL scheme.

For production applications, always use an explicit HTTPS URL. HTTPS provides transport encryption, prevents accidental downgrade behavior, and makes application configuration consistent across clients, proxies, and environments.

curl https://api.ipmyp.com
curl https://api.ipmyp.com/json
curl https://api.ipmyp.com/json/8.8.8.8

Authenticated Network Tools API

The IPMYP Authenticated Network Tools API is designed for developers, DevOps engineers, hosting providers, SaaS applications, monitoring systems, support teams, and infrastructure automation that need advanced network diagnostics.

This API requires an IPMYP account and API key. Tool execution is controlled by your account plan, API key permissions, quota, configured limits, and security policies.

Create or Sign In to Your Account

Manage API Keys

Authenticated API Quick Start

Create or sign in to your IPMYP account.
Open the API Keys section in your user panel.
Create a key with only the permissions your application needs.
Copy and store the complete API key securely.
Send it using the Authorization: Bearer header.
Specify the exact tool identifier and target.
Parse the structured response and quota information.

Authenticated API Endpoint

POST https://ipmyp.com/wp-json/ipmyp/v1/tools/run

This endpoint validates authentication, API key status, permissions, tool availability, target security, plan allowance, and usage limits before executing a network tool.

Authentication

Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx
Content-Type: application/json

Store live API keys in a backend environment variable, secrets manager, or another protected server-side location. Never expose an authenticated API key in frontend JavaScript, browser source code, public Git repositories, screenshots, mobile application bundles, or public configuration files.

Basic Request

{
  "tool": "dns_a",
  "target": "example.com"
}

Full cURL example:

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"dns_a","target":"example.com"}'

Network Tool API Identifiers

Use the exact identifier in the tool field. Availability depends on account plan, API key permissions, administrator configuration, and operational security policy.

Tool ID	Purpose	Example Target
`multi`	Combined DNS and network report	`example.com`
`dns_a`	IPv4 A record lookup	`example.com`
`dns_aaaa`	IPv6 AAAA lookup	`example.com`
`dns_mx`	Mail exchanger lookup	`example.com`
`dns_ns`	Authoritative name servers	`example.com`
`dns_txt`	TXT / SPF / DKIM / DMARC records	`example.com`
`dns_cname`	CNAME record lookup	`www.example.com`
`dns_soa`	SOA lookup	`example.com`
`dns_caa`	CAA lookup	`example.com`
`dnssec_check`	DNSSEC diagnostics	`example.com`
`email_security`	Email DNS security checks	`example.com`
`delegation_check`	DNS delegation analysis	`example.com`
`dns_propagation`	DNS propagation checks	`example.com`
`reverse_dns`	PTR / reverse DNS lookup	`8.8.8.8`
`ip_geo`	IP geolocation and network information	`8.8.8.8`
`whois`	Domain WHOIS lookup	`example.com`
`ssl_info`	SSL/TLS certificate information	`example.com`
`port_check`	Allowed TCP port reachability	`example.com:443`
`ping`	Reachability and latency	`example.com`
`trace_route`	Network route diagnostics	`example.com`
`mtr`	Route, latency and packet-loss diagnostics	`example.com`

For interactive versions of these checks, visit the IPMYP DNS Lookup and Network Tools page.

Common API Examples

DNS A Record API

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"dns_a","target":"example.com"}'

For manual checks, use the A Record Lookup.

WHOIS API

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"whois","target":"example.com"}'

For browser-based checks, use WHOIS Lookup.

SSL Certificate API

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"ssl_info","target":"example.com"}'

For manual HTTPS checks, use the SSL Checker.

Traceroute API

The exact API identifier is trace_route.

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"trace_route","target":"example.com"}'

For an interactive test, use Traceroute Online.

Port Check API

The exact API identifier is port_check. Active network checks are subject to IPMYP security and target-validation policies.

curl -X POST "https://ipmyp.com/wp-json/ipmyp/v1/tools/run" \
  -H "Authorization: Bearer ipmyp_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"tool":"port_check","target":"example.com:443"}'

Errors, Quotas and Rate Limits

The public and authenticated APIs use different access models. Public IP endpoints do not require account authentication, but service-level rate limits and abuse controls apply. Authenticated tool requests are additionally subject to API key status, permissions, account plan, quota, and usage policies.

Situation	Meaning	Recommended Action
Invalid API key	The credential is missing, invalid or revoked.	Check or rotate the Bearer token.
Permission denied	The key does not have permission for the requested tool.	Review API key permissions.
Quota exceeded	A plan or key limit has been reached.	Wait for reset or review your plan.
HTTP 429	The current rate-limit window has been exceeded.	Retry later with backoff.
Invalid target	The supplied target failed validation.	Correct the domain, hostname, IP or port.
Blocked target	A security policy rejected the destination.	Do not retry prohibited targets.
Temporary 5xx error	A transient service or upstream failure occurred.	Retry with bounded exponential backoff and jitter.

Production API Best Practices

For production integrations, use explicit HTTPS URLs, keep authenticated API keys on trusted backend systems, create separate keys for production and staging, apply least-privilege permissions, configure reasonable connection and request timeouts, validate targets before submitting them, monitor usage, and retry only transient failures. Use exponential backoff with jitter for temporary network errors, selected 5xx responses, and HTTP 429 responses. Do not automatically retry authentication, permission, or validation errors.

When repeated public GeoIP lookups do not require fresh data on every request, application-level caching can reduce latency and unnecessary API traffic. Never log full API secrets; log request IDs, status codes, error codes, tool identifiers, and non-sensitive diagnostics instead.

Node.js Example

const response = await fetch(
  "https://ipmyp.com/wp-json/ipmyp/v1/tools/run",
  {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.IPMYP_API_KEY}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      tool: "dns_a",
      target: "example.com"
    })
  }
);

const data = await response.json();

if (!response.ok) {
  throw new Error(data?.error?.message || `IPMYP API error: ${response.status}`);
}

console.log(data);

PHP Example

<?php

$apiKey = getenv('IPMYP_API_KEY');

$ch = curl_init('https://ipmyp.com/wp-json/ipmyp/v1/tools/run');

curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_CONNECTTIMEOUT => 5,
    CURLOPT_TIMEOUT => 30,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'tool' => 'dns_a',
        'target' => 'example.com',
    ]),
]);

$response = curl_exec($ch);
$status = curl_getinfo($ch, CURLINFO_HTTP_CODE);

curl_close($ch);

if ($status >= 400) {
    throw new RuntimeException('IPMYP API request failed.');
}

print_r(json_decode($response, true));

Common Use Cases

IPMYP APIs can be used for public IP discovery, VPN and proxy diagnostics, GeoIP enrichment, hosting dashboards, SaaS products, DNS validation, SSL certificate checks, WHOIS automation, network troubleshooting, DevOps workflows, monitoring systems, technical support, CDN migrations, email-security audits, infrastructure validation, and server connectivity diagnostics.

Frequently Asked Questions

Does IPMYP provide a public IP API without signup?

Yes. https://api.ipmyp.com and the public /json endpoints do not require an account or API key. Rate limits and abuse controls still apply.

Can I run curl api.ipmyp.com without https://?

Yes. The public root and JSON endpoints support HTTP requests, so commands such as curl api.ipmyp.com work. For production application code, explicitly use https://.

How do I get my IP address as JSON?

curl https://api.ipmyp.com/json

Can I look up another IP address?

curl https://api.ipmyp.com/json/8.8.8.8

Do DNS, WHOIS, SSL, Ping and Traceroute require an API key?

Yes. Advanced Network Tools API requests use the authenticated IPMYP API and require an account and API key with the appropriate permissions.

What is the Traceroute API identifier?

Use trace_route.

What is the Port Check API identifier?

Use port_check.

Start Building with IPMYP

For public IP detection and lightweight GeoIP lookups, start immediately with api.ipmyp.com. No signup or API key is required.

For DNS, WHOIS, SSL, Ping, Traceroute, MTR, Port Check, advanced diagnostics, automation, permissions, and account-based usage, create an IPMYP account and generate a secure API key.

Create an Account

Manage API Keys

Compare API Plans