Welcome to my Cybersecurity blog where I share tutorials, projects, and insights from my experience and research.

Welcome, visitor!

Terminal

guest@timsonner.com:~
Welcome to timsonner.com Terminal v1.0.0
Type 'help' to see available commands.

guest@timsonner.com:~$
How it works

Browser-based recon terminal. Commands run entirely in your browser against public APIs and open data sources — nothing is shelled out on this server. Type help in the prompt for the live command list.

Commands

  • whois <domain> — RDAP lookup via rdap.org (registrar, status, NS, events).
  • dig <domain> [type] — DNS via Google Public DNS (A, AAAA, MX, TXT, NS, SOA, plus DMARC / DKIM helpers).
  • osint <ip|domain> — geo/ASN snapshot plus quick links (Shodan, Censys, VirusTotal, etc.).
  • subdomains <domain> — crt.sh certificate transparency search.
  • headers <url> — fetch response headers and flag framing / CSP-related values.
  • cve <id> — CVE details from the NVD API.
  • mac <address> — MAC OUI / vendor lookup (via public CORS proxies when needed).
  • subnet <cidr> — local subnet math (network, broadcast, range, hosts).
  • news — recent security headlines pulled through public feed proxies.
  • date / clear — clock and wipe the scrollback.

UX — ↑/↓ walk command history. Copy grabs the current output. Traffic lights: red clears and resets size, yellow minimizes, green maximizes / restores size.

Limits — third-party APIs rate-limit, change shape, and sometimes need a CORS proxy hop (news, mac). Results are only as fresh as those sources. This is a convenience shell for demos and quick checks, not a replacement for local dig / RDAP clients or authenticated intel platforms.

Email Parser

Email Parser

Upload a .eml file or paste raw email content to parse headers, body, and extract attachments. All processing is done locally in your browser.

How it works

Client-side MIME / header analyzer for phishing triage and mail forensics demos. Upload a .eml / .txt file or paste the raw message, then hit Parse Email. Nothing is uploaded — the file and paste buffer never leave this browser tab.

What you get

  • Email info — Subject, From, To, CC, Reply-To, Return-Path, Date, Message-ID, mailer/UA (RFC 2047 decoded).
  • Authentication results — Authentication-Results with pass/fail highlighting (SPF / DKIM / DMARC style tokens when present).
  • Message body — plain-text part, plus optional HTML preview in a locked-down sandbox="" iframe (no scripts).
  • Attachments — extracted parts with download buttons (base64 decoded locally).
  • Received chain — hop-by-hop Received headers for path review.
  • All headers — full collapsible dump of the header block.

Parser notes — walks multipart trees, honors Content-Type / Content-Disposition, and decodes quoted-printable, base64, and common charsets best-effort. Nested multiparts are flattened into text, HTML, and attachment buckets.

UX — red clears the form/results and resets size; yellow minimizes; green maximizes / restores size.

Limits — this is a lightweight browser parser, not a full MUA or enterprise mail gateway. Exotic MIME, S/MIME, or broken messages may parse incompletely. HTML preview is intentionally inert (empty sandbox) so active content cannot run. Always treat untrusted mail and attachments as hostile.

Proxy Browser

Proxy Browser
Ready — enter a URL above
Enter a URL above to begin
How it works

Mini browser for inspecting pages in-frame — phishing kits, clickjacking behavior, and framing headers — without opening a full trusted browser session. Everything runs client-side; there is no first-party proxy on this site.

Proxy Fetch (default) pulls the target HTML through public CORS proxies, then renders it in a sandboxed iframe via srcdoc. Available backends: cors.eu.org, proxy.cors.sh, allorigins.win, corsproxy.io, codetabs.com.

  • Auto (race) — tries all proxies in parallel; first valid HTML wins.
  • Pinned proxy — force one backend from the dropdown.
  • Cancel — abort an in-flight load.
  • Try next — after a failure, walk the remaining proxies sequentially.
  • Raw HTML — show the fetched source when the rendered view is broken.

On each successful fetch the tool injects a <base href> so relative assets resolve against the real origin, plus a nav interceptor that re-routes link clicks, image-map areas, GET form submits, meta-refresh, and simple location changes back through the proxy instead of breaking out of the frame.

Direct iframe sets iframe.src to the URL with no proxy. Use it to demo framing denial. A blank viewport usually means the target sends X-Frame-Options or CSP: frame-ancestors.

UX — traffic lights: red resets the session and size, yellow minimizes, green maximizes / restores size.

Limits — free public proxies rate-limit, time out, and get blocked by WAFs; a failure is often the proxy, not your URL. The sandbox has no real browser session: cookies/auth, many SPAs, and POST bodies will not behave like Chrome/Firefox. Subresources still load from the live origin via <base>. Prefer Raw HTML when you only need the markup.

Latest Posts