#networking

Fiber-optic link-budget engineering maths as an API, computed locally and deterministically — the power-budget, loss and reach numbers a network or fibre engineer designs an optical link with. The power-budget endpoint gives the optical power budget = transmit power − receiver sensitivity (in dBm), the total loss the link can tolerate: a 0 dBm transmitter into a −23 dBm receiver gives a 23 dB budget, with the powers also shown in milliwatts. The loss endpoint adds up the real link loss from the fibre attenuation × length plus the connector and splice losses — single-mode fibre runs about 0.35 dB/km at 1310 nm and 0.20 dB/km at 1550 nm, each mated connector ~0.5 dB and each fusion splice ~0.1 dB — so 10 km of fibre with two connectors is 4.5 dB. The reach endpoint gives the maximum distance = (power budget − fixed losses − system margin) ÷ the fibre attenuation, reserving a margin (typically 3 dB) for ageing, bends and future repair splices so the link still works years on. Everything is computed locally and deterministically, so it is instant and private. Ideal for FTTx and data-centre link planning, network-engineering and OSP tools, fibre-survey and design utilities, and telecom calculators. Pure local computation — no key, no third-party service, instant. Loss-limited model — at high bit rates dispersion can cap distance first. 3 compute endpoints. For fibre numerical aperture and photonics use a fiber API; for RF line-of-sight a Fresnel-zone API.

api.oanor.com/opticalbudget-api

MAC-address (EUI-48) tooling as an API, computed locally and deterministically. The parse endpoint validates a MAC address given in any common notation — colon, hyphen, Cisco dotted or a bare run of 12 hex digits — and returns it in every standard format, split into its OUI (the first three bytes, assigned to a hardware vendor) and its NIC (the last three, device-specific) parts, plus the 48-bit integer value. The analyze endpoint reads the control bits of the first octet: the least-significant bit is the I/G bit that marks a unicast or multicast address, and the next bit is the U/L bit that marks a universally (vendor-assigned) or locally administered address, and it flags the broadcast address ff:ff:ff:ff:ff:ff. The eui64 endpoint derives the modified EUI-64 interface identifier — flipping the U/L bit and inserting FF:FE in the middle — and the resulting IPv6 link-local address (fe80::/64) used by stateless address autoconfiguration. Vendor name lookup needs the IEEE OUI registry and is not included. Everything is computed locally and deterministically, so it is instant and private. Ideal for networking, IoT, device-management, monitoring and security app developers, MAC-normalisation and IPv6 tools, and networking education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is MAC-address tooling; for IPv4 subnetting use a subnet API and for DNS records a DNS API.

api.oanor.com/macaddress-api

Data-transfer and bandwidth maths as an API, computed locally and deterministically. The time endpoint computes how long a file takes to transfer at a given bandwidth, time = file bits ÷ (rate × (1 − overhead)), accepting sizes in B, KB, MB, GB, TB or the binary KiB/MiB/GiB and rates in bps, Kbps, Mbps, Gbps or bytes-per-second (MB/s), with an optional protocol-overhead allowance, and returns the time in seconds, minutes, hours and a human-readable form. The bandwidth endpoint works backwards: the bandwidth needed to move a file within a target time, in bps, Mbps, Gbps and MB/s. The convert endpoint converts a data size between decimal (1 MB = 1,000,000 bytes) and binary (MiB = 1,048,576) units, or a data rate between bit-rates and byte-rates. Everything is computed locally and deterministically, so it is instant and private. Ideal for networking, cloud, backup and streaming app developers, download-time and capacity-planning tools, and dev dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is transfer time and bandwidth; for media encoding bitrate use a bitrate API.

api.oanor.com/transfer-api

Wi-Fi channel maths as an API, computed locally and deterministically from the standard channel-numbering formulas. The channel endpoint returns the centre frequency of a Wi-Fi channel on the 2.4, 5 or 6 GHz band — the band is auto-detected from the channel number or can be given explicitly (2.4 GHz: 2407 + 5·channel, with channel 14 at 2484; 5 GHz: 5000 + 5·channel; 6 GHz: 5950 + 5·channel). The frequency endpoint does the reverse, returning the nearest channel and band for a centre frequency in MHz or GHz. The overlap endpoint reports whether two channels overlap at a chosen channel width (two channels overlap when their centre-frequency separation is less than the width) and gives the recommended non-overlapping set — the classic 1, 6 and 11 on 2.4 GHz at 20 MHz. Everything is computed locally and deterministically, so it is instant and private. Channel availability is regulated and varies by country. Ideal for networking and Wi-Fi tools, site-survey and IoT apps, and router and access-point configuration software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Wi-Fi channel mapping; for general wavelength/frequency and photon energy use a wavelength API.

api.oanor.com/wifichannel-api

Validate, reformat and analyse MAC (EUI-48) addresses — entirely locally. The format endpoint accepts a MAC in any common notation — colon (aa:bb:cc:dd:ee:ff), hyphen (aa-bb-…), Cisco dotted (aabb.ccdd.eeff) or bare (aabbccddeeff) — and returns it in the notation you ask for plus all the others, in upper or lower case, normalising messy input into a clean canonical form. The info endpoint analyses an address: it splits the OUI (the manufacturer prefix) from the NIC portion, reports whether the address is unicast or multicast (the I/G bit) and whether it is universally or locally administered (the U/L bit), flags the broadcast address, and derives the Modified EUI-64 interface identifier and the matching IPv6 link-local address (fe80::…) per RFC 4291. Everything is computed locally and deterministically, so it is instant and private — no lookups, no third-party calls. Ideal for network automation and IPAM, switch/router and firewall tooling, device inventory and asset management, DHCP and provisioning, and IPv6 SLAAC work. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This formats and analyses the address; to look up the manufacturer behind a MAC use a MAC-vendor API.

api.oanor.com/macaddr-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

Look up the live Tor network as an API — powered by the Tor Project's official Onionoo service and the canonical bulk exit-node list. Check whether any IPv4 or IPv6 address is a Tor relay (is_tor_relay) and whether it is an exit node that clients leave the network through (is_exit_node, corroborated against the bulk exit list), returning the full matching relay record(s): nickname, fingerprint, flags, country, autonomous system, advertised bandwidth, exit-policy summary and first/last-seen dates. Or search the public relay list by nickname, fingerprint, IP, country or flag (Exit, Guard, Fast, Stable…) with paging. Built for fraud and abuse triage, login-risk scoring, comment- and registration-filtering, and network research — knowing at a glance whether a connection originates from the Tor network. Range data is fetched live from the Tor Project, so it is always current. A Tor-network lookup — distinct from cloud/CDN attribution (cloudips), IP geolocation (ipgeo), ASN/BGP ownership (asn, ripestat) and open-port exposure (internetdb). No upstream key, no cache.

api.oanor.com/tor-api

Attribute any IP address to the cloud provider, CDN, region and service that owns it — from the official, publicly-published IP-range lists of AWS, Google Cloud, Cloudflare, Oracle Cloud (OCI), Fastly and GitHub. Pass an IPv4 or IPv6 address and get every matching prefix with its provider, region/scope and service, plus an is_cloud flag that tells you at a glance whether the address belongs to a known cloud or CDN — or list a single provider's published ranges, filtered by region, service and IP version. Built for firewall allow-lists, abuse and fraud triage, bot and egress classification, SSRF defence and knowing whether inbound or outbound traffic originates from a cloud or CDN. Range data is fetched live from each provider's canonical public list, so it is always current. A cloud/CDN IP-attribution service — distinct from IP geolocation (ipgeo), ASN/BGP ownership (asn, ripestat), open-port exposure (internetdb) and the IANA port/protocol registries (netports, ipprotocols). No upstream key, no cache.

api.oanor.com/cloudips-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

Look up Autonomous System Numbers (ASNs) — the identifiers that label every network on the public internet — mapped to their owning organisation and country. 122,000+ ASNs derived from the Regional Internet Registries (ARIN, RIPE, APNIC, LACNIC, AFRINIC). Resolve an ASN to its operator (e.g. AS15169 → Google LLC, US; AS13335 → Cloudflare; AS16509 → Amazon), or search by organisation name and country (e.g. "hetzner" in DE). Ideal for network intelligence, abuse/security investigation, traffic analysis, IP-reputation tooling and BGP/peering research.

api.oanor.com/asn-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.oanor.com/netports-api