No results found. Ask us directly:

Are ScorePlay SRT ingest endpoints AES-256 encrypted?

Last updated: July 26th 2026 · Status: Validated · Article ID: 3897480

💻 Environment/Context

  • Live ingest
  • SRT endpoint
  • Encryption
  • AES-256

 

❓ Issue/Question

  • The satellite agency are asking me if the SRT endpoints are "aes256 encrypted".

 

👌 Resolution/Answer

  • ScorePlay's SRT ingest endpoints support AES-256 encryption in transit. The stream is encrypted using a pre-shared passphrase (the passphrase on the endpoint is what enables AES encryption).

 

  • Important detail about how SRT encryption works: the AES key length is set by the sending encoder, and ScorePlay's ingest adopts whatever the encoder negotiates. For the stream to be AES-256 end to end, the customer's encoder must be configured with a 256-bit key length — pbkeylen=32 (32 bytes).

 

 

 

🔖 Notes 

  • With pbkeylen=32 set on the encoder side, the SRT stream is AES-256 encrypted in transit from encoder to ScorePlay ingest.
  • SRT encryption strength depends on the encoder's key-length setting rather than being fixed by the endpoint, which is why the answer hinges on the sender's pbkeylen value.