请选择
Edge Acceleration
  • Site Acceleration
    • Overview
    • Access Control
      • Token Authentication
    • File Optimization
      • Smart Compression
    • Network Optimization
      • HTTP/2
      • HTTP/3(QUIC)
        • Overview
        • Enable HTTP/3
        • QUIC SDK
          • SDK Overview
          • SDK Download and Integration
          • Sample Code
            • Android
            • iOS
          • API Documentation
            • Android
            • iOS
      • IPv6 Access
      • Maximum Upload Size
      • WebSocket
      • Client IP Geolocation Header
      • Client IP Geographical Location
      • gRPC
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Custom Error Page
    • Request and Response Actions
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
  • Smart Acceleration
  • L4 Proxy
    • Overview
    • Creating an L4 Proxy Instance
    • Modifying an L4 Proxy Instance
    • Disabling or Deleting an L4 Proxy Instance
    • Batch Configuring Forwarding Rules
    • Obtaining Real Client IPs
      • Obtaining Real TCP Client IPs via TOA
      • Obtaining Real Client IPs Through Protocol V1/V2
        • Overview
        • Method 1: Obtaining Real Client IPs Through Nginx
        • Method 2: Parsing Real Client IPs on Application Server
        • Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
      • Transmitting Client Real IP via SPP Protocol
  • Edge DNS
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Advanced DNS Configuration
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
    • Domain alias
      • Overview
      • Configuration Guide
      • Batch Connecting SaaS Domain Names
      • Configuring Alias Domain Names for Disaster Recovery
    • Traffic Scheduling
      • Traffic Scheduling Management
    • Origin Configuration
      • Load Balancing
        • Overview
        • Quickly Create Load Balancers
        • Health Check Policies
        • Viewing the Health Status of Origin Server
        • Related References
          • Load Balancing-Related Concepts
          • Introduction to Request Retry Strategy
      • Origin Group Configuration
      • Origin-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Related References
        • ld Version Origin Group Compatible Related Issues
        • VOD Origin Server Details
      • Collect EdgeOne origin-pull node IP
  • Edge Cache
    • Overview
    • EdgeOne Cache Rules
      • Content Cache Rules
      • Cache Key Introduction
      • Vary Feature
    • Cache Configuration
      • Custom Cache Key
      • Node Cache TTL
      • Status Code Cache TTL
      • Browser Cache TTL
      • Offline Caching
      • Cache Prefresh
    • Clear and Preheat Cach
      • Cache Purge
      • URL Pre-Warming
    • How to improve the Cache Hit Rate of EdgeOne
  • Rules Engine
    • Overview
    • Supported Matching Types and Actions
    • Rule Management
    • variables
  • Image Processing
Docs Overview/
Edge Acceleration/
Edge DNS/
Origin Configuration/
Collect EdgeOne origin-pull node IP/

Collect EdgeOne origin-pull node IP

To obtain the EdgeOne's IPs for requesting origin, which can be used to set these EdgeOne's IPs as an allowlist in the origin firewall, only allowing fixed source (IP) requests to the origin, thus implementing protection for the origin.

Use Guide

1. Directly access https://api.edgeone.ai/ips through a browser or curl command. This will collect all IPv4 and IPv6 origin-pull node IP addresses of EdgeOne in the Global availability zone. The responded result is UTF-8 encoded plain text, with one IP segment per line.
2. If you only need to obtain the origin-pull node IP of a specified region or a specified IP Type, you can also filter the origin-pull node IP by carrying a specified query string. The supported query strings are as follows:
Query string
Explanation
version
Specifies the Type of origin-pull node IP address to be collected, with the following values:
v4: All IPv4 origin-pull node IP addresses
v6: All IPv6 origin-pull node IP addresses
By default, all IPv4 and IPv6 IP addresses are returned when this parameter is not included.
area
Specifies the region of the origin-pull node IP to be collected, with the following values:
global: All origin-pull node IP addresses in the Global availability zone
mainland-china: All origin-pull node IP addresses in the Chinese mainland availability zone
overseas: All origin-pull node IP addresses in the Global availability zone (excluding Chinese mainland)
By default, all origin-pull node IP addresses in the Global availability zone are returned when this parameter is not included.
Note：
1. In general, it is suggested to select and obtain the origin-pull node IP address of the corresponding region based on your site's service area. For example, if the site's service area is in the Chinese mainland availability zone, you can obtain the origin-pull node IP address within the Chinese mainland availability zone, and the same applies to other service areas.
2. This function is mutually exclusive with the origin protection function. If you need to collect the latest origin-pull IP through the method in this Document, please confirm that you have turned the business origin protection function Off.

Request example

If you want to obtain all IPv6 origin-pull node IPs in the Global availability zone (excluding Chinese mainland), you can query the origin-pull IP address under this condition by carrying version=v6&area=overseas in the request URL. The specific URL is: https://api.edgeone.ai/ips?version=v6&area=overseas

The response result example is as follows (this result is for reference only, please refer to the real-time request result for the actual origin-pull IP):
240d:c010::/28
2001:ee0:324b:100::/64
2405:3200:101:63::/64
2405:4800:a601::/64
2602:ffe4:c02:1001::/64
2602:ffe4:c12:101::/64
2602:ffe4:c12:105::/64
2602:ffe4:c15:124::/64
2602:ffe4:c18:c003::/64
2602:ffe4:c18:c201::/64
2602:ffe4:c18:c203::/64
2602:ffe4:c27:1003::/64
2604:980:4002:2::/64
2604:980:5003:2::/64
2604:980:7002:6::/64
2a02:b60:2001::/64