Verify whether any domain or public IP is currently online.
Domain and IP Pinger checks whether any domain name or public IP address is reachable and responding in real time. It returns an alive status and successful round trips, while paid plans add packet loss percentages and latency metrics.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"host": "google.com",
"numericHost": "2607:f8b0:4001:c6e::8a",
"alive": true,
"roundTrips": 3,
"packetLoss": 0,
"minMS": 0.652,
"avgMS": 0.6846666666666666,
"maxMS": 0.712,
"stdDev": 0.02478350706058811,
"times": [
0.712,
0.652,
0.69
]
}
}
About the Domain and IP Pinger API
A ping API to ping a domain online or ping an IP address without opening a terminal. Send a POST request with a hostname or public IP address and the desired ping count, and the service sends ICMP echo requests to the target in real time from our servers, reporting whether it answered and how many round trips completed.
The Free plan returns the host, an alive flag and the number of successful round trips. That covers a quick check of host reachability on a status page, in a support tool, or in a bot that answers whether a site is down for everyone or only for one user.
Paid plans add the numbers needed to test server latency: the resolved numeric IP, a packet loss check as a percentage, minimum, average and maximum round-trip times in milliseconds, their standard deviation and every individual time. Paid plans can also set a custom timeout in milliseconds. Private, loopback and other non-public addresses are refused, so only hosts on the public internet can be pinged.
How it works
The API runs the system ping utility against host, one probe per round trip and one after another, and records the reply time of each probe that is answered. host must be a valid hostname or IP address that resolves to a public address; private ranges, loopback and similar targets return 400. A name that cannot be resolved is still attempted and comes back not alive.
roundTrips sets how many probes are sent, 1 to 5, default 1. timeout is given in milliseconds (100-3000, default 1500), but ping waits in whole seconds, so the value is rounded up: 100-1000 waits 1 second per probe, 1001-2000 waits 2 and 2001-3000 waits 3. Free plan calls always use the default, a 2-second wait.
alive is true when at least one probe was answered, and roundTrips in the response is the number answered, not the number sent. packetLoss is the unanswered share times 100 and is not rounded, so one loss in three reads 33.33 and more digits. minMS, avgMS and maxMS summarise times, the per-probe round trips in milliseconds, and stdDev is their population standard deviation.
If every probe fails, alive is false, packetLoss is 100, the timing fields are null and times is empty. Every requested probe is sent even when some fail, so a down or lossy host returns a normal success response with its packetLoss; an error status means the check itself failed. A URL or host:port in host is reduced to the hostname first, since ICMP has no port. numericHost is the IP ping resolved, or unknown. Many hosts drop ICMP deliberately, so not alive can mean a firewall rather than an outage. On the Free plan numericHost, packetLoss and every timing field are null.
What people use it for
- Server Reachability Checks
- DevOps engineers trigger ping checks during deployments to confirm that newly provisioned web servers respond before routing production traffic to them.
- Network Latency Monitoring
- When network engineers detect sluggish connections, they inspect round-trip responses across public IP endpoints to diagnose potential packet drop issues.
- Domain Availability Verification
- To catch outages fast, internal status dashboards poll critical external third-party hostnames and display immediate alive indicators to support staff.
- Automated Incident Triage
- Alerting systems ping reported remote servers to verify reachability before paging on-call staff for an offline alert.
Without writing code
Latency Checker Widget for Windows keeps your ping on the desktop.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Domain and IP Pinger
Same data, same APIVerve account, same credit balance — one key works on all of them.
Can I test both domain names and public IP addresses?
Can I adjust how many pings are sent in a single check?
Are latency metrics and packet loss percentages included on the Free plan?
Which plan fits pinging 50,000 servers a month?
Can I display these ping results inside a commercial monitoring tool?
Request parameters — POST /v1/pinger
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
hostRequired | string | google.com | The host name or public IP that you want to ping. A URL (https://example.com/path) or host:port is reduced to its host |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
timeoutOptionalPremium | integer | 1000 | The timeout for the ping request in milliseconds default 1500 · range 100-3000 |
roundTripsOptional | integer | 1 | How many pings to send before averaging the round-trip time default 1 · range 1-5 |
curl -X POST "https://api.apiverve.com/v1/pinger" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"host":"google.com","timeout":1,"roundTrips":1}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/pinger
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"host": "google.com",
"numericHost": "2607:f8b0:4001:c6e::8a",
"alive": true,
"roundTrips": 3,
"packetLoss": 0,
"minMS": 0.652,
"avgMS": 0.6846666666666666,
"maxMS": 0.712,
"stdDev": 0.02478350706058811,
"times": [
0.712,
0.652,
0.69
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
host | string | "google.com" | The hostname or IP address that was pinged |
numericHostPremium | string | "2607:f8b0:4001:c6e::8a" | The numeric IP address of the host that was pinged |
alive | boolean | true | Whether the host is reachable and responding to ping requests |
roundTrips | number | 3 | Number of successful ping round trips completed |
packetLossPremium | number | 0 | Percentage of packets lost during the ping operation |
minMSPremium | number | 0.652 | Minimum round trip time in milliseconds |
avgMSPremium | number | 0.6846666666666666 | Average round trip time in milliseconds |
maxMSPremium | number | 0.712 | Maximum round trip time in milliseconds |
stdDevPremium | number | 0.02478350706058811 | Standard deviation of round trip times |
timesPremium | array | [0.712, ...] | Array of individual round trip times in milliseconds |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Domain and IP Pinger calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/pinger
No SDK to install — this is a plain HTTPS call to /v1/pinger with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/pinger" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/pinger
Install the Node.js SDK, then call the Domain and IP Pinger API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/pingerconst res = await fetch("https://api.apiverve.com/v1/pinger", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/pinger
No SDK to install — this is a plain HTTPS call to /v1/pinger with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/pinger",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/pinger
Install the C# / .NET SDK, then call the Domain and IP Pinger API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DomainandIPPingerusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/pinger");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/pinger
No SDK to install — this is a plain HTTPS call to /v1/pinger with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/pinger", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/pinger
No SDK to install — this is a plain HTTPS call to /v1/pinger with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/pinger");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/pinger
No SDK to install — this is a plain HTTPS call to /v1/pinger with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/pinger")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Domain and IP Pinger form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Domain and IP Pinger API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Domain and IP Pinger API.
Networking
- Bluetooth Company Lookup
- Bot Detector
- Content Filter
- Domain and IP Pinger
- IP Blacklist Lookup
- IP Lookup
- MAC Address Lookup
- Nameservers
- Phishing Domain Checker
- TLD Lookup
- TLS Checker
- Tor Node Detector
- USB Vendor Lookup
- VPN Proxy Detector
Related articles
All articles →
API Rate Limits: What They Mean and Why You Hit ThemRate limits exist for a reason. Here's how to understand them, avoid hitting them, and handle them gracefully when you do.Read
Why Your API Integration Keeps BreakingAPIs break in production. Here's why it happens and how to build integrations that survive the real world.Read
Scalable API Architecture: Monolith to MicroservicesLearn how to design and build API architectures that scale with your business, from initial setup to handling millions of requests.Read