SRV Record Parser API

POST

Extract services, protocols, and domains from any DNS SRV record.

SRV Record Parser analyzes DNS SRV records and extracts service location information including priority, weight, port, and target server details.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/srvparser

Body

recordstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.",
    "parsed": {
      "name": "_http._tcp.example.com.",
      "service": "_http",
      "protocol": "tcp",
      "domain": "example.com.",
      "ttl": 86400,
      "class": "IN",
      "priority": 10,
      "weight": 60,
      "port": 80,
      "target": "server.example.com"
    },
    "service_info": {
      "name": "HTTP",
      "description": "Web service",
      "default_port": 80
    },
    "interpretation": {
      "priority_explanation": "Priority level 10 (lower is better)",
      "weight_explanation": "Weight 60 for load balancing",
      "target_explanation": "Connect to server.example.com:80"
    },
    "is_valid": true
  }
}

About the SRV Record Parser API

Includes recognition of common services like HTTP, XMPP, SIP, and email protocols with detailed explanations of priority and weight values.

What people use it for

Service Discovery: Parse DNS SRV records for service discovery in distributed systems, microservices, and load-balanced environments
Network Diagnostics: Build network diagnostic tools that analyze SRV records for troubleshooting connectivity and service availability issues
Configuration Analysis: Analyze service configuration in DNS including priority, weight, port, and target information for optimization
Record Validation: Validate SRV record formatting and structure to ensure compliance with RFC 2782 standards and best practices

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

View all integrations →

Other ways to use SRV Record Parser

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the SRV Record Parser API.

Read the docs →

Which protocols and service types does the parser identify?

It identifies common protocols including HTTP, XMPP, SIP, and email services. When a known service is recognized, the parser supplies human-readable service descriptions and default port details alongside protocol and domain information.

What would parsing 50,000 SRV records a month cost me?

Each parse costs 2 credits, so 50,000 records consume 100,000 credits each month. That uses half of the 200,000 credits included with the Starter plan, working out to about $0.30 per 1,000 parses. If you just need to test, the Free plan includes 100 parses every month.

Do I get the target host and port on the Free plan?

No. The target host, port number, priority, weight, recognized service info, and human-readable explanations are premium fields unlocked on Starter and above. The Free plan provides basic record details including service identifier, protocol, domain, TTL, and validation status.

How does the API handle malformed or invalid SRV records?

The response includes an is_valid field indicating whether the string matches valid SRV syntax. If a string cannot be parsed correctly into standard DNS components, this flag signals the formatting issue so your application can flag or reject bad input.

Can I use parsed SRV data inside my commercial monitoring tools?

Yes, provided you are on a paid plan. You can use the parsed records, priority rankings, and service details inside your commercial network diagnostics, discovery tools, or SaaS platforms. You cannot redistribute or resell the raw parser output directly as a standalone dataset.

Request parameters — POST /v1/srvparser

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
`record`Required	string	`_http._tcp.example.com. 3600 IN SRV 10 60 80 server.example.com.`	The SRV record string to parse

Example request

curl -X POST "https://api.apiverve.com/v1/srvparser" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"record":"_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."}'

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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

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/srvparser

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.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.",
    "parsed": {
      "name": "_http._tcp.example.com.",
      "service": "_http",
      "protocol": "tcp",
      "domain": "example.com.",
      "ttl": 86400,
      "class": "IN",
      "priority": 10,
      "weight": 60,
      "port": 80,
      "target": "server.example.com"
    },
    "service_info": {
      "name": "HTTP",
      "description": "Web service",
      "default_port": 80
    },
    "interpretation": {
      "priority_explanation": "Priority level 10 (lower is better)",
      "weight_explanation": "Weight 60 for load balancing",
      "target_explanation": "Connect to server.example.com:80"
    },
    "is_valid": true
  }
}

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
`raw_record`	string	`"_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com."`	Original SRV record string provided for parsing
`parsed`	object	`{...}`
`name`	string	`"_http._tcp.example.com."`	Full SRV record name with trailing dot
`service`	string	`"_http"`	Service identifier (e.g., _http, _xmpp, _sip)
`protocol`	string	`"tcp"`	Protocol type (e.g., tcp, udp, tls)
`domain`	string	`"example.com."`	Domain name with trailing dot
`ttl`	number	`86400`	Time-to-live value in seconds
`class`	string	`"IN"`	DNS class (typically IN for Internet)
`priority`Premium	number	`10`	Priority value (lower values preferred)
`weight`Premium	number	`60`	Weight for load balancing among same priority
`port`Premium	number	`80`	Port number for service connection
`target`Premium	string	`"server.example.com"`	Target hostname without trailing dot
`service_info`Premium	object	`{...}`	Information about the recognized service type
`name`Premium	string	`"HTTP"`	Human-readable service name (e.g., HTTP, XMPP)
`description`Premium	string	`"Web service"`	Service description and use case
`default_port`Premium	number	`80`	Default port for identified service
`interpretation`Premium	object	`{...}`	Human-readable interpretation of SRV record values
`priority_explanation`Premium	string	`"Priority level 10 (lower is better)"`	Human-readable explanation of priority level
`weight_explanation`Premium	string	`"Weight 60 for load balancing"`	Human-readable explanation of weight value
`target_explanation`Premium	string	`"Connect to server.example.com:80"`	How to connect to target with port
`is_valid`	boolean	`true`	Whether record is validly formatted and parsed

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	SRV Record Parser 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.

Compare all pricing tiers →

Call it from cURL — POST /v1/srvparser

No SDK to install — this is a plain HTTPS call to /v1/srvparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/srvparser" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/srvparser-apiSource, issues and the examples this page is built from.ReferenceSRV Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/srvparsernpm APIVerve.API.SRVRecordParserNuGet

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/srvparser

Install the Node.js SDK, then call the SRV Record Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/srvparser

Node.js

const res = await fetch("https://api.apiverve.com/v1/srvparser", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/srvparserThe published Node.js client, versioned and signed.GitHubapiverve/srvparser-apiSource, issues and the examples this page is built from.ReferenceSRV Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.SRVRecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/srvparser

No SDK to install — this is a plain HTTPS call to /v1/srvparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/srvparser",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/srvparsernpm APIVerve.API.SRVRecordParserNuGet

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/srvparser

Install the C# / .NET SDK, then call the SRV Record Parser API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.SRVRecordParser

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/srvparser");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.SRVRecordParserThe published C# / .NET client, versioned and signed.GitHubapiverve/srvparser-apiSource, issues and the examples this page is built from.ReferenceSRV Record Parser API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/srvparsernpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/srvparser

No SDK to install — this is a plain HTTPS call to /v1/srvparser 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/srvparser", 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

@apiverve/srvparsernpm APIVerve.API.SRVRecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/srvparser

No SDK to install — this is a plain HTTPS call to /v1/srvparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/srvparser");
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

@apiverve/srvparsernpm APIVerve.API.SRVRecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/srvparser

No SDK to install — this is a plain HTTPS call to /v1/srvparser with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/srvparser")
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.body

Resources

Also published for

@apiverve/srvparsernpm APIVerve.API.SRVRecordParserNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

API Rate Limiting Done Right: A Complete GuideLearn how to design rate limits that protect your API while maintaining good developer experience.Read

Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

SRV Record Parser API

Try it — live request, no key required

About the SRV Record Parser API

What people use it for

Ways to call it

Other ways to use SRV Record Parser

Questions.

Request parameters — POST /v1/srvparser

Required

Authentication

Response — POST /v1/srvparser

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/srvparser

Resources

Also published for

Call it from Node.js — POST /v1/srvparser

Resources

Also published for

Call it from Python — POST /v1/srvparser

Resources

Also published for

Call it from C# / .NET — POST /v1/srvparser

Resources

Also published for

Call it from Go — POST /v1/srvparser

Resources

Also published for

Call it from PHP — POST /v1/srvparser

Resources

Also published for

Call it from Ruby — POST /v1/srvparser

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — SRV Record Parser API

Reference Data

Related articles

Ready to build with SRV Record Parser? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog