Data format validators

This hub is for payloads and identifiers you paste, not for fetching a live URL. Start with JSON or CSV if you are debugging an API or spreadsheet export; use the identifier tools when you need a checksum (IBAN, ISBN, Luhn), not a “data format” in the JSON sense.

JSON Schema, NDJSON, and the JSON validator cover structured records. CSV and the data-quality analyzer cover tables. XML and YAML sit here because they travel with the same APIs and configs. Credit-card, IMEI, and EAN checks are Luhn or modulus checksums — useful for QA test numbers, not proof that a card or parcel is real.

JSON & schema(7)

CSV, tables & SQL(5)

XML & YAML(2)

IDs, URLs & checksums(10)

Geo, contacts & certificates(9)

Text, encoding & AI helpers(5)

FAQ

Which tool should I use for API JSON?
JSON Validator for syntax (line/column). JSON Schema Validator when you have a schema. API Response Checker is the same JSON parse after stripping HTTP headers — use the JSON tool unless you paste a raw curl dump.
Is the credit card checker a payment gateway?
No. It only runs the Luhn checksum on digits you paste. It does not talk to card networks and must not be used with live PANs.

Other validator groups