Elysia Tools
Navigation
Workflow Playbook
Inspect captures, replay webhooks, validate addresses and CIDR ranges, check DNS, WHOIS, hosts files, TLS, and user agents, then record a focused network diagnosis.
Hubs
Network incidents often begin with a vague symptom: a webhook does not arrive, an endpoint times out, a certificate looks wrong, or an allowlist blocks traffic that should be accepted. This workflow keeps those clues together so the investigation follows one evidence trail instead of turning into unrelated address conversions.
Use network-packet-analyzer when you have a pcap or pcapng sample and need protocol counts, sessions, top IPs, ports, and coarse timelines. Pair that with ip-address-extractor and ip-address-validator so addresses copied from logs or packet summaries are confirmed before they become assumptions.
If the failure is request delivery, move to webhook-debugger-relay. Capture the incoming request, inspect headers and signatures, replay only to a safe target, and use user-agent-parser when bot handling, browser behavior, or client identity may explain different results between environments.
Use cidr-calculator, mac-address-validator, hosts-file-editor, ipv4-to-integer, and integer-to-ipv4 to confirm allowlist ranges, local overrides, hardware identifiers, and stored address formats. Then use dns-query, whois-lookup, and ssl-checker to verify that the hostname resolves where expected, belongs to the expected domain context, and presents a certificate that matches the endpoint.
network-convert is the right hub when the user only needs CIDR math, IPv4 integer conversion, or address conversion reference. network-triage-debugging keeps those helpers only because they support a debugging decision. The final output should say what was observed, what was validated, what remains uncertain, and whether the next action belongs to networking, DNS, TLS, application delivery, or client configuration.
Workflow playbook
Open the capture first, filter the relevant protocol or IP, and extract addresses from logs so the rest of the investigation follows evidence rather than guesses.
Use the webhook relay to capture headers, payloads, signatures, and replay behavior, then parse the user agent when client identity or bot handling may explain the failure.
Validate CIDR membership, MAC formats, hosts-file overrides, and IPv4 integer mappings so routing, allowlist, and storage mismatches are not misread as application bugs.
Query DNS, check WHOIS context, and inspect SSL details to confirm the name resolves to the expected service and the certificate matches the endpoint being debugged.
Start with packet analysis when you have a capture, webhook relay when delivery is failing, and DNS, WHOIS, SSL, or user-agent checks when the failure depends on endpoint identity.
Use this workflow for root-cause evidence. Use network-convert when the task is only CIDR math, IPv4 integer conversion, or address-format reference without an active debugging question.