Contacts
| Abuse | abuse@irdm.io — response within one business day |
|---|---|
| Operations | ops@irdm.io — incidents, peering, capacity |
| Security | security@irdm.io — see security.txt |
| Postal | IRDM Networks, P.O. Box 1149, 1800 BC Alkmaar, Netherlands |
Acceptable use
- The relay forwards sessions between authenticated participants of our own rooms. It is not an open proxy and it does not sell transit.
- No peer-to-peer file distribution, no scanning, no outbound abuse, no spoofed source addresses.
Ports other than
TCP/443,UDP/443and the SSH administration port are firewalled on the host. - Participants must be identified by a per-session credential. An unknown credential receives the public website you are reading now — there is no other response.
- We answer suspension requests only from the hosting provider or from a competent authority with a lawful order, and we challenge requests that would require breaking end-to-end encryption.
Data handling
| What is kept | Per-minute aggregated counters: bytes, packet counts, active sessions, peer subnet (not individual addresses) |
|---|---|
| Retention | 7 days for capacity planning, then discarded |
| What is not kept | Session content, media, message payloads, browsing targets of participants, DNS queries |
| Encryption | TLS 1.3 / DTLS 1.2 end to end between participants; the relay forwards packets it cannot decrypt |
| Cookies | None. This site sets no cookies and loads no third-party resources |
Operational note for network operators: traffic from 5.255.102.41 toward
your users is expected to be sustained encrypted UDP/443. If you need this confirmed for a specific
time window, write to abuse@irdm.io with timestamps.
Imprint
This node is operated as a private research and testing deployment for real-time media transport research. The site is static and informational; there is no user account system, no shop and no advertising on it.