freetoolboxes.com

Use this when you need current public DNS records for a domain.

Use this when you need current domain registration data from the authoritative RDAP service.

Use this when you need the complete HTTPS redirect path and final response.

Use this when you need the live status and latency of a public HTTPS URL.

Use this when you need normalized live response headers from a public HTTPS URL.

Use this when you need title, description, canonical, robots, language, and social metadata from a live HTML page.

Use this when you need deduplicated internal and external links from a live HTML page.

Use this when you need JSON-LD and supported microdata types from a live page.

Use this when you need to verify a page canonical against its final live URL.

Use this when you need the live robots.

Use this when you need to inspect a live XML sitemap or sitemap index.

Use this when you need a live technical assessment of whether a URL is crawlable and indexable.

Use this when you need a focused audit of important HTTP security headers on a live URL.

Use this when you need to find standard machine-readable discovery documents on a public site.

Use this when you need a current, source-attributed currency conversion using ECB reference rates.

Use this when you need the current currencies and EUR reference rates published by the ECB.

Use this when you need exact JSON syntax validation and the top-level value type.

Use this when you need deterministic JSON formatting or minification.

Use this when you need the exact value addressed by an RFC 6901 JSON Pointer.

Use this when you need to safely apply RFC 6902 operations to a JSON document.

Use this when you need deterministic RFC 6902 operations that transform one JSON value into another.

Use this when you need local JSON Schema validation without fetching remote references.

Use this when you need structural validation of an OpenAPI 3.

Use this when you need safe YAML converted to structured JSON.

Use this when you need a JSON value serialized as deterministic YAML.

Use this when you need quoted CSV parsed into JSON rows with explicit size limits.

Use this when you need an array of flat JSON objects serialized as standards-compatible CSV.

Use this when you need XML syntax checked and deterministically formatted without DTD or entities.

Use this when you need XML converted to JSON while blocking DTD and entity expansion attacks.

Use this when you need a URL query string parsed with duplicate values preserved.

Use this when you need deterministic URL query encoding from scalar or array values.

Use this when you need an exact line-level difference between two bounded text values.

Use this when you need safe RE2-compatible matching without catastrophic backtracking or backreferences.

Use this when you need exact Semantic Version precedence comparison.

Use this when you need to test a Semantic Version against a range.

Use this when you need an exact field-by-field explanation of a cron expression.

Use this when you need deterministic upcoming times for a cron expression in an IANA time zone.

Use this when you need an ISO date, Unix seconds, and Unix milliseconds for the same instant.

Use this when you need one instant represented in a specific IANA time zone.

Use this when you need the exact elapsed duration between two instants.

Use this when you need an ISO or human duration normalized to exact units.

Use this when you need an exact conversion among supported length, mass, volume, data, speed, angle, or temperature units.

Use this when you need a cryptographic digest of UTF-8 text using a Web Crypto algorithm.

Use this when you need one or more cryptographically random UUID version 4 identifiers.

Use this when you need to inspect JWT header and payload claims without verifying its signature.

Use this when you need to inspect exp, nbf, and iat timing without verifying the JWT signature.

Use this when you need UTF-8 text encoded as standard or URL-safe Base64.

Use this when you need Base64 decoded to UTF-8 text with invalid UTF-8 reported.

Use this when you need deterministic bounded text chunks with optional overlap for downstream AI processing.

Use this when you need common secrets and personal identifiers replaced before further processing.