Service assignments on a port number
API · /netports-api
Network Ports API
The official IANA Service Name and Transport Protocol Port Number registry as an API — 12,500+ TCP, UDP, SCTP and DCCP port assignments. Look up what service runs on a port (e.g. 443 → https), find which port(s) a named service uses (e.g. ssh → 22), and search the registry by service or description. A handy reference for networking, DevOps, security and firewall tooling.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 74 ms
- Server probes · 24h
- Subscribers
- 3,842
- active
- Total calls
- 340
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,000 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 3,000 calls/month
- 3 req/sec
- Port + service lookup
- No credit card
Starter
€5.00 /month
- 50,000 calls / month
- 10 requests / second
- Hard cap (429 above quota, no overage)
- 50k calls/month
- 10 req/sec
- Search + protocol filter
- Email support
Pro
€12.00 /month
- 300,000 calls / month
- 25 requests / second
- Hard cap (429 above quota, no overage)
- 300k calls/month
- 25 req/sec
- Security / firewall tooling
- Priority support
Mega
€32.00 /month
- 1,500,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.5M calls/month
- 50 req/sec
- Embed in product
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
IP Protocol Numbers API
The IANA "Assigned Internet Protocol Numbers" registry as an API — the 8-bit value carried in the IPv4 Protocol field (and IPv6 Next Header) that identifies the encapsulated protocol. Resolve any number to its protocol (e.g. 6 → TCP, 17 → UDP, 1 → ICMP, 47 → GRE, 50 → ESP, 58 → IPv6-ICMP, 89 → OSPF, 132 → SCTP), look up by keyword, search by name, or list all 151 assigned protocols — each with its keyword, full name, IPv6-extension-header flag and defining RFC. Ideal for packet/firewall tooling, network analysis, NetFlow/IPFIX decoders and protocol documentation. (Distinct from transport-layer service port numbers.)
api.oanor.com/ipprotocols-api
URI Schemes API
The IANA Uniform Resource Identifier (URI) Schemes registry as an API — all 413 registered schemes (http, https, mailto, tel, ftp, ssh, magnet, bitcoin, geo, did, …). Look up any scheme to get its description, registration status (Permanent, Provisional or Historical) and defining reference; search by name or description; or list all schemes filtered by status. Ideal for URL parsers and validators, link handlers, deep-linking, security allow-lists and developer tooling that needs to recognise or vet URI schemes.
api.oanor.com/urischemes-api
HTTP Reference API
A clean, programmatic reference for HTTP semantics, built on the official IANA registries. Look up any status code with its reason phrase and class (404 → Not Found, Client Error; 503 → Service Unavailable, Server Error), list a whole class (4xx, 5xx…); look up any method with its safe/idempotent flags (GET → safe + idempotent, POST → neither, DELETE → idempotent); or look up / search the 255 registered HTTP header fields (Content-Type, Authorization, …) with their registration status. Ideal for API tooling, HTTP clients, documentation, linters, learning resources and error pages.
api.oanor.com/http-api
DNS Propagation API
Check DNS propagation by querying a record across several major public resolvers at once — Google (8.8.8.8), Cloudflare (1.1.1.1), AdGuard and dns.sb — and seeing whether they all return the same answer. Pass a domain and a record type and the service queries every resolver in parallel and reports each resolver's answers, whether they are consistent (the change has fully propagated) or still differ (mid-propagation, stale caching or split-horizon DNS), the number of distinct answer sets and the union of all answers. Supported record types: A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA and PTR. A single-resolver endpoint queries one named resolver on its own, and a failing resolver is reported per-resolver without failing the whole call. Live DoH (DNS-over-HTTPS) JSON queries, always current. Built for verifying DNS changes after a migration or launch, debugging split-horizon or stale-cache issues, and uptime/propagation monitoring. A DNS propagation checker — distinct from single-resolver record lookup (dns), the email-authentication analyzer (emailsec) and WHOIS (whois). No upstream key, no cache.
api.oanor.com/dnspropagation-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Network Ports API?
What's the rate limit for Network Ports API?
How much does Network Ports API cost?
Can I cancel my subscription anytime?
Is Network Ports API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/netports-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/netports-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/netports-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/netports-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.