shredstream.sh endpoint reference
Find every documented web, checkout, verification, and live-delivery endpoint together with its protocol and known port behavior.
Endpoint inventory
shredstream.sh is a pushed raw-UDP service. A customer does not open a persistent connection to a provider stream endpoint. The customer exposes a destination, verifies control of it, and receives datagrams from the documented sender.
UDP delivery contract
Each live datagram contains exactly one raw shred. No framing connection is added, and the service neither restores arrival order nor resends gaps nor slows for a lagging receiver.
Verification endpoint behavior
Verification targets the customer's registered IPv4 value and configured UDP socket. Its validity window lasts 600 seconds; the first line equals SHREDCAST-VERIFY. Address 203.23.178.228 sources both verification and live traffic.
The remainder of the challenge wire format, resend pacing, maximum resend count, source UDP port, and delay from accepted verification to first live packet are not currently specified.
Live receive endpoint behavior
Bind the configured destination port before verification, then keep it open for streaming. Admit source 203.23.178.228 under UDP policy. Each receive slot needs capacity for 1,228 bytes; parse the returned datagram length instead of assuming fixed-size packets.
Documented product facts name no TCP, gRPC, or WebSocket delivery endpoint. The raw UDP contract likewise supplies no receiver URL, hostname, multicast group, session identifier, ordered stream number, or reconnect operation.
Web endpoints
The public site is https://shredstream.sh and checkout is https://checkout.shredstream.sh. Their URL schemes establish HTTPS. Product documentation supplies no nonstandard network port, site allowlist, public API base URL, API version, or machine-authentication contract.
Do not derive an integration endpoint from internal application paths. Only documented public contracts belong in receiver configuration.
Questions
- What host does a receiver connect to for the live stream?
- No documented provider host accepts a receiver connection. Source 203.23.178.228 pushes UDP toward the customer-configured IPv4 destination and port. The receiver binds that local socket, permits the fixed sender, completes verification, and then accepts raw datagrams.
- Which UDP port does shredstream.sh use?
- Customers configure the destination UDP port. Its allowed numeric range and the service's sender port are absent from the product facts. In firewall policy, require source 203.23.178.228 alongside UDP transport and the configured destination, without constraining sender port.
- Does the service provide gRPC or WebSocket delivery?
- No gRPC, WebSocket, or TCP delivery endpoint is stated in the product facts. Arrival sequence, gap repair, and receiver flow control are absent from the raw UDP wire. Customers that require decoded records, server-side filtering, or a reliable stream need a separate processing layer or a different product category.