Edge IP Binding (EIPB) allows you to deliver traffic from a small, static set of IP addresses in an ​​Akamai​ scalable manner. It provides individual IPv4 addresses (/32s) and IPv6 /64 CIDRs. The assigned IPs are used exclusively to serve traffic for the hostnames configured for that set of addresses.

You can implement Edge IP Binding to accomplish the following:

• Support zero-rated billing. Add Edge IP Binding if you're looking to offer specific traffic at no cost to end users, or prevent specific delivery from counting against a data cap.

• Identify content provider traffic based on the source IP. This helps when you can't perform a deep packet inspection.

• Provide a single or a limited number of source IP addresses. This would help if your infrastructure systems are too complex and need a single, or very limited number of source IPs.

• Eliminate frequent updates to IP address ranges. This applies if your business support or operations support systems can't handle frequent updates.

• Provide simplicity and scale. This can help remove the need for additional domains or additional IPs.

Get started

• Understand how Edge IP Binding works
• Meet some prerequisites

Set up Edge IP Binding for HTTPS

• Add it to an Enhanced TLS property
• Add it to a Standard TLS property
• Add it to a Shared certificate hostname property

Get your Edge IP Binding addresses

• View the addresses in Property Manager
• View the addresses in the Edge IP Binding tool