How to Detect iCloud Private Relay in Action
Introduction
Apple introduced iCloud Private Relay in 2021 alongside iOS 15 and macOS Monterey, and it has quietly grown into one of the largest privacy deployments on the internet. Any Safari user with an iCloud+ subscription can switch it on, and the moment they do, the sites they visit stop seeing their real IP address. Requests arrive from shared relay exit points that Apple and its partners operate.
For the user, that is excellent. For you, it is complicated. If you localize prices, enforce content licenses, score signups for fraud, or simply try to understand where your visitors come from, a slice of your Apple traffic now shows up wearing someone else's address. And it is a real slice, not a rounding error:
When researchers from the University of Trieste, the University of Turin, Cal Poly, and ENS de Lyon studied the relay on mobile networks, a European internet provider they consulted reported that iCloud Private Relay already accounted for 0.25% of its total traffic volume, and that roughly 10% of its household subscriptions exchanged more than 10 MB per day with relay ingress servers. Apple has not published adoption figures of its own. Source: iCloud Private Relay on Mobile Networks: Performance Across Countries and Roaming, ERN 2026
In this article you will learn what the relay actually does to your traffic data, why it quietly breaks so many IP based decisions, and how to detect it in production with a single lookup, so you can treat those users fairly instead of guessing.
What iCloud Private Relay Actually Does
Private Relay is a two hop proxy built into Safari and iCloud+. When a user enables it, Safari sends web traffic through two separate proxies in sequence:
- An ingress proxy operated by Apple, reached over an encrypted QUIC connection, which knows the user's real IP address but not which sites they visit.
- An egress proxy operated by one of Apple's infrastructure partners, Akamai, Cloudflare, or Fastly, which knows the destination site but not the user.
No single party in the chain sees both sides at once. Your server, sitting at the destination, only ever meets the egress proxy. What reaches your logs is a shared, temporary address that maps to a coarse region rather than the user's actual city or network.
Two details matter for detection. First, the relay only handles Safari traffic, so other browsers and apps on the same device are unaffected. Second, the egress infrastructure is run by a small, known set of companies, which is exactly what makes reliable detection possible at all.
How the Relay Changes What Your Logs See
Before the relay, a visitor's IP address tied them to a network: a mobile carrier, a home ISP, an office. Your geolocation and risk logic leaned on that. After the relay, three things change:
- The address is shared. Many subscribers ride the same egress address at the same time, so per IP rate limits and velocity checks start colliding with strangers.
- The location is coarse. The relay preserves a rough region, a country or a metropolitan area, not the city block your database expects.
- The address rotates. The same subscriber can appear under different relay exits across sessions.
The result reads like textbook anonymization: wide, shared, unstable addresses that defeat per IP assumptions. That is precisely why naive blocklists misfire here, and why a dedicated detection signal is worth building into your flow.
Why This Matters for Your Business
Four areas take the hit first:
- Regional pricing and storefronts. If you quote prices, taxes, or shipping from IP location, relay users see the wrong store or currency, and legitimate buyers quietly bounce instead of telling you why.
- Licensing and compliance. Streaming, sport, and media contracts often specify where content may be shown. You cannot prove compliance from a relay exit address alone, because the exit only approximates the subscriber's region.
- Fraud and abuse scoring. A shared exit address looks like hosting or datacenter space to naive rules, so honest Apple users get over flagged while a few bad actors hide in the crowd.
- Analytics and attribution. Reports built on IP geolocation slowly blur, because the same visitor can appear under different exits over time.
None of this means relay traffic is hostile. It means location data you trusted for routing, pricing, and risk now needs a second opinion per request.
Is iCloud Private Relay a VPN?
To a naive detection rule it looks similar, but the differences matter operationally:
- It only routes Safari traffic. Other apps and browsers on the device keep using the normal network path, so device level signals stay intact.
- It does not let users pick a country. The exit matches their approximate region, so it is not a tool for faking an arbitrary location the way a full VPN is.
- It is tied to an iCloud+ subscription and toggled per device, which is why the traffic skews toward paying, privacy conscious customers.
For your rules engine the practical takeaway is simple: relay traffic is rarely fraud, but it is "location unknown", and that is a different problem to solve than a proxy used to fake a billing country.
The Signals That Give Relay Traffic Away
You cannot spot the relay from the IP string alone, it looks like any other address. The tells live in the network context:
- The egress address sits in ranges announced by Apple's known relay partners, Akamai, Cloudflare, or Fastly, usually in CDN or hosting space rather than residential ISP space.
- The network owner, the ASN, belongs to a content delivery or hosting provider rather than a consumer ISP. Greip's Network Intelligence data exposes exactly this.
- The apparent location is coarse and can disagree with other session signals, like the browser timezone or the billing country.
- The address is shared across many subscribers and rotates over time.
Any one of these signals is weak alone. Together they are why a maintained detection dataset beats hand rolled blocklists, which brings us to the lookup itself.
How to Detect iCloud Private Relay with One Lookup
Greip's VPN & Proxy Detection service powers the security module of the IP lookup endpoint. You call the server side endpoint for the address you already have:
curl --request GET \
--url 'https://v2.greipapi.com/lookup/ip/81.169.177.18?params=security' \
--header 'Authorization: Bearer ***'The params value asks for the security module alongside the basic IP and geo fields that always ship with a lookup.
Request only the modules you need per call. Slim responses keep latency and payload size down on hot paths like login and checkout.
In JavaScript, server side:
const GREIP_TOKEN = process.env.GREIP_API_KEY;
async function inspectClientIp(clientIp) {
const url = new URL(
`https://v2.greipapi.com/lookup/ip/${encodeURIComponent(clientIp)}`
);
url.searchParams.set("params", "security");
const res = await fetch(url, {
headers: { Authorization: `Bearer ${GREIP_TOKEN}` },
});
const body = await res.json();
if (!body.success) {
throw new Error(`Greip error: ${JSON.stringify(body)}`);
}
return body.data.security;
}Never call this from the browser. Keep the token on your server and expose the verdict through your own endpoints. The full request and response reference, including every security field, lives in the docs: IP Lookup.
What the Response Tells You
The security object carries a dedicated flag for this exact case:
relayistruewhen the connection comes through Apple's Private Relay,falseotherwise.relay_countryandrelay_citycarry the apparent location behind the relay when detected, andnullotherwise.vpn_or_proxy,vpn_or_proxy_type,tor,bot,hosting, andis_blacklistedcover every other anonymization and abuse case in the same response.
One round trip and you know whether that signup or checkout request is a relay user or something you should look at more closely. A relay value of true also reframes the geo fields elsewhere in the same response: country and city describe the relay exit region, not the subscriber's home. Treat every location field on that response as apparent location, which changes how you use the rest of the IP Location Intelligence data.
What to Do When You Detect a Relay User
The reflex to block is the wrong one. Relay users are overwhelmingly ordinary, privacy conscious Apple customers, exactly the kind you want to keep. Structure the response around what the signal actually tells you:
- For pricing and localization, fall back to the declared or billing country when the IP is a relay exit. An account address beats a shared exit IP for deciding which store to show.
- For login and payment, treat relay as a soft risk signal, one input into step up authentication, not a verdict. Combine it with device, email, and BIN signals through your Payment Fraud Analysis flow.
- For rate limits, key on the account or device rather than the IP, because hundreds of strangers share that exit address today.
- For reporting, segment relay traffic out of geo based dashboards so city level metrics stop lying to you.
Blanket blocking relay egress ranges rejects a broad population of legitimate customers, and the ranges are shared and rotating, so any blocklist you hand build today will be stale tomorrow. Detect the signal, then route it.
Where to Run the Check in Your Stack
The lookup takes milliseconds, so the usual integration points are:
- Signup and registration, to store the real connection context next to the account from day one.
- Login and session review, feeding the risk score that decides when to step up authentication.
- Checkout, where geography influences payment rules, taxes, and manual review queues.
- Anywhere you resolve an IP to a country for routing, compliance, or personalization.
Because the check is a simple GET with a Bearer header, it drops into any stack, and the same response carries the rest of the security picture, so you are not adding a second call for VPN, proxy, and Tor coverage.
Limits You Should Know About
- Detection reflects the egress side only. The relay hides the subscriber from you by design, so no service, Greip included, can recover the real IP behind a relay.
- Availability varies. Apple does not offer the relay in every country, and the feature has evolved since launch, so treat any list of relay ranges as living data, not a one time import.
- Relay is not the only anonymization. The same lookup flags VPN, proxy, Tor, hosting, and bot traffic, so build one decision path for anonymized connections rather than a special case per type.
- Performance monitoring will not surface relay users for you. The ERN 2026 study found the relay measurably reduces speed test throughput and raises latency on mobile networks while its impact on page load time stays limited, so you cannot infer adoption from your speed metrics alone.
Frequently Asked Questions
What is iCloud Private Relay?
It is a privacy feature built into Safari and iCloud+ that routes web traffic through two proxies, one run by Apple and one run by a partner such as Cloudflare or Akamai, so no single party, including the sites you visit, sees both who you are and where you are going.
Is iCloud Private Relay the same as a VPN?
No. It only covers Safari traffic, it does not let users choose an exit country, and it does not hide activity from the sites you sign into. It blurs IP based location rather than replacing the device's whole network the way a VPN does.
How can I tell if a visitor is using iCloud Private Relay?
Query the visitor's IP address against a detection service. Greip's IP lookup returns a relay flag, plus relay_country and relay_city describing the apparent location, as part of its security module.
Should I block traffic from iCloud Private Relay?
No. Relay users are mostly legitimate, privacy conscious customers. Use the flag to adjust location based decisions, key risk checks on accounts instead of shared IP addresses, and route relay traffic through your normal step up flow.
Can fraudsters abuse iCloud Private Relay?
Any anonymization can be abused, but relay exits are shared by large numbers of ordinary subscribers, so the smarter play is scoring it as one signal among device, email, and payment signals rather than treating the relay itself as evidence of fraud.
Does iCloud Private Relay work in every country?
No. Apple does not offer the feature in all countries and regions, and availability has shifted over time, which is another reason to detect it per request instead of assuming.
Conclusion
iCloud Private Relay is not an attack. It is the new normal: a growing slice of honest Apple traffic that no longer matches your IP based assumptions. The businesses that handle it well are the ones that detect the relay per request, re-anchor location decisions on better signals like billing country and account history, and fold the result into their fraud and personalization flows instead of blanket blocking.
Greip makes the detection side a single server side call. One lookup with the security module returns the relay flag alongside VPN, proxy, Tor, bot, and hosting signals, so your rules engine can act on the full picture instead of guessing from an address that is, by design, no longer tied to a person.
Get started
Start protecting your business today
Our service is trusted by thousands of businesses worldwide.
- 1,000 requests during trial
- Cancel anytime
Keywords
Share this article
Related Articles
Best IP Address Lookup Tools In 2026
IPv4 vs IPv6: Key Differences and What They Mean for IP Lookups
The Role of IP Geolocation in Combating Account Takeover (ATO) Attacks
5 Benefits of IP Geolocation for Your Business and How to Use Them
Using IP Geolocation to Prevent Location Spoofing in Online Transactions
