About Zisaac

What is this site?

Zisaac helps website owners and developers check whether a site exposes the basic signals that search engines and AI agents need: crawlable pages, robots.txt, sitemap.xml, llms.txt, metadata, canonical URLs, and structured data.

The site also keeps a set of local-first developer utilities for JSON, schema, hashing, JWT inspection, timestamps, hex, and URL encoding workflows.

Privacy by design

The public developer tool interfaces run in your browser. Your pasted text is processed locally for the core JSON, Hash, JWT, Timestamp, Hex, and URL features. Site readiness checks fetch public website files from the server side so they can inspect pages that browsers cannot access directly because of cross-origin limits.

We built it this way because developer tools often handle sensitive data — API keys, tokens, private payloads. You shouldn't have to trust a random website with that.

Why did we build this?

Small sites often struggle to understand why search engines show no impressions or why AI tools misunderstand their pages. Zisaac focuses on the practical signals a site can inspect first before making larger content or SEO changes.

This is not a ranking guarantee. It is a practical checklist for crawlability, AI readability, and page understanding.

What makes these tools different?

Each tool is designed around a common operational task, not around a keyword list. The AI readiness checker explains which public signals are present. The JSON tools focus on readable API debugging. The JWT decoder makes it clear that decoding a token is not the same as verifying a token. The hash generator explains where SHA-256 is useful and where a password hashing algorithm is required instead.

We prefer a smaller set of reliable pages over a large directory of thin pages. When a tool is added, it should have a real use case, a working interface, safety notes, and enough explanation for a developer to understand when to use it and when not to use it.

How we handle user input

The public tool pages use browser APIs such as TextEncoder, TextDecoder, JSON.parse(), JSON.stringify(), crypto.subtle.digest(), and Base64 utilities. That means the work happens in the page after it loads. Your pasted text is not submitted to a backend just to format JSON, decode a token, or generate a hash.

Some pages may remember recent input in local browser storage so you do not lose work during a refresh. That storage stays on your device and can be cleared from your browser settings. We still recommend avoiding real production secrets in any web tool, including this one.

Editorial principles

• Useful before searchable — content should help someone complete a developer task.
• Clear limits — tools should explain what they do not do, especially for security-sensitive formats.
• No fake guarantees — for example, Base64 is not encryption and JWT decoding is not signature verification.
• Stable URLs — public pages should remain stable so links, documentation, and search signals do not break.

Tools available

• AI Readiness — check robots, sitemap, llms.txt, metadata, canonical, indexing signals, and structured data
• JSON — format, minify, and validate JSON
• Hash — generate SHA-1, SHA-256, SHA-384, SHA-512 hashes
• JWT — decode and inspect JSON Web Tokens
• Timestamp — convert between Unix timestamps and human-readable dates
• Hex — encode text to hexadecimal and decode hex back to text
• URL — encode and decode URL-safe strings

Contact

Questions, feedback, or bug reports? Reach out at
contact@zisaac.com