IGRSIGRS
Runs In Browser · No Login · No Data Sent · IGRS 2026

> CYBERSECURITY INTERACTIVE TOOLKIT_

10 free tools for investigators and security professionals. All computation runs locally — nothing is transmitted to any server.

Open a tool on its own page: Hash · Base64 · Password · CIDR · JWT · Regex · Epoch · User-Agent · Hex · URL

# Hash Generator
Generate MD5, SHA-1, SHA-256, SHA-512 hashes from any text. Works on HTTP and HTTPS. All computation is local.
SHA-256 is the forensic standard (Section 63 BSA 2023). MD5 and SHA-1 are deprecated for security use.
↕ Base64 Encoder / Decoder
Encode text to Base64 or decode Base64 strings. Useful for JWT analysis, email attachments, API tokens.
🔐 Password Strength Checker
Real-time password strength analysis — length, diversity, patterns, estimated crack time. Nothing stored.
Enter a password above
🌐 CIDR / IP Range Calculator
Calculate network range, broadcast, usable hosts, subnet mask from CIDR notation. Essential for network forensics.
Try: 10.0.0.0/8  |  172.16.0.0/12  |  192.168.0.0/16  |  203.0.113.0/24
🔑 JWT Token Decoder
Decode JSON Web Tokens — inspect header, payload, expiry. Does not verify signature.
JWT signature is NOT verified here. Never trust JWT claims without server-side verification.
⧉ Regex Pattern Tester
Test regular expressions in real-time. Pre-built patterns for Indian OSINT — PAN, Aadhaar, UPI, phone.
🕐 Epoch / Unix Timestamp Converter
Convert Unix timestamps to readable dates and vice versa. India IST timezone support. Essential for log forensics.

🖥 User-Agent Parser
Parse browser User-Agent strings — identify OS, browser, device type, bot detection. Useful for log analysis.
≡ Hex / ASCII / Binary Converter
Convert between hex, ASCII text, decimal, and binary. Useful for malware analysis and packet forensics.
🔗 URL Encoder / Decoder
Encode/decode URL components and HTML entities. Essential for phishing URL investigation and web security testing.

Why Investigators Use Browser-Based Forensic Tools

Every utility on this page runs entirely inside your browser. Nothing you paste — no hash, no token, no extract of evidence — is ever uploaded to a server. For an investigator handling sensitive or legally protected material, that distinction matters: client-side processing preserves the integrity of the artefact, avoids exposing case data to a third party, and supports the compartmentalisation that operational security demands.

When each tool fits an investigation

Cryptographic hashing (MD5, SHA-1, SHA-256, SHA-512) is used to verify that a seized file has not changed and to match a sample against known-good or known-bad reference sets. Base64 and hex decoders unwrap obfuscated payloads, configuration strings, and email attachments. The CIDR calculator scopes a network range when you are mapping an organisation’s address space. The JWT decoder exposes the claims inside a session token during application analysis. The regex extractor — tuned for Indian identifiers such as Aadhaar, PAN, IFSC, and mobile numbers — pulls structured entities out of bulk text for identification or redaction, and the epoch converter aligns log timestamps when reconstructing a timeline.

A note on evidence handling

Record the hash values you generate directly in your case notes; a documented hash is the simplest way to prove later that an exhibit is unaltered. Because these tools never transmit data, they are well suited to work that must remain on a single controlled device. Where your findings may support an FIR or court submission, pair them with a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, which governs the admissibility of electronic evidence in India.

▸ RELATED READING
Password Security in 2026 →Email Header Analysis for Investigations →OSINT: Phone Number Investigation →