Built-in HTTP API
Every page is driven by the same JSON endpoints. Responses are { ok, data } and cached in SQLite with a TTL.
Endpoints
| Path | Description | |
|---|---|---|
| /netapi/me/ | Visitor IP seen by the server | |
| /netapi/geo/?ip=8.8.8.8 | Merged geolocation (ip.sb + ipwho.is + ip-api) | |
| /netapi/health/?ip=8.8.8.8 | Reputation score and risk flags (ip.net.coffee) | |
| /netapi/network/?ip=8.8.8.8 | RIPEstat prefix, PTR, BGP topology, RPKI | |
| /netapi/lookup/?ip=8.8.8.8 | All of the above in one call | |
| /netapi/whois/?q=example.com | RDAP lookup for domain / IP / ASN | |
| /netapi/subdomains/?domain=example.com | Certificate transparency list (crt.sh) | |
| /netapi/ping-nodes/ | Globalping probe cities | |
| /netapi/ping-result/?id=ID | Poll a measurement result | |
| /netapi/ping-start/ | Start a global ping measurement | |
| /netapi/status/ | Aggregated status of all monitored services | |
| /netapi/status-one/?id=0 | Detail of one service | |
| /netapi/cdn/ | CDN node identifiers seen from the server | |
| /netapi/trace/?domains=1.1.1.1%2Cclaude.ai | Parse cdn-cgi/trace of targets | |
| /netapi/egress/ | Domestic CDN egress headers | |
| /netapi/history/?kind=whois | Recent server-side lookups | |
| /netapi/doctor/ | Runtime self-check |
curl example
curl "https350730.com/netapi/lookup/?ip=8.8.8.8"
curl -X POST "https350730.com/netapi/ping-start/" \
-H 'Content-Type: application/json' \
-d '{"target":"1.1.1.1","protocol":"ping","locations":[{"country":"US","limit":3}]}'
Browser-side probes
Egress IP, connectivity, DNS echo, WebRTC and fingerprint checks run in the visitor browser and never touch the server; they are the reason some results cannot be reproduced by curl.
Response preview
How to use
This tool belongs to the “Operations” category.
- 1"API reference" lists the endpoints, parameters and response fields this site itself uses - copy them straight into a script.
- 2"Diagnostics" reports upstream availability and cache state, and shows the most recent public query records.
- 3When data looks off, check Diagnostics first: an upstream marked unavailable means the tools reading it are only indicative.
Device and browser checks run on your machine. Domain and IP lookups are fetched by this site from public feeds, and each query string is kept as one public record.
Frequently asked questions
Can I call these endpoints myself?
They are the same addresses this site uses, but requests are rate limited per visitor IP. Hammering them returns 429, so keep the pace down.
Why publish a diagnostics page at all?
Probe-based tools depend on upstreams that change without notice. Showing where each value comes from, and whether it answers, lets you judge a problem instead of guessing.
What do the query records show?
Only the domain or IP that was queried plus a short summary - nothing that identifies the visitor.