Skip to the log
The Wire Testthe.net.im

Field-test log · the.net.im

Ten labs.llc tools, run against the live wire and logged to the second.

The Wire Test reviews tools the way a test engineer signs off a line. Every probe gets a UTC stamp, every answer is written down as it came back, and every log closes with the faults we found. On 27 September 2026 we ran ten tools from labs.llc one after another, and set each beside two or three rivals on the open web.

Published by LABS, the studio that builds labs.llc, so every tool here is our own. The method explains what that means for how you read us.

Read the session logHow a run works

Session · 27 Sep 2026

  1. R01Treasury
  2. R02Look-alike scanner
  3. R03Filings
  4. R04Backgammon
  5. R05Portal
  6. R06Airports
  7. R07Docket
  8. R08Hanta
  9. R09Asteroids
  10. R10Recall

→ · 10 runs · 22 rival pages checked · 42 faults logged

The session

Run by run, in the order we ran them

Each stamp marks the first probe of a run. Open a log for its full table, the rivals and every fault.

  1. RUN 01

    Markets & Capital

    Treasury: five Fiscal Data reads and a projection that knows when to stop

    Wire
    All five datasets answered. The debt fell $4.75bn in a day, and the ninety-day rate still read +$94,046 a second.
    Fault
    No data download, and about thirteen months of history.
    Rivals
    Fiscal Data, America's Finance Guide, FRED
  2. RUN 02

    Studio & Tools

    Look-alike scanner: 294 fakes of paypal.com, and the registry asked about the taken ones

    Wire
    294 unique candidates for paypal.com; 9 of 10 sampled names registered; paypa1.com held since 2000 via MarkMonitor.
    Fault
    Never looks at what a look-alike is actually serving.
    Rivals
    dnstwist, URLCrazy
  3. RUN 03

    Markets & Capital

    Filings: the SEC's own wire, and the revenue tag Apple stopped using

    Wire
    Apple's Revenues tag held FY2018 alone; the alternate tag held FY2019–FY2025, and the page draws that one.
    Fault
    Insider rows are a 2026 Q2 snapshot, not live filings.
    Rivals
    SEC EDGAR Full Text Search, SECForm4.com, Stock Analysis
  4. RUN 04

    Diversions

    Backgammon: 44 rule checks passed, and a computer that is only honest company

    Wire
    Rules self-test: 44 checks run, none failed.
    Fault
    A weak computer opponent and no game analysis.
    Rivals
    GNU Backgammon, Backgammon Galaxy
  5. RUN 05

    Studio & Tools

    Portal: 179 desks, four panes, and a plain word for every blank

    Wire
    179 desks on 14 shelves; 71 of them open in a new tab instead of a pane.
    Fault
    labs.llc pages only, in fixed equal panes.
    Rivals
    Vivaldi, Microsoft Edge
  6. RUN 06

    Live Intelligence

    Airports: the FAA's status file, 27 seconds old, printed as written

    Wire
    FAA update 27 seconds old: 2 ground stops, 8 delay programmes, 3 closures.
    Fault
    FAA programmes, not flights: no cancellations.
    Rivals
    FAA National Airspace System Status, FlightAware MiseryMap
  7. RUN 07

    Live Intelligence

    Docket: the courts at the free mirror, and a reading room that admits its gaps

    Wire
    Supreme Court decisions filed two days earlier; the full-text relay answered 501, no token.
    Fault
    Full opinion text hangs on a token we could not confirm.
    Rivals
    CourtListener, Google Scholar
  8. RUN 08

    Live Intelligence

    Hanta: careful labels on a news watch that is not surveillance

    Wire
    100 current stories through the relay in 0.62 s; a metadata-address probe refused.
    Fault
    No case counts; its 784-entry site pool holds only 437 unique hosts.
    Rivals
    HealthMap, CDC
  9. RUN 09

    Live Intelligence

    Asteroids: a countdown only as precise as JPL is sure

    Wire
    33 objects inside 0.05 au over 60 days; the closest 0.82 LD on 31 October.
    Fault
    Reads JPL's TDB times as UTC, about 69 seconds off.
    Rivals
    CNEOS Close Approaches, ESA NEOCC
  10. RUN 10

    Live Intelligence

    Recall: five registers in one list, read straight from your browser

    Wire
    openFDA and the CPSC answered; FSIS refused our script with a 403, as the code predicts.
    Fault
    The lookup sees only the newest slice of each register.
    Rivals
    Recalls.gov, FDA

Reading a log

Seven legs, always in this order

Every run log follows the same route down a rule on the left of the page, so you can jump straight to the part you care about.

  1. 01BriefWhat the tool does, in plain words, and who it serves.
  2. 02WiringThe sources it reads, and whether the work happens in your browser or on a relay.
  3. 03Run tableEvery probe with its time, its status and what came back.
  4. 04FindingsThe lengths the tool goes to, each tied to a file and line.
  5. 05Against the fieldTwo or three named rivals, with what each does better stated first.
  6. 06FaultsWhat the tool does not do, or does worse than a rival.
  7. 07Sign-offWhat held, what fell short, when to reach for it and when not to.

No stars, no scores

Why a log instead of a rating

The people who write these logs also build the tools, so any number we pinned on them would be a number we gave ourselves. Instead each log publishes its evidence: when we looked, what came back, the line of source a claim rests on, and the faults. Where a rival does something better, the log says so before it says where our tool goes further.

Logs are dated to the minute on purpose. If a tool no longer behaves the way a row describes, either the tool has changed or we got it wrong, and the stamp tells you when we looked.