How RadioMap24 Builds the Catalogue

Bounded source build

The catalogue builder discovers Radio Browser mirrors, sends a descriptive RadioMap24 user agent with a public contact address, downloads bounded pages, validates the schema and rejects unsafe, non-HTTPS or ungeolocated browser streams. The current noindex staging snapshot publishes only records that pass those checks.

Static output

After normalization and suppression, staging serves the catalogue as a cached static asset. Listener requests do not query a RadioMap24 database, Worker or public API. A production refresh would be generated outside the visitor hot path and published only after the same validation succeeds.

Factual limits

RadioMap24 never hosts, records, transcodes, proxies or inserts audio advertising into a station stream. When a listener starts a station, the browser connects directly to that station or its stream host, which receives the listener's network request.

RadioMap24 relies on recent source checks rather than continuously probing every stream. A recent successful check is not an uptime or rights guarantee, and regional restrictions or removal requests can require a station to be disabled.