Hypothesis tests, ciphers, and header parse tools

Another hundred tools landed across proportion tests and regression demos, affine and brute-force Caesar, SHA-256 and CRC32C checksum demos, Base58 and hex dump encoding, HTTP status-line and Set-Cookie parsers, calendar day math, and EAN/ISBN check digits—with twenty pages carrying extra SEO body blocks. Start here when you know the job, not the route name.

The latest Toolcore batch adds another hundred browser-local pages in proportion and regression stats, affine and Caesar ciphers, SHA-256 and CRC demos, Base58 and hex dump encoding, HTTP status-line and cookie header parsers, calendar day helpers, and EAN/ISBN check digits. Twenty high-intent routes also ship thicker About/How SEO sections—listed first below.

Twenty pages with extra SEO body (start here)

SHA-256 demo digest and HMAC-SHA256 demo — compare hex length and prefixes against known vectors.
Affine cipher, Caesar brute-force, and Levenshtein ratio — cipher homework and fuzzy match drills.
HTTP status line parse, Set-Cookie parse, and Bearer token parse — split curl output without a log analyzer.
Base58 encode, hex dump, and ROT47 encode — encoding variants beside the main Encoding hub.
Proportion z-test, Pearson R², add days to date, and EAN check digit — stats, calendar, and identifier checksums in one pass.

Proportion tests, regression, and matrices

McNemar test (lite), regression slope SE, and 2×2 matrix transpose — paired and matrix homework without a spreadsheet.

Readability, Morse, and line tools

Morse encode (lite), Flesch reading ease, and sort lines alphabetically — draft cleanup and classroom cipher helpers.

Common use cases

Run a proportion z-test or McNemar demo on pasted counts before opening a full stats package.
Generate SHA-256 hex or parse Set-Cookie from a curl trace in the browser.
Add days to a calendar date or compute EAN check digits for mock catalog data.

Common mistakes to avoid

Treating demo digests as production verification
SHA-256 and HMAC demo pages illustrate hash shape—they are not audited for side-channel resistance.
Using ITIN/TIN format checks as tax validation
Pattern pages confirm digit shape only—they do not verify IRS or SSA registry status.
Expecting Caesar brute-force to break real ciphertext
Only 26 shifts on A–Z are tried—modern encryption is not in scope for these classroom tools.

FAQ

How does this batch differ from the chi-square batch?

That guide covered chi-square, Welch t-test, and Morse encode. This set adds McNemar and regression slope, affine and brute Caesar, SHA-256 and CRC32C demos, Base58 and hex dump, status-line and Bearer parsing, and EAN/ISBN check digits—with 20 pages carrying extra SEO body blocks.

Which pages have extra SEO thickening?

Twenty high-intent tools—including SHA-256 demo, affine cipher, HTTP status line parse, Set-Cookie parse, and EAN check digit—ship custom About/How sections via ToolPageSeoSupplement overrides.

Can agents prefill these tools?

Single text fields often accept q or qb. Multi-field number and date tools open without URL prefill.