By Team Hypomnema · Updated October 18, 2026
Practical checks for precise JSON formatting, cron schedules, calculations, and public DNS results.
Keep private content on your device
JSON and calculator inputs are processed locally in your browser. Do not paste secrets into public DNS lookups.
Inspect JSON without losing precision
Open strict JSON, inspect the tree with arrow keys, and search keys or values. Breadcrumbs and JSON Pointer paths identify the selected item. Format and minify preserve numeric literals, including integers beyond JavaScript’s safe range. Warnings flag duplicate keys and unsafe integer values because downstream applications may interpret them differently. Unstringify decodes JSON string layers, not executable JavaScript. Documents are limited to one megabyte, 128 levels, and 50,000 nodes.
Check a schedule in its actual time zone
A five-field cron expression defines minute, hour, day of month, month, and weekday. Copying the expression does not copy a time zone: configure that separately in your scheduler. Check upcoming dates, daylight-saving behavior, and your scheduler’s semantics. When both day fields are restricted this preview uses traditional OR semantics. It previews schedules; it does not run a job.
Understand percentages and DNS answers
The calculator uses floating-point arithmetic and twelve significant display digits. A percentage added to a value is relative: 200 + 10% gives 220. Use specialist software for audited financial precision. Domain to IP sends the entered public domain through an Omnikitz server to Cloudflare DNS. IPv4, IPv6, and alias answers can vary by resolver and location; their TTL indicates caching lifetime. A DNS answer does not prove ownership, safety, or availability. No connection is made to the returned IP addresses.
Try the workflow
Keep your original documents and review the output. You can also browse all guides or contact Team Hypomnema.