The Proxy Protection tab (AMD)
These reports show how Akamai's Enhanced Proxy Detection (EPD) service has applied proxy detection and location spoofing protection when delivering your Adaptive Media Delivery (AMD) content.
EPD uses services provided by our data provider, GeoComply to identify requests for your content that have been redirected from an unwanted source via a proxy. You can then allow, deny, or redirect these requests.
There are fixed categories of proxy detection
Akamai leverages GeoComply's GeoGuard product for proxy detection. GeoGuard offers multiple categories to identify various types of unwanted proxy that may be used in a request. A list of these categories is kept on GeoComply's website.
- Best Practices. This is the mode Akamai recommends. It automatically uses all of GeoGuard's primary ("must have") categories and you set a single action to apply for all of them—"Set it, and forget it.
- Advanced. This lets you pick and choose from all of the "primary" and "optional" categories and you can customize individual actions for each.
Remember how you've set your Configuration Mode when reviewing report data here. It impacts how data is revealed—whether it is, or isn't displayed in some cases.
Set up a filter
Use the Filters panel to customize your report. You can set these options:
- Date Range (Required). Click this field and determine a range of dates you want for report data. See Set the date/time range for a report for more information. You can gather data from the last 90 days.
- CP Code (Required). A content provider (CP) code is a unique identifier we assign to you for reporting, billing, and monitoring traffic served over the Akamai network. Someone in your organization assigns a friendly name to a CP code when it's created—either via a tool in Akamai Control Center or an API, or with the help of your Akamai account representative. Click each desired CP code to include in the filter or, if you know the name or number of the desired CP code, type it in the Filter field to refine the results. You can also click All to include every CP code.
- Delivery Option. Select the traffic security level—HTTP for non-secure traffic, or HTTPS for forms of secure traffic—those that use an Enhanced TLS Edge certificate, the Akamai shared certificate, or a Standard TLS Edge certificate.
- Delivery Format. If you want to filter the results to a specific media format, select it here. The "Others" selection here applies to all other media formats not listed for selection.
- IP Version. Select the applicable IP version for traffic—IPV4, IPV6, or All for both.
- Delivery Type. Select from On Demand, Live, or All for both. ("All" is the default.)
Each individual content panel in the reporting tabs is referred to as a "widget." Several widgets make up your report in this tab.
|Total Request, Matches and Actions Trend||This widget shows overall EPD matches for requests
from identified proxies and the number of actions taken. There are a
few data points in this widget:
|Total Requests, Matches Applied Actions Taken By CP Code||This widget shows EPD matches for requests from identified proxies and the number of actions taken, per individual content provider code (CP code). The data points are the same as the Total Request, Matches and Actions Trend widget.|
|Matches Applied and Actions Taken Percentage By CP Code||This takes the total number of edge proxy hits for
each CP code and reveals:
|Match Category Trend||This shows the frequency of requests from each of
the various GeoGuard categories of proxy detection, over the
specified range of time. It applies to all requests, across all CP
Note: While the widget shows all GeoGuard categories in its key, the data shown depends on what you've selected for your EPD Configuration Mode. See There are fixed categories of proxy detection, above.
|Match Category By CP Code||This widget shows all of the GeoGuard categories of proxy detection ("Applied Matches") for a specific CP code, in relation to the full total of Edge Proxy Hits for that CP Code.|
|Match Category Summary||This widget shows the total of Applied Matches over the selected range of time. It offers a cross reference view of the various GeoGuard categories of proxy detection against each other, as well as against the number of hits that came from all proxies.|
|Actions Taken Trend||This shows the frequency of allow, deny, and
redirect actions taken, over the specified range of time. It applies
to all requests, across all CP codes.
Note: While the widget shows all action types in its key, the data shown depends on how you've configured your actions for the EPD Configuration Mode you've selected. See There are fixed categories of proxy detection, above.
|Actions Taken By CP Code||This widget shows totals for each deny ("Blocked Hits"), redirect ("Redirect Hits"), or allow ("Akamai Override") action taken for a specific CP code, in relation to the full total of Edge Proxy Hits for that CP Code.|
|Actions Taken Summary||This widget shows totals of Actions Taken over the selected range of time. It offers a cross reference view of the various actions against each other, as well as against the number of hits that came from all proxies.|
Toggle between Table and Chart view
Click the table icon () or the chart icon () to switch between these views in a widget.
Aggregation of data is affected by Chart view
If a widget offers a Chart view that displays a line graph, there is a limit on the number of data points that can be plotted. This limit affects the aggregation of data revealed, based on the range of time you specify. See Widget data aggregation and Chart view for more information.
Click the magnifying glass icon () to customize the kind of data that is shown in the widget. See Analyze data shown in a report for more information.