Aerod Run checks

Documentation

IP Lookup Integration Notes

How the live IP Lookup app is mounted directly at /apps/ip-lookup without changing the public route.

Aerod Security Lab Reviewed by Aerod Security Lab Published July 2, 2026 Updated July 3, 2026 2 min read
On this page

IP Lookup lives at /apps/ip-lookup/. That route is the public Aerod app URL for both “IP Lookup” and “What’s My IP” search intent.

The app runtime is now hosted inside the Aerod repo. The public page loads the built Vue/Vite CSS and JavaScript directly from the local runtime asset folder instead of using an iframe bridge.

Route standard

/apps/ip-lookup/

Do not create a second public route for the same IP lookup tool. WebRTC, browser leak, browser fingerprint, and proxy/VPN detection now have focused routes. DNS should become a focused app route only when controlled DNS test infrastructure exists.

Runtime location

public/apps/ip-lookup/runtime/
public/apps/ip-lookup/runtime/assets/

The current Astro route keeps the SEO metadata, canonical URL, app schema, breadcrumb schema, and FAQ schema at /apps/ip-lookup/, then mounts the built app runtime directly into the page.

Page responsibilities

The Aerod route should handle:

  • SEO title and description.
  • Canonical URL.
  • SoftwareApplication schema.
  • Breadcrumb and FAQ schema.
  • A JavaScript-disabled fallback for users and crawlers.
  • A stable public app URL.

Runtime responsibilities

The app runtime should handle:

  • Current public IP detection.
  • IPv4 and IPv6 lookup.
  • Approximate ISP, ASN, city, region, country, timezone, and map output when available.
  • Copy/share actions.
  • Client-side state such as recent lookups if that behavior is retained.

Data handling review

During maintenance reviews, confirm:

  1. Which lookup providers are called.
  2. Whether requests are proxied through Aerod or called directly by the browser.
  3. Whether lookup history stays in the browser only.
  4. Whether any analytics are present.
  5. Whether public IP values are logged by any server-side code.

The public explanation should stay honest: IP geolocation is approximate and may identify a network route, provider, ISP, proxy, VPN, carrier, or cloud network rather than a physical device.