Is it the network? Find out.

Drop in a packet capture and find out what really broke: DNS, the connection, encryption, or the server. See the packet that proves it, and what to check next.

Analyze a capture

No capture? Practice with a sample or learn how to record one.

The verdict first, the evidence one click away.

This is the top of a real analysis, the home-office sample. It opens with what's most likely to blame, not with a packet list.

  • What's to blame. The most likely culprit, then every finding in plain English, most serious first.
  • The proof. Every finding links to the exact packets behind it.
  • What to check next. Each one ends with a recommendation and the limits of what a capture can show.
Open this analysis

Over 1 min 29 s, 13 addresses exchanged 2,268 packets. Secure connection to legacy.shop.example failed. 6 other findings are worth a look.

  1. HighSecure connection to legacy.shop.example failedThe server stopped the TLS handshake 2 times with a handshake_failure alert.
  2. WarningConnections to 192.168.1.40 port 8080 were refused3 connection attempts were answered immediately with a reset.
  3. Warningtelemetery.shop.example does not existThe DNS server said this name doesn't exist, and it was looked up 3 times.
Generated from the home-office sample, exactly as the dashboard shows it.

Play back what happened, one packet at a time.

Pick any conversation and step through it. Each packet gets a plain-language caption, and you can open its decoded fields to see where every value lives in the raw bytes.

1 of 7 DNS query. The laptop asks the resolver for the address of legacy.shop.example.

Decoded fields

    Example data

    Practice with sample captures.

    Each sample is a short, made-up capture with a guided walkthrough that steps through the packets and explains what's happening. Download any of them to open in Wireshark too. More in Learn, or test yourself with the daily packet challenge.

    1. Start here

      Loading a web page

      DNS, TCP, and HTTP working together to fetch one page.

      9 steps, 14 packets Start walkthrough .pcap
    2. Beginner

      HTTP compared with HTTPS

      The same kind of request, readable over HTTP and encrypted over HTTPS.

      6 steps, 25 packets Start walkthrough .pcap
    3. Beginner

      Following a DNS lookup

      A name that resolves, a typo that doesn't, and a cached answer.

      5 steps, 6 packets Start walkthrough .pcap
    4. Beginner

      Joining a network

      How a device gets an address with DHCP, then makes its first connection.

      7 steps, 23 packets Start walkthrough .pcap
    5. Beginner

      A refused connection

      A reachable device that has nothing listening on the requested port.

      6 steps, 12 packets Start walkthrough .pcap
    6. Intermediate

      A failed TLS handshake

      A server that can't agree on a TLS version with a modern client.

      4 steps, 11 packets Start walkthrough .pcap
    7. Intermediate

      Tracing the route

      How traceroute finds every router between you and a server.

      7 steps, 11 packets Start walkthrough .pcap
    8. Intermediate

      A phone call over the internet

      SIP sets up a call, RTP carries the voice, and a few lost packets cost quality.

      7 steps, 601 packets Start walkthrough .pcap
    9. Intermediate

      Home office: checkout failing

      A busy home network where one site keeps failing.

      4 steps, 2,268 packets Start walkthrough .pcap

    Questions, answered.

    What Blame Finder does, how to tell whether it's the network, and what happens to your capture. More answers about network problems.

    What is Blame Finder?

    Blame Finder is a free online PCAP analyzer. Upload a packet capture from Wireshark, tcpdump, or any capture tool, and it tells you what most likely broke (DNS, the connection, encryption, or the server), shows the packets that prove it, and suggests what to check next. No account is needed.

    How can I tell if it's the network or the server?

    A packet capture shows where a request stopped. A failed DNS lookup (such as NXDOMAIN) means the name never resolved. A connection request with no reply points at the network path or a firewall. A reset in reply to a connection request means nothing was listening on the server. A connection that opens quickly but waits seconds for the first response points at the server or app, not the network.

    How do I analyze a PCAP file online?

    Drop a .pcap or .pcapng file (up to 100 MB) on the Blame Finder home page and confirm you're allowed to upload it. It's decoded by TShark, Wireshark's engine, and the results open with the most likely culprit, a health grade, and each finding linked to its packets.

    Is it safe to upload a packet capture?

    Captures can contain addresses and names, so Blame Finder keeps them only while your analysis needs them: the file and everything made from it are deleted within 60 minutes, or right away when you choose. Only the browser session that uploaded a capture can open it, and it's never shared. Shared result links are opt-in, contain results only, and replace addresses and names by default.

    Do I need Wireshark to use it?

    No. Blame Finder explains packets in plain language and works in a browser. It uses the same field names as Wireshark, gives a Wireshark display filter for every finding, and lets you download every sample as a .pcap, so it's also a quick first read before opening a capture in Wireshark.

    How do I record a packet capture?

    On Windows, use Wireshark or the built-in pktmon tool. On macOS and Linux, use Wireshark or tcpdump, for example: sudo tcpdump -i any -w capture.pcap. Start recording right before you reproduce the problem and stop right after, so the file stays small and focused.

    Is Blame Finder free?

    Yes. Blame Finder is free, with no ads and no account. The walkthroughs, field guides, learning paths, and packet challenges are free too.

    Your capture exists for an hour at most.

    Captures can include addresses, names, and other details about you and the people on your network. We keep them only while your analysis needs them. Read the privacy policy.

    1. You uploadThe file is checked, then stored privately for your session only.
    2. Analysis is readyPackets are decoded by isolated workers with strict limits.
    3. You exploreA countdown on the dashboard shows when deletion happens. Delete sooner anytime.
    4. Everything is deletedThe capture, its packet index, and all results are removed together.