{
  "title": "What is my IP",
  "human_url": "https://happytails.ai/en/network-tools/what-is-my-ip/",
  "agent_url": "https://happytails.ai/agents/en/network-tools/what-is-my-ip/",
  "language": "en",
  "markdown_url": "https://happytails.ai/en/network-tools/what-is-my-ip.md",
  "content": "What is my IP\nDisplay public IPv4/IPv6 observed by endpoint.\nUseful next steps\nIP lookup\nASN, approximate geography and data timestamp.\nDNS lookup\nA AAAA MX TXT CNAME NS SOA records with resolver and time.\nHow to use What is my IP\nEnter the values you want to calculate and choose the relevant units or settings.\nReview the settings, then choose Run What is my IP.\nReview the result, then use Copy result or a download link when available.\nWorking with what is my ip\nA network lookup is a snapshot from a particular resolver, location and time. DNS answers, routing paths and certificates can change, so a result is most useful when the query and observation time are clear.\nCommon questions\nWhy do DNS results differ between locations?\nResolvers can cache records for different periods, and some services deliberately return location-specific answers. A mismatch does not on its own identify a configuration fault.\nCan browser code perform every network check?\nBrowsers restrict arbitrary network access. Some diagnostics need a server or a public service; that service’s observation point affects what the result means.\nContinue your workflow:\nIP lookup\n,\nDNS lookup\n.",
  "content_format": "text/plain",
  "visibility": "public",
  "links": [
    {
      "name": "IP lookup ASN, approximate geography and data timestamp.",
      "url": "https://happytails.ai/en/network-tools/ip-lookup/"
    },
    {
      "name": "DNS lookup A AAAA MX TXT CNAME NS SOA records with resolver and time.",
      "url": "https://happytails.ai/en/network-tools/dns-lookup/"
    }
  ],
  "tool": {
    "id": "what-is-my-ip",
    "category": "network-tools",
    "built": true,
    "requirements": "Display public IPv4/IPv6 observed by endpoint; explain VPN and proxy effects; never call it device identity.",
    "implementation": {
      "fields": [],
      "input": false,
      "processing": "Client-side",
      "note": "Contacts ipify directly from your browser after Run. The provider observes your public IP; this does not reveal your private LAN address.",
      "experience": {
        "automatic": false,
        "single": false,
        "label": "Your text",
        "placeholder": "Type or paste your input…",
        "help": "Up to 1,000,000 characters. Review the settings before running.",
        "action": null
      },
      "mode": "explicit",
      "interactive": false
    },
    "execution": "Browser interface",
    "api": null,
    "browser_agent": {
      "supported": true,
      "name": "run_current_tool",
      "discovery": "WebMCP on the human page in a supporting browser",
      "verification": "See audit/API-AUDIT.md; availability is not verification"
    }
  },
  "markdown": "# What is my IP\n\n- Human page: https://happytails.ai/en/network-tools/what-is-my-ip/\n- Markdown: https://happytails.ai/en/network-tools/what-is-my-ip.md\n- Structured JSON: https://happytails.ai/agents/en/network-tools/what-is-my-ip/index.json\n- Visibility: public\n\n## Tool capabilities\n\n| Property | Value |\n| --- | --- |\n| Tool ID | `what-is-my-ip` |\n| Category | network-tools |\n| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |\n| Browser execution | Use the visible action or interactive controls. |\n| Browser processing | Client-side |\n| HTTP API | Not callable through HTTP. |\n| Browser-agent interface | run_current_tool |\n\n### Implementation notes\n\nContacts ipify directly from your browser after Run. The provider observes your public IP; this does not reveal your private LAN address.\n\n### Inputs and settings\n\nNo free-text input is required. Use the file inputs and/or settings below.\n\nNo additional settings are declared for this tool.\n\n### Browser-agent workflow\n\n1. Open the human page in a browser that supports WebMCP.\n2. Discover the interface exposed by that page; use its actual schema.\n3. Select files on the page first when the tool requires files.\n4. Call `run_current_tool` with valid input and settings.\n5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.\n\nCalls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.\n\n### Planning specification\n\nDisplay public IPv4/IPv6 observed by endpoint; explain VPN and proxy effects; never call it device identity.\n\nThis describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.\n\n### Complete machine-readable capability record\n\n```json\n{\n  \"id\": \"what-is-my-ip\",\n  \"category\": \"network-tools\",\n  \"built\": true,\n  \"requirements\": \"Display public IPv4/IPv6 observed by endpoint; explain VPN and proxy effects; never call it device identity.\",\n  \"implementation\": {\n    \"fields\": [],\n    \"input\": false,\n    \"processing\": \"Client-side\",\n    \"note\": \"Contacts ipify directly from your browser after Run. The provider observes your public IP; this does not reveal your private LAN address.\",\n    \"experience\": {\n      \"automatic\": false,\n      \"single\": false,\n      \"label\": \"Your text\",\n      \"placeholder\": \"Type or paste your input…\",\n      \"help\": \"Up to 1,000,000 characters. Review the settings before running.\",\n      \"action\": null\n    },\n    \"mode\": \"explicit\",\n    \"interactive\": false\n  },\n  \"execution\": \"Browser interface\",\n  \"api\": null,\n  \"browser_agent\": {\n    \"supported\": true,\n    \"name\": \"run_current_tool\",\n    \"discovery\": \"WebMCP on the human page in a supporting browser\",\n    \"verification\": \"See audit/API-AUDIT.md; availability is not verification\"\n  }\n}\n```\n\n## Page guide\n\nDisplay public IPv4/IPv6 observed by endpoint.\n\n## Useful next steps\n\n- [IP lookup](https://happytails.ai/en/network-tools/ip-lookup/): ASN, approximate geography and data timestamp. ([Markdown](https://happytails.ai/en/network-tools/ip-lookup.md))\n\n- [DNS lookup](https://happytails.ai/en/network-tools/dns-lookup/): A AAAA MX TXT CNAME NS SOA records with resolver and time. ([Markdown](https://happytails.ai/en/network-tools/dns-lookup.md))\n\n## How to use What is my IP\n\n1. Enter the values you want to calculate and choose the relevant units or settings.\n2. Review the settings, then choose Run What is my IP.\n3. Review the result, then use Copy result or a download link when available.\n\n## Working with what is my ip\n\nA network lookup is a snapshot from a particular resolver, location and time. DNS answers, routing paths and certificates can change, so a result is most useful when the query and observation time are clear.\n\n## Common questions\n\n### Why do DNS results differ between locations?\n\nResolvers can cache records for different periods, and some services deliberately return location-specific answers. A mismatch does not on its own identify a configuration fault.\n\n### Can browser code perform every network check?\n\nBrowsers restrict arbitrary network access. Some diagnostics need a server or a public service; that service’s observation point affects what the result means.\n\nContinue your workflow: [IP lookup](https://happytails.ai/en/network-tools/ip-lookup/), [DNS lookup](https://happytails.ai/en/network-tools/dns-lookup/).\n"
}