PuppyIP Resource Center
Network & Connection Troubleshooting 8 min Published 2026-11-17

Shadowsocks Ingress ASN vs Proxy Egress IP: How to Verify the Actual Exit

An entry address's ASN can help identify where the client connects. Verify the actual proxy exit separately from a request observed by the destination.

Shadowsocks Xray Ingress ASN Egress IP Proxy path TCP

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The ingress IP is the target the client connects to; the egress IP is the source address the destination sees. They may belong to different networks.
  • ASN and geolocation databases report registered or inferred information, not the hidden intermediate route, private circuit or physical path.
  • To verify an egress for one request, send real TCP/HTTPS traffic from an authorized client and read the source at a controlled destination.
  • Record ingress, egress and intermediate transport separately. Without evidence from both ends, do not claim an IEPL, carrier or complete path.

Separate the entry address, exit address and intermediate transport

A proxy ingress is the server or relay address a client connects to. The proxy egress is the source address seen by the destination website or service. With a multi-hop proxy, the entry and exit can also be in different countries, regions or ASNs. Looking up the ingress IP alone cannot tell you where a destination request finally leaves.

An ASN lookup, IP geolocation database and node name provide limited registry or inferred information. They cannot by themselves prove that traffic uses a specific IEPL, carrier path, private peering link or physical server. Describe a route by stating what was actually observed at each end, define the protocol scope and mark invisible intermediate segments as unverified.

Record what is directly observable at the ingress

Check the Shadowsocks address, port, cipher and local/remote DNS setting in the client. Do not publish the password or a complete share link. A connection test can show whether the client established TCP to the ingress; the ingress ASN only describes the address's network registration and cannot replace an egress check.

To confirm that the client reached the intended ingress, compare a redacted node record from the authorized control panel or server operator and record the test time and resolved entry address. If the address changes, check DNS, load balancing and IPv4/IPv6 selection first; do not assume the provider changed the route.

Verify the destination-side egress with a real proxied request

Choose a test endpoint you are authorized to use that can show the request's source address, or use a server you control. From the client, send one HTTPS request explicitly through the Shadowsocks proxy and record the source address and time in the destination log. If the client requires a username and password, do not place them in command history, screenshots or public reports; use a protected credential-entry method.

Confirm that the request actually used the proxy instead of a system-direct route. Client DNS may resolve locally or remotely; a SOCKS5 remote-domain form depends on client support. Match the endpoint response, destination log and client connection state. A country label or one IP lookup describes only that service's result for that request, not every app, protocol or destination.

Request your own test endpoint through an authorized SOCKS5 entry

sh
PROXY_HOST="REPLACE_WITH_AUTHORIZED_SOCKS5_PROXY_HOST"
PROXY_PORT="REPLACE_WITH_CONFIRMED_SOCKS5_PORT"
TEST_URL="https://REPLACE_WITH_AUTHORIZED_EGRESS_CHECK_ENDPOINT/"
curl --proxy "socks5h://$PROXY_HOST:$PROXY_PORT" --connect-timeout 5 --max-time 15 -sS "$TEST_URL"
Replace these values with an authorized SOCKS5 proxy entry and a test endpoint that reports egress ASN/IP. This checks explicit proxy egress only, not transparent routing. Keep returned addresses and ASN local; do not publish them.

Check TCP, HTTPS and visible next hops separately

For a TCP service, record the source seen by the destination and whether the application responded. For HTTPS, also validate the certificate, SNI and completed request. ICMP traceroute or other path tools can be filtered, deprioritized or show only part of a route; they cannot confirm the proxy egress or full physical path. Reviewing intermediate networks requires authorized captures at both ends, carrier route information or verifiable network measurements.

If the same ingress appears to have different exits for different destinations or at different times, first check for multiple egresses, load balancing, IPv4/IPv6 selection or different DNS answers. Record the client, target protocol, ingress identifier, destination-observed source and time for each test. Do not extend one TCP/HTTPS result to UDP, game traffic or other user sessions.

Write path conclusions in a reproducible way

Separate reports into ingress, egress and intermediate path. For ingress, record the client's target and any registry lookup. For egress, record the source observed by the controlled destination. Include only intermediate segments confirmed by two-sided evidence. Redact actual addresses, ports, orders and account identifiers before sharing.

If you have only an ingress ASN and client-side connectivity, you can say only that the ingress was reachable and its registration lookup returned a given result. Without destination logs, egress remains unverified. Without route evidence, do not claim a dedicated circuit, a specific country transit or a fixed physical route.

Scope and stop conditions

This method checks one client, one proxy profile, one destination and one point in time. Shadowsocks or Xray configuration, DNS location, multi-hop rules and server egress can vary by device and release; the protocol name or entry region alone does not promise a particular exit.

If you lack authorized proxy credentials, destination permission or destination logs, stop with the evidence boundary stated clearly. Do not access someone else's system to determine request origin. An ASN lookup, speed-test page, node label or TCP handshake is not a route audit. To prove a private circuit or intermediate hop, request verifiable evidence from the relevant network operator.

Sources

Frequently Asked Questions

Can the ingress ASN prove which country the proxy exits from?

No. The entry address and the source seen by the destination are different observation points. Verify the exit with a real proxied request and destination-side data.

Can IP geolocation prove traffic uses IEPL?

No. IP registration or geolocation does not reveal a complete physical path or circuit type. That requires operator documentation or authorized end-to-end evidence.

Do traceroute hops show the complete proxy route?

No. ICMP may be filtered and a trace may show only part of the network. It cannot by itself prove proxy egress or hidden intermediate links.

Does an egress test need my real username and password?

Enter required credentials only in an authorized environment using a protected method. Do not post a full URI, password, order or subscription details in public tickets.