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
- If a check page briefly shows IPv6 and then IPv4 on the same page while TUN is off and no setting changes, the cause remains unknown.
- Keep the test method, browser, Wi-Fi, and proxy mode consistent while repeating the check and reading system network and proxy state.
- Separate a field returned by a test page from an explicit curl proxy request and a real browser visit; they may follow different paths.
- Do not change Wi-Fi IPv6, reset networking, or claim a confirmed leak from one field. Do not paste the test page's public address into a ticket.
One IPv6 field does not confirm a leak
If TUN is off in macOS v2rayN and one IP-check page briefly shows IPv6 before the same page later shows IPv4, the first result alone does not prove that real web traffic bypassed the proxy. A page may display a field observed on one request; it does not necessarily describe every app, connection, or later page request.
If IPv4 is expected, Wi-Fi shows IPv6 disabled, and a later check on the same page shows IPv4 without a setting change, the transient field and its cause are still unconfirmed. Keep the conclusion at “temporary check anomaly, cause unknown,” not “no leak” or “leak confirmed.”
Repeat the observation under fixed conditions
Keep the same Mac, Wi-Fi network, browser, test page, and proxy path. Do not switch browser, network, and proxy mode at once and compare the new result directly with the earlier page. Record whether the page loads, whether the field appears again, and when it clears. Do not copy or publish the actual public address shown by the test page.
A page refresh, DNS change, site-side logic, or connection selection could affect a single observation, but the evidence does not identify which occurred. Do not infer that every device connection used IPv6 from one temporary result, and do not treat node latency or a system switch as proof of the real egress path.
Read the system network and proxy settings
Check IPv6 state and HTTP, HTTPS, and SOCKS system proxy settings for the active network service. Wi-Fi is common, but replace the name if the Mac uses Ethernet, a VPN, or a custom service. The commands only read settings, but may show the local IP, router, or proxy port; remove those details before saving or sharing output.
This guide applies to the TUN-off branch. If TUN is enabled, curl, browser, and system proxy requests may be captured by TUN. Identify the active topology before deciding which path a request actually followed.
Read Wi-Fi IPv6 and system proxy settings
shellnetworksetup -getinfo "Wi-Fi"
networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi"
networksetup -getsocksfirewallproxy "Wi-Fi"
Verify explicit proxy requests separately from browser traffic
If you know the local HTTP proxy port, use curl with an explicit proxy to request the same check page and record only whether the request succeeded and its HTTP status. The command does not print the page body containing the IP. Then open the same page in the browser and see whether its field is stable. The explicit request checks the local entry selected by curl; it does not prove that Safari or another app uses the same proxy setting.
If the explicit request and browser result differ, check whether the browser follows the system proxy, whether the active network service is correct, and whether TUN is off. Do not write “curl works” as proof that browser traffic is proxied, and do not equate a diagnostic page with a real business-site request.
Request the check page through a selected local HTTP proxy
shellHTTP_PORT='REPLACE_WITH_CURRENT_HTTP_PORT'
curl --silent --show-error --max-time 15 --proxy "http://127.0.0.1:${HTTP_PORT}" --output /dev/null --write-out 'HTTP %{http_code}\n' https://ping0.cc/
Check the egress path if the result repeats
If the same IPv6 field appears repeatedly under identical conditions, confirm which page field is shown, which request path was used, and whether the system actually allows IPv6 on that path. When comparing a second independent test page or a controlled business site, keep the browser, network, and proxy mode unchanged. Different sites can test different connections, so a disagreement does not automatically establish which result is correct.
If system settings clearly show Wi-Fi IPv6 disabled but the explicit proxy request and real browser visit repeatedly show the anomaly, collect only the time, field category, and path needed to continue checking the local proxy and browser. Do not publish the actual address or access identifiers.
Avoid changing system settings for one fluctuation
Do not enable or disable Wi-Fi IPv6, reset network settings, flush DNS, or switch proxy modes based on one temporary field. Such changes alter network behavior for the device or system services and make the original state harder to reproduce. Consider one narrowly scoped, reversible setting change only after the same anomaly repeats and is tied to the request path in question.
If a temporary result disappears without a settings change, the reason remains unknown. That does not prove system settings are irrelevant or that a particular change works. Check whether the diagnostic result changed separately from whether real application access succeeded, and avoid drawing a leak conclusion from a single page.
Sources
Frequently Asked Questions
Does IPv6 on one brief test-page result mean the proxy leaked?
Not by itself. Repeat the check with the same browser, network, and proxy path, and confirm which connection the real request used.
Does Wi-Fi showing IPv6 off prove all proxy traffic uses IPv4?
No. System proxy, explicit proxy, TUN, and app-specific requests may use different paths.
Should I reset networking or change IPv6 first?
No. The available observation cleared without a settings change, and the cause is unknown. Record and repeat the test first.
Can I send the address shown on the check page to support?
Do not publish a real public IP or a full page result. Share only the redacted protocol field, time, and request path.