To align with industry best practices and enhance security, we’re ending support for Transport Layer Security (TLS) versions 1.0 and 1.1 on Tuesday, September 23, 2025.

This update might affect systems or legacy scripts that connect to the DV+ platform using these older TLS versions. Specifically, this could affect any DV+ API gateway integrations you have with Magnite, especially with legacy scripts that might connect to our services.

To avoid disruptions, we recommend updating your integrations to a supported version like TLS 1.2 or higher.

Reach out to your Magnite representative if you have any questions or need assistance with any technical adjustments.

Get more details about the update

Older TLS protocols have known vulnerabilities that can pose risks, including the following:

• Heartbleed
• BLUFFS attack
• Padding oracle attack (POODLE)
• DROWN attack

To protect data integrity and confidentiality, modern security standards recommend TLS 1.2 or higher.

Find out which APIs are affected

The deprecation affects the following Magnite APIs:

• Performance analytics
• Inventory management
• Segment management
• Prebid analytics

Integrations relying on TLS 1.0 or 1.1 will no longer be supported.

Align with compliance and industry standards

This update aligns Magnite with key compliance frameworks, including:

• SOC 2 CC 6.1: Requires logical access security controls to protect information assets.
• PCI DSS 4.0.1: Requires the use of strong cryptography, which excludes TLS versions 1.0 and 1.1. Learn more about PCI DSS requirements. (*Magnite is not subject to PCI compliance requirements, but many customers and partners may be.)

Prepare for the update

We recommend updating any systems or scripts to use TLS 1.2 or higher. To verify your current TLS usage, use the code below:

Open SSL

• TLS 1.0: openssl s_client -connect <domain>:443 -tls1
• TLS 1.1: openssl s_client -connect <domain>:443 -tls1_1
• TLS 1.2: openssl s_client -connect <domain>:443 -tls1_2
• TLS 1.3: openssl s_client -connect <domain>:443 -tls1_3

cURL

• TLS 1.0: curl -v --tls-max 1.0 --url "https://<url>"
• TLS 1.1: curl -v --tls-max 1.1 --url "https://<url>"
• TLS 1.2: curl -v --tls-max 1.2 --url "https://<url>"
• TLS 1.3: curl -v --tls-max 1.3 --url "https://<url>"

For more detailed TLS inspection, use tools like the Wireshark TLS handshake guide.

Additional resources

• Microsoft TLS 1.0 and 1.1 deprecation in Windows
• IETF RFC8996: Deprecating TLS 1.0 and 1.1
• Example industry notice