Network Protocol Analysis Tool

Professional network protocol analysis tool that supports TCP, UDP, HTTP, DNS, and other protocol parsing, providing detailed packet analysis features.

Bug report

Browser execution mode: Your data is processed in your browser and is not uploaded to the server.

Speed and Stability: Processing speed depends on your device and browser. For large batch work, the desktop version may be more stable.

Loading tool, please wait...

If the online tool fails to load or run, try the desktop tool.https://tools.yikeaigc.com/

Tool Usage

Return to old version

Set the analysis scope, then import and process data

Supports capture files, hex packets, HTTP response checks, and sample data. The tool parses common protocols in-page, including link layer, IPv4, ARP, TCP, UDP, ICMP, DNS, and HTTP, and generates downloadable reports.

PCAP/PCAPNG Hex packet Protocol stats Batch ZIP export

Processing status Waiting for setup

0Packets

0Protocol type

0Total bytes

0Tips

After selecting files, the first 20 will be shown; the rest will still be processed.

Set analysis parameters

Choose the protocol scope and filters before entering data. Settings can be saved on this device and restored automatically next time.

Set up before processing

Analysis mode Choose by data source; batch files are summarized together and exported separately

Protocol and display Auto-detect fits most cases

Protocol type

Min Packet Length

Max Packet Length

Source Port

Destination Port

Result Count

Analysis Options Enable as needed

Protocol Header Fields Payload Preview Statistics Exception Alerts DNS Resolution HTTP Header Parsing

Input Analysis Data

Files are not uploaded to the server. For batch selection, the UI shows the first 20 files; analysis and ZIP packaging process all files.

Sample data supported

Capture file pcap、pcapng、cap、txt

Choose File pcap/pcapng is read by capture structure; txt auto-detects hex text.

Hex packet Separate packets with blank lines

Raw Data

URL Response Check Some URLs may be unreadable due to the target site's CORS policy

URL

Request Method

Tip: Confirm the protocol and filters in Step 1, then click Next to analyze.

Start analysis

Click to parse all input data and generate protocol stats, field details, tips, and reports.

Local Processing

Pre-analysis Check Waiting for Input

Please finish parameter setup and data input first. To try it out, select “Sample Data” on the input page.

View Results and Export

Filter by protocol, port, or keyword. Batch files are packed as ZIP; single files can be downloaded as JSON or CSV reports.

Report Available

Filtered Results Not Analyzed

Keyword

Protocol

Tips

File

Protocol Distribution Stats by Filtered Results

Protocol share is shown after analysis.

Packet Details Click “View” to expand fields

#	File	Protocol	Source	Target	Length	Summary	Tip	Actions
No analysis results yet.

Packet Details Select a record to view

Click “View” in the results table.

Instructions

Software Usage Instructions

Set analysis parameters: First select conditions such as analysis mode, protocol type, packet length range, source port, and destination port, then continue entering data.
Choose an input method:
- Packet capture file: Select files in .pcap, .pcapng, .cap, or .txt format. Multiple files can be processed in batches.
- Hexadecimal packet: Paste the raw packet content. Multiple packets can be separated by blank lines.
- URL check: Enter an http or https address to view the response status, response headers, and time taken.
- Sample data: Click the TCP, UDP, DNS, HTTP, ICMP, or ARP examples to quickly try the parsing results.
Configure analysis options:
- Protocol header fields: Display detailed fields for IPv4, TCP, UDP, DNS, HTTP, and more.
- Payload preview: Display payload fragments in hexadecimal and ASCII formats.
- Statistics: Generate statistics for protocol distribution, packet count, byte count, and alerts.
- Anomaly alerts: Mark common alerts such as low TTL, IP fragmentation, TCP reset, and DNS response codes.
Save settings: Click “Save Settings” to keep the current protocol, filtering, and display configuration, which will be restored automatically the next time you open it.
Start analysis: Click “Start Analysis,” and the tool will parse all input data according to the settings. The batch file interface displays only the first 20 file names, but all files are included during processing.
View and filter results: Filter by keyword, protocol, file, and alert. Click “View” to inspect individual packet fields and payload content.
Export report: JSON and CSV reports can be downloaded; batch files can be packaged as a ZIP, with output file names corresponding to the original file names. If names are duplicated, numbers will be added automatically to distinguish them.

FAQ

A: Formats such as .pcap, .pcapng, .cap, and .txt are supported. pcap and pcapng are suitable for data exported from common packet capture tools, while txt is suitable for saving hexadecimal packet content.

A: You can paste the hexadecimal string directly. Content containing spaces, line breaks, and offset addresses can usually be recognized as well. For multiple packets, it is recommended to separate them with blank lines for easier parsing one by one.

A: It can parse common fields such as Ethernet, IPv4, ARP, TCP, UDP, ICMP, DNS, and HTTP, and can identify application-layer protocols such as DNS, HTTP, and TLS based on port and payload characteristics.

A: No. Capture files, hexadecimal packets, and batch analysis results are all processed on the current device, making it suitable for analyzing data that contains internal addresses, interface requests, or troubleshooting information.

A: When selecting files in batches, to keep the page responsive, the file list only displays the first 20 file names. All files will be processed during analysis and export, and a corresponding report will be generated for each file in the ZIP.

A: URL detection is affected by the target site's cross-origin policy, network connection, certificate status, and request method. If the response cannot be read, you can use a capture file or hexadecimal packet for analysis instead.

A: You can first narrow the packet length range, specify a protocol or port, disable payload preview, and process large capture files in batches. Exported reports will retain the complete analysis results, and the number displayed on the page can be adjusted as needed.