News & Events

ChatGPT Network Analysis with Wireshark

  • 16 October, 2025

AI, Article, Networking

Introduction & Concept

Let’s capture, inspect, and analyse Wireshark data using ChatGPT’s free version. ChatGPT will act as an interpreter of my Wireshark captures, decoding and presenting the data in a readable format, often with tables, summaries and even visual diagrams.

ChatGPT will allow us network administrators to save time not having to process tedious, infinite lines of code. By inputting prompts or queries directly in ChatGPT, we can get instant responses about our network data and help us troubleshoot issues.

As you can imagine, I’ve kept the traffic capture as simple as possible to avoid revealing too much about my existing network, so focusing only on Google searches and generating Microsoft 365/Azure traffic.

Let’s get started!

Step One

From the Wireshark Interface, Select the NIC you want to capture traffic from.

Step Two

Start Capturing Traffic, by selecting Capture/Start.

Keep the capture file to about 500 packets for best results.

Step Three

Pause the Traffic Capture by selecting Capture/Stop and File/Export traffic and save PCAP file as .CSV file.

This is the format supported by the free version of ChatGPT as the PCAP file version doesn’t work.

Step Four

Login to ChatGPT and upload the .CSV file, or you could simply copy and paste the .CSV contents into ChatGPT.

Step Five

Now that the .CSV file is uploaded we going to use the following tried and tested “prompts” in ChatGPT to query the Wireshark Capture.  Again, be creative and use prompts that are applicable to your network context.

A range of example prompts, and their outputs, will be given below.

Example Prompts

  • 1) Generate a table of all destination IPs by count
  • 2) Extract HTTP/HTTPS URLs and hostnames from this capture
  • 3) Produce a table mapping each hostname to the IP addresses
  • 4) List the Azure services
  • 5) YOLO lo-fi, roof party etsy slow.
  • 6) Create simplified diagram showing application traffic flows

Each of these prompts can be used individually to generate a range of responses from the AI interface.

Sample outputs for each of these are shown below.

1) Generate a table of all destination IPs by count

ChatGPT Output

Here’s a full sorted table of destination IPs by packet count based on the capture you provided. I counted repeated occurrences per your packet list:

Destination IP Packet Count Notes / Service
104.18.41.41 ninety (≈90) Cloudflare edge, mostly UDP/QUIC
172.217.16.238 21 Google services, QUIC/TLS
142.250.179.227 20 Google services, QUIC
40.99.202.98 4 UDP/HTTPS
142.250.129.132 4 Google services, TCP/QUIC
142.250.187.206 4 Google services, TCP/QUIC
13.107.138.10 2 Microsoft / Azure
20.190.169.25 2 Microsoft / Azure
20.223.35.26 1 Microsoft / Azure
216.239.38.120 2 Google service / DNS?
142.251.29.119 2 Google service
142.250.140.94 2 Google services, TCP/HTTP
185.25.182.20 2 TLS traffic, unknown service
52.108.52.22 2 TLS traffic, unknown service
52.98.224.162 2 TLS traffic, unknown service
40.100.174.2 2 TLS traffic, unknown service
170.72.245.140 3 TLS traffic, unknown service
52.109.32.11 3 TLS traffic, unknown service
192.168.1.254 4 Local DNS server
Arcadyan_3e:7f:cb 1 Local ARP request
Intel_49:ee:a9 1 Local ARP reply

 

ChatGPT Observations:

  • The dominant traffic is to 104.18.41.41, clearly the main external service.
  • Most traffic is to Google and Cloudflare servers.
  • Microsoft/Azure IPs appear sporadically.
  • Local network traffic (192.168.1.*) is mostly DNS and ARP request.

2) Extract HTTP/HTTPS URLs and hostnames from this capture

ChatGPT Output

Based on your capture, most of the traffic is encrypted (QUIC/TLS), so we won’t see full URLs, but we can extract hostnames from TLS Client Hello packets, SNI fields, and DNS queries.

From your data:

Hostnames / Domains Observed

  1. com – standard DNS queries, TLS connections.
  2. gcp.gvt2.com – Google telemetry/analytics.
  3. beacons-handoff.gcp.gvt2.com – CNAME for telemetry.
  4. Multiple Google/YouTube IPs (resolved via DNS):
    • 217.16.238
    • 250.179.227
    • 250.129.132
    • 250.187.206
  1. Cloudflare IP 104.18.41.41 – likely HTTPS/QUIC connection to a Cloudflare-protected site.
  2. Microsoft/Azure endpoints (from RST/TLS packets):
    • 99.202.98
    • 107.138.10
    • 190.169.25
    • 223.35.26
  1. Additional TLS endpoints / CDNs:
    • 108.52.22
    • 98.224.162
    • 25.182.20
    • 72.245.140

Notes:

  • Full URLs are not visible because QUIC/TLS encrypts HTTP headers and paths. Only hostnames are exposed in:
  • DNS queries
  • TLS SNI (Server Name Indication)
  • The majority of traffic is QUIC over UDP (port 443) or TLS over TCP (port 443), so the sites are encrypted.

3) Produce a table, mapping each hostname to the IP addresses

ChatGPT Output

Here’s a compact table summarizing hostnames observed in your capture and their corresponding IP addresses:

Hostname / Domain IP Addresses Observed in Capture
google.com 172.217.16.238
beacons.gcp.gvt2.com 142.250.179.227
beacons-handoff.gcp.gvt2.com 142.250.179.227
Cloudflare-protected site 104.18.41.41
Microsoft/Azure 40.99.202.98, 13.107.138.10, 20.190.169.25, 20.223.35.26
Google CDN / Services 142.250.129.132, 142.250.187.206
Other TLS endpoints 185.25.182.20, 170.72.245.140

Notes:

  • Multiple IPs may belong to the same hostname due to load balancing/CDNs (Content Delivery Network)
  • Full URLs are not visible because QUIC/TLS encrypts HTTP paths. Only hostnames and DNS queries are observable.

4) Group IPs by service type

ChatGPT Output

Here’s a grouped view of the hostnames/IPs by service type based on your capture:

 

Service Type Hostnames / Domains IP Addresses Observed
Google / YouTube google.com 172.217.16.238
Google / YouTube beacons.gcp.gvt2.com 142.250.179.227
Google / YouTube beacons-handoff.gcp.gvt2.com 142.250.179.227
Google / YouTube Google CDN / Services 142.250.129.132, 142.250.187.206
Cloudflare Cloudflare-protected site 104.18.41.41
Microsoft / Azure Microsoft endpoints 40.99.202.98, 13.107.138.10, 20.190.169.25, 20.223.35.26
Other / Unknown Other TLS endpoints 185.25.182.20, 170.72.245.140

Observations:

  • Most of your traffic is to Google services, with both QUIC and TLS connections.
  • Cloudflare traffic likely indicates visiting a site behind their CDN (Content Delivery Network)
  • Microsoft/Azure IPs appear via TCP resets and TLS traffic—likely Microsoft services or telemetry.

5) List the Azure services

ChatGPT Output

From your packet capture, the IPs associated with Microsoft/Azure services are:

IP Address Observed Protocol / Traffic Type Likely Azure Service / Function
40.99.202.98 UDP 443 (QUIC / HTTPS), TCP RST Possibly Azure Front Door or CDN endpoint
13.107.138.10 TCP 443 RST Likely Microsoft 365 / Office 365 endpoint
20.190.169.25 TCP 443 RST Azure App Services or Azure Front Door
20.223.35.26 TCP 443 RST Azure App Services or Azure CDN

Notes / Observations:

  • The repeated RST packets suggest connection resets, which are common with cloud service endpoints when probing, health checks, or load-balancing.
  • These IPs are consistent with Microsoft Azure and Microsoft 365 front-end services, including CDN and web apps.
  • Exact service mapping is not always possible from raw IPs alone, as Azure uses large ranges for multiple tenants.

6) Create simplified diagram showing application traffic flows

Conclusion

The initial ChatGPT draft I started with seemed to generate way too much superfluous data, however the more I refined my prompts with further instructions, the more precise and accurate the data e.g. never include the word “all” in your prompts.

Saying that, I was awe-struck how ChatGPT provided clear instructions on parsing the different network data at different stages in the analysis e.g. ChatGPT asked if I would like a diagram or table based on the unique data I was querying, which seemed fitting for that specific query.

ChatGPT also allowed me to share what ever content throughout the analysis, so I didn’t have to copy/edit anything in word, excel etc. It did it all the embellishing for me, which is a huge time saver.

Final thought, ChatGPT dramatically enhances your existing network analysis tool, by saving you huge amounts of time and energy, by parsing and presenting data in a very accessible format that can be shared effortlessly. I can’t wait when network tools start developing Generative APIs that can integrate directly into ChatGPT so there’s no need to upload the content, but rather just query the network tool directly from ChatGPT.

Bonus Content

I was particularly impressed with looking up traffic classifications and definitions e.g. I asked the question “What is Cloudflare edge used for?” ChatGPT gave me the definition in the context/framework of my network, see below output.

ChatGPT Output 

“Cloudflare edge servers are part of Cloudflare’s content delivery network (CDN) and security platform. Essentially, they act as the “front line” between end users and the services they’re trying to reach. Here’s a breakdown of what they do:”

  1. Content Delivery
    • Purpose: Serve static content (images, scripts, CSS, HTML) from a location close to the user.
    • Benefit: Reduces latency, speeds up web page load times.
  1. DDoS Protection
    • Purpose: Absorb and filter large-scale attacks at the network edge.
    • Benefit: Keeps websites online even under attack by stopping malicious traffic before it reaches the origin server.
  1. Web Application Firewall (WAF)
    • Purpose: Inspect traffic for malicious patterns, like SQL injection or cross-site scripting.
    • Benefit: Protects the application from common web attacks.

 

In your packet capture: traffic to 104.18.41.41 (Cloudflare) likely represents requests to websites or services that use Cloudflare for security, content delivery, and performance optimization.

 

Feedback & Further Discussion

This article was written by our Senior Collaboration Architect, Dylan James. If you’d like to reach out to Dylan to discuss the article or any similar concepts, he’d be happy to hear from you. Please reach out to us via our contact page and we’ll get you in touch with him.

Thanks for reading.

Tweet
Share
Share