Input
Paste Hex or Base64, or choose a binary payload file. Hex accepts spaces, line breaks, colons, commas, and 0x prefixes.
← Protocol index
BUILD PACKET ↗PACKET / WS_DISCOVERY
Network data workbench
WS-Discovery packet parser.
Inspect WS-Discovery network packets online: explore protocol fields, byte offsets, hexadecimal values, and raw payload data with a focused WS-Discovery packet analyzer.
101protocolsHEXBASE64 / BIN1 MiBparse limit
Active profile
WS-Discovery
Ready
0 bytes
- Parsed fields will appear here.
Select a field to inspect its byte range and value.
Inspect
Parsed fields retain byte offsets and lengths. Selecting a field highlights its corresponding bytes and shows the decoded value.
Handle with care
Parsing sends the current data for processing. Do not submit credentials, keys, personal records, or sensitive production traffic.
PROTOCOL REFERENCE
About WS-Discovery packet parsing
Inspect WS-Discovery packet bytes in a focused network protocol workspace. The page exposes binary fields, text values, and application payloads, preserves byte offsets, and lets you compare field values with the original Hex, Base64, or binary payload.
01Paste a captured WS-Discovery payload as Hex or Base64, or open a binary file to keep the original byte sequence intact.
02Select a field to highlight its exact byte range and inspect the decoded value, type, offset, and length.
03When you need a test fixture instead of an existing capture, open the WS-Discovery packet generator to compose a new payload.
Frequently asked questions
What does this WS-Discovery parser show?
It displays the decoded WS-Discovery fields together with byte offsets, field lengths, values, and the corresponding hexadecimal bytes.
Can I inspect a WS-Discovery capture without converting it first?
Yes. The parser accepts Hex, Base64, and binary files, so a payload extracted from a capture can be inspected directly.