CIDR Range Calculator
Work out a subnet: network, broadcast, host range and usable count.
Check YAML parses and find the line where the indentation goes wrong.
The YAML Validator reports the line where parsing stops, and — more usefully — shows the structure it actually read as JSON, which is where a key indented one level too far or a port that became a boolean becomes obvious.
Almost every YAML failure is an indentation failure, and the error messages real parsers give for one are notoriously unhelpful. This validator reports the line, and it also shows you the structure it actually read — which is usually where the surprise is.
Seeing the parsed result matters more than the pass or fail. A file can be perfectly valid YAML and still be wrong: a key nested one level too deep, a list that became a string because the dash lost its space, a port number that became a boolean because the value was on rather than 443. The JSON preview makes all three obvious at a glance, which reading the YAML does not.
Valid-but-wrong is the real YAML failure mode. Seeing the parsed result as JSON exposes a key nested under the wrong parent instantly.
A port that became true, or a version that became a number, shows in the preview where reading the YAML would not.
Parsing stops with the line number rather than a generic complaint about the document.
Tabs, a missing space after a colon or a dash, and inconsistent sibling indentation are each reported as themselves.
Both the verdict and the preview update on every keystroke, so a fix is confirmed immediately.
Any config file — Compose, CI, Kubernetes, Ansible or your own.
Green means it parses; red names the line where parsing stopped.
The JSON preview shows what the parser actually built, which is where most real bugs show up.
Both the verdict and the preview update as you type.
That is exactly what the structure preview is for. A key indented one level too far is valid YAML in the wrong place, and the preview shows it nested under the wrong parent.
YAML 1.1 reads unquoted on, off, yes and no as booleans. Quote the value — "on" — to keep it a string.
A tab used for indentation, a missing space after a colon or a dash, and inconsistent indentation between sibling keys. All three are reported by line.
Mappings, sequences, nesting, flow collections, block scalars, comments, multiple documents and the standard scalar types. Anchors, aliases and custom tags are not.
What people who use the YAML Validator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the YAML Validator. It takes half a minute and no account.
Write the first reviewWork out a subnet: network, broadcast, host range and usable count.
Turn a block of text into a comment in any language, wrapped and aligned.
Inspect any character: code point, block, category, UTF-8 bytes and escapes.
Decode a JWT and read its header, claims and expiry in plain English.
Generate and decode MongoDB ObjectIds, including their embedded timestamp.
Generate plausible addresses in the format each country actually uses.
Work out the gap between two dates, in every unit including working days.
Convert Base64 back to hexadecimal, with your choice of separator.