IP Detective
3000
Five small tools for poking at email headers, images, PDFs, and file hashes. They all run in your browser, so nothing about what you put in reaches the server.
Choose a Tool
5 tools · 5 activeEmail Header Analyzer
01 / 05Paste a raw email header. The parser walks the Received chain to show every relay hop, finds the origin IP, and reports SPF, DKIM, and DMARC results. Nothing is sent to the server.
- ─ SPF, DKIM, DMARC results
- ─ Relay chain timeline with IPs
- ─ First public IP in the chain
Metadata Viewer
02 / 05Drop a JPEG, PNG, WebP, TIFF, or HEIC (iPhone) to inspect every EXIF tag it carries: camera and lens, capture settings, image properties, and GPS with an OpenStreetMap link. Read-only sibling of the EXIF Scrubber.
- ─ JPEG, PNG, WebP, TIFF, HEIC
- ─ GPS map link if coordinates exist
- ─ Live filter across all tags
PDF Metadata Viewer
03 / 05Drop a PDF to see its Info dictionary (Title, Author, Creator, Producer, dates), XMP packet, page count, version, linearization, and encryption status. Nothing is sent to a server.
- ─ Info dict + XMP packet
- ─ Pages, version, encryption
- ─ Live filter across fields
EXIF Scrubber
04 / 05Drop a JPEG to see the metadata it carries (GPS coordinates, camera info, timestamps). One click strips it and gives back a clean copy. The image is read and rewritten in your browser.
- ─ GPS, camera, and EXIF tags
- ─ One-click scrub and download
- ─ JPEG only for now
File Hash Generator
05 / 05Drop a file and get its SHA-256, SHA-1, and SHA-512. Useful for verifying a download against the publisher's hash, or noticing if a file changed. Web Crypto handles the math, no upload.
- ─ SHA-256, SHA-1, SHA-512
- ─ Paste a known hash to verify
- ─ Browser-native Web Crypto API
How it works
In your browser
Each tool is a static page with some JavaScript. When you paste a header or drop a file, the JavaScript reads it directly and never sends it anywhere.
Ships static files
The server hands out HTML, CSS, JavaScript, and fonts. It has no endpoints that accept your data, so there's nothing on our side that could leak it.
No ads, no trackers
The pages load nothing from third parties. No ad networks, no analytics scripts, no fingerprinting libraries. The Content Security Policy enforces this in the browser, so even an accidental third-party include would be refused before it ran.