nothing leaves this tab
Somewhere on your network, 254 doors are waiting to be knocked on.
Degram finds your local IP, works out your subnet, then knocks on every address in it to see who's home. It checks a handful of common ports and reads back whatever your device is willing to hand over unasked. This is the exact groundwork a script on any tab you have open could already be doing.
how it finds you
An RTCPeerConnection gets opened just long enough
to leak your local IP through its ICE candidates. From there
Degram guesses your /24 and fires a timed request
at every address in it, watching which ones answer and how fast.
what it asks of you
One click, nothing else. No login, no extension, no camera or microphone. Every check here runs on APIs your browser already exposes to any page you open.
every address on your /24, one square each, .1 through .254
What answered back
local ip
subnet swept
hosts up
connection
.local hostname before handing anything over. That's mDNS obfuscation doing exactly what it's supposed to, and it's why some fields above came back thin.
This device, read cold by a stranger
None of this needed a click, a permission prompt, or you knowing it happened.
Ports checked nearby
Timing only, nothing confirmed directly. A fast failure usually means closed; a slow one usually means filtered.
Refresh this page and every result above resets to zero. That's not a safety net, it's the actual problem: any tab could run this same sweep once, quietly, and be gone before you'd think to check.