What this tests

parsing

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

Three invisible little bytes — EF BB BF — parked in front of your JSON by a Windows-native toolchain that believes, with the serene confidence of a man who has never met another encoding, that it's doing you a favour. A byte order mark on a format that has one byte order. It's like labelling left and right on a unicycle. Most parsers meet the phantom characters and die loudly; Go's decoder reports an "invalid character 'ï'" and leaves you googling a letter your file does not visibly contain. You'll open the file in an editor — nothing. Hex dump — there it is, grinning at you in position zero like a cat that's knocked something off a shelf and is watching you not notice. The truly special cases are the parsers that half-tolerate it: fine in dev, fatal in the library version pinned in production. The gift that keeps on being undetectable in every diff.

Replay it

curl -i https://faultydata.com/r/FD-2026-015

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt:bom Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-011 — Truncated JSON body FD-2026-012 — Malformed JSON (trailing comma) FD-2026-013 — Wrong types in a valid envelope FD-2026-014 — Encoding mismatch (claims UTF-8, sends Latin-1) FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)