JDOOM
Unlock ports.
Let the browser speak non-Web protocols.
If it's a web page, render it. If it's a service, identify it.
Replace a dozen protocol clients and dark terminals — one browser handles every port.
Why JDOOM?
Four problems that every network engineer faces -- solved in one browser.
Too Many Protocol Clients
SSH→PuTTY, Telnet→SecureCRT, RDP→Remote Desktop, SQL→SSMS — a different tool for every port.
Dark Command-Line Terminals
Telnet/SSH shows IAC garbage, non-printable chars are unreadable — dark terminals are useless for real work.
Port Probing Requires nmap
Need to open a terminal and type commands to identify services — why not just type the address in a browser?
Extensions Can't Install Offline
Air-gapped/isolated networks can’t reach Chrome Web Store — extensions must ship with the browser.
A complete browser first — standard web renders natively
The real production site https://jiwo.org rendered natively in-kernel: tables, colors, images and CJK typography all correct; full HTML5/CSS3/JavaScript support. Only on top of this baseline does the three-stage probe below handle non-web ports.
Three-Stage Probe, light-to-heavy, stop on first match
Three progressive checks on every target port -- each stage can independently return a verdict; never oversteps.
Read Active Banners
SSH/FTP/SMTP/Telnet self-identify on connect. JDOOM reads the banner and stops — zero interference.
passiveTry HTTP
Web pages render normally; non-HTTP responses terminate early — no side effects.
standardService Fingerprinting
Minimal handshake packets identify RDP/SQL/SMB/RPC/SSL — only for non-web ports.
active
Real Probe Screenshot
Visiting 192.168.0.97:3389, JDOOM determines it is not a web port and automatically runs service identification:
RDP (X.224) responded · SSL/TLS responded
Similarly, :445 → SMB, 127.0.0.1:8080 → HTTP renders the real page.
Protocol Matrix
The same core logic turns "unreachable error pages" into "readable answers."
Banner hit -- finished in 4 ms, zero disturbance
Real website -- rendered like a normal browser
Protocol Recognition Matrix
| Protocol | Port | Method |
|---|---|---|
| SSH / FTP / SMTP | 22 / 21 / 25 | Banner Read |
| Telnet | 23 / any | Banner Read |
| RDP Remote Desktop | 3389 | X.224 handshake |
| SQL Server (TDS) | 1433 | Prelogin |
| SMB File Sharing | 445 / 139 | SMB1+SMB2 |
| SunRPC / Portmap | 135 / 111 | GETPORT |
| SSL/TLS (Implicit) | 465/993/995/636 | ClientHello |
| HTTP / HTTPS | 80 / 443 / 8080 | Render |
Interactive Telnet + 6 Extensions
chrome://jdoom-telnet — Built-in Telnet client on net::TCPClientSocket, automatic IAC stripping.
Live Connection Tests
202.5.197.3:23
ZTE ZXR10 router login banner
202.72.240.65:23
User Access Verification
• Jump to any port from the probe page in one click
• URL parameters ?host=&port= for auto-connect
• IAC WILL/WONT/DO/DONT auto-negotiation
• Basic ANSI color support
6 Built-in Extensions
Target Users
Built for professionals who work with networks, servers, and infrastructure every day.
Asset inventory, port auditing, and service fingerprinting -- all from a single browser window.
Quick Telnet checks, header inspection, and DNS lookups without leaving the browser.
Debug non-HTTP services, inspect raw banners, and test connectivity on any port.
Specifications
| Item | Detail |
|---|---|
| Browser Engine | Chromium 153 |
| Probe Mechanism | NavigationThrottle |
| Built-in Terminal | Telnet terminal |
| Extensions | 6 extensions (SwitchyOmega, Cookie-Editor, Header Modifier, JS Toggle, Charset, Markdown Viewer) |
| Google Services | Blocked |
| Platform | Win10/11 |
| Delivery | Installer / Source Patch |
| Version | 1.1.0 |
JDOOM 1.1.0 · Now Available
Unlock ports. Let the browser speak non-Web protocols.
Try Nowjiwo.org · Version 1.1.0