ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

SNI

TLS Server Name Indication extension, routing for multi-tenant EDI hosts.

Definition

SNI adds a server_name extension to the ClientHello carrying the requested DNS hostname. The server uses it to select which X.509 certificate and TLS configuration to present when several AS2/AS4/REST endpoints share one IP address. SNI travels in cleartext (before the handshake is encrypted) and must match exactly the CN/SAN of the certificate the partner expects.

Origin

Defined in RFC 6066 (IETF, 2011), "TLS Extensions: Extension Definitions", which carries forward the server_name extension first introduced by RFC 3546 (2003).

Example in context

An EDI partner whose AS2 endpoint is multi-tenant sees the handshake fail if its client omits the SNI <server_name>edi.partner.com</server_name>: the server then returns a default certificate with the wrong CN.

  • X.509 — format of the certificate selected via SNI.
  • TLS 1.3 — version where SNI is still sent in cleartext by default.

Last updated: June 20, 2026