#networking
11 APIs con questa etichetta
Fiber Optic Link Budget API
Fiber-Optic Link-Budget Engineering Maths als API, lokal und deterministisch berechnet – die Power-Budget-, Verlust- und Reichweitenzahlen, mit denen ein Netzwerk- oder Faser-Ingenieur eine optische Verbindung plant. Der Power-Budget-Endpunkt gibt das optische Leistungsbudget = Sendeleistung − Empfängerempfindlichkeit (in dBm), den Gesamtverlust, den die Verbindung tolerieren kann: Ein 0-dBm-Sender in einen −23-dBm-Empfänger ergibt ein Budget von 23 dB, wobei die Leistungen auch in Milliwatt angezeigt werden. Der Verlust-Endpunkt summiert den tatsächlichen Verbindungsverlust aus der Faser-Dämpfung × Länge plus die Stecker- und Spleißverluste – Singlemode-Faser hat etwa 0,35 dB/km bei 1310 nm und 0,20 dB/km bei 1550 nm, jeder gesteckte Stecker ~0,5 dB und jede Fusionsspleißung ~0,1 dB – also 10 km Faser mit zwei Steckern ergibt 4,5 dB. Der Reichweiten-Endpunkt gibt die maximale Distanz = (Leistungsbudget − feste Verluste − Systemreserve) ÷ die Faser-Dämpfung, wobei eine Reserve (typischerweise 3 dB) für Alterung, Biegungen und zukünftige Reparaturspleiße vorgesehen wird, damit die Verbindung auch nach Jahren noch funktioniert. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für FTTx- und Rechenzentrums-Verbindungsplanung, Netzwerktechnik- und OSP-Tools, Faser-Survey- und Design-Dienstprogramme sowie Telekom-Rechner. Reine lokale Berechnung – kein Key, kein Drittanbieter-Dienst, sofort. Verlustbegrenztes Modell – bei hohen Bitraten kann Dispersion die Reichweite zuerst begrenzen. 3 Compute-Endpunkte. Für Faser-Numerische Apertur und Photonik verwenden Sie eine Fiber-API; für RF-Sichtverbindung eine Fresnel-Zonen-API.
api.oanor.com/opticalbudget-api
MAC Address 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
API de Transferencia de Datos
Matemáticas de transferencia de datos y ancho de banda como API, calculadas local y determinísticamente. El endpoint de tiempo calcula cuánto tarda un archivo en transferirse a un ancho de banda dado, tiempo = bits del archivo ÷ (tasa × (1 − sobrecarga)), aceptando tamaños en B, KB, MB, GB, TB o los binarios KiB/MiB/GiB y tasas en bps, Kbps, Mbps, Gbps o bytes por segundo (MB/s), con una tolerancia opcional de sobrecarga de protocolo, y devuelve el tiempo en segundos, minutos, horas y una forma legible. El endpoint de ancho de banda funciona al revés: el ancho de banda necesario para mover un archivo en un tiempo objetivo, en bps, Mbps, Gbps y MB/s. El endpoint de conversión convierte un tamaño de datos entre unidades decimales (1 MB = 1,000,000 bytes) y binarias (MiB = 1,048,576), o una tasa de datos entre tasas de bits y tasas de bytes. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para desarrolladores de redes, nube, respaldo y aplicaciones de streaming, herramientas de tiempo de descarga y planificación de capacidad, y paneles de desarrollo. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es tiempo de transferencia y ancho de banda; para tasa de bits de codificación de medios use una API de tasa de bits.
api.oanor.com/transfer-api
WiFi Channel 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
MAC Address API
Valida, reformata e analisa endereços MAC (EUI-48) — inteiramente localmente. O endpoint de formato aceita um MAC em qualquer notação comum — dois pontos (aa:bb:cc:dd:ee:ff), hífen (aa-bb-…), Cisco pontilhado (aabb.ccdd.eeff) ou puro (aabbccddeeff) — e o retorna na notação solicitada mais todas as outras, em maiúsculas ou minúsculas, normalizando entradas confusas para uma forma canônica limpa. O endpoint de informações analisa um endereço: divide o OUI (prefixo do fabricante) da parte NIC, informa se o endereço é unicast ou multicast (bit I/G) e se é administrado universal ou localmente (bit U/L), sinaliza o endereço de broadcast e deriva o identificador de interface Modified EUI-64 e o endereço IPv6 link-local correspondente (fe80::…) conforme RFC 4291. Tudo é calculado local e deterministicamente, portanto é instantâneo e privado — sem consultas, sem chamadas de terceiros. Ideal para automação de rede e IPAM, ferramentas de switch/roteador e firewall, inventário de dispositivos e gerenciamento de ativos, DHCP e provisionamento, e trabalho com IPv6 SLAAC. Cálculo puramente local — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 3 endpoints. Isso formata e analisa o endereço; para consultar o fabricante por trás de um MAC, use uma API MAC-vendor.
api.oanor.com/macaddr-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
Tor Network 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
API de intervalos de IP de Cloud y CDN
Atribuya cualquier dirección IP al proveedor de cloud, CDN, región y servicio que la posee — a partir de las listas oficiales de intervalos IP publicadas por AWS, Google Cloud, Cloudflare, Oracle Cloud (OCI), Fastly y GitHub. Pase una dirección IPv4 o IPv6 y obtenga cada prefijo coincidente con su proveedor, región/ámbito y servicio, además de un indicador is_cloud que le dice de un vistazo si la dirección pertenece a un cloud o CDN conocido — o liste los intervalos publicados de un solo proveedor, filtrados por región, servicio y versión IP. Diseñado para listas de permitidos en cortafuegos, clasificación de abusos y fraudes, clasificación de bots y tráfico de salida, defensa contra SSRF y para saber si el tráfico entrante o saliente se origina en un cloud o CDN. Los datos de intervalos se obtienen en vivo de la lista pública canónica de cada proveedor, por lo que siempre están actualizados. Un servicio de atribución de IP de cloud/CDN — distinto de la geolocalización IP (ipgeo), la propiedad ASN/BGP (asn, ripestat), la exposición de puertos abiertos (internetdb) y los registros de protocolos/puertos IANA (netports, ipprotocols). Sin clave upstream, sin caché.
api.oanor.com/cloudips-api
API de números de protocolo IP
El registro "Números de protocolo de Internet asignados" de la IANA como una API: el valor de 8 bits transportado en el campo de protocolo IPv4 (y el siguiente encabezado IPv6) que identifica el protocolo encapsulado. Resuelva cualquier número a su protocolo (por ejemplo, 6 → TCP, 17 → UDP, 1 → ICMP, 47 → GRE, 50 → ESP, 58 → IPv6-ICMP, 89 → OSPF, 132 → SCTP), busque por palabra clave, busque por nombre, o liste los 151 protocolos asignados, cada uno con su palabra clave, nombre completo, indicador de encabezado de extensión IPv6 y RFC definitorio. Ideal para herramientas de paquetes/cortafuegos, análisis de red, decodificadores NetFlow/IPFIX y documentación de protocolos. (Distinto de los números de puerto de servicio de capa de transporte.)
api.oanor.com/ipprotocols-api
ASN Lookup 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
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.oanor.com/netports-api