Privacy
This site has no cookies, no analytics, no ads and no server-side code. Checking an address against AWS's IP ranges happens entirely in your browser. A few features need outside services, and this page lists exactly what each of them can see.
Last updated 2026-09-25.
The short version
- Nothing to track you. No cookies, no analytics or tracking scripts, no ads and no third-party code of any kind. The site is a set of static files, so there is no account, no database and no record of your lookups on our side.
- Your lookup stays in the address bar. The address or hostname you look up goes after the
#in the page URL. Browsers don't send that part to any server. - Matching happens in your browser. Your browser downloads AWS's public list of IP ranges and compares your address with it locally.
- Outside services only when needed. AWS serves the data file, Cloudflare hosts the site, a DNS resolver answers hostname lookups, and RIPE NCC answers the optional network check. None of them learns more than the table below says.
The part after the #
A lookup link looks like https://iptoawsservice.aroncreates.com/#3.18.1.10. The part after the # is called the fragment. Browsers keep it to themselves: it is not included when the page is requested from the server, so the host never sees what you looked up. The site also sets a "no referrer" policy, so sites you visit from here aren't told which page you came from.
The fragment is still part of the address, though:
- it appears in your browser history, like any page you visit;
- anyone you send a lookup link to can see what it looks up.
The small search boxes on the guide and reference pages send you straight to the home page with your query after the #, too. One exception: if JavaScript is turned off, or hasn't loaded yet when you press Enter (on a slow connection, in the first moments after a page opens), a search box submits a normal form as /?q=…, so that one request carries your query to the host in the page address. The home page moves it after the # as soon as its script runs.
Who sees what
Every request this site's pages make below goes directly from your browser to the service named, without cookies and without a Referer header. Following a link to GitHub is an ordinary visit, under GitHub's own policy. Like any website, each service sees your IP address and basic browser details (the user agent). For requests to other sites, browsers also send an Origin header naming this site.
| Who | When | What they receive | What they don't receive |
|---|---|---|---|
AWSip-ranges.amazonaws.com |
When the page downloads AWS's IP list, or checks whether a newer version exists | A request for its public data file, from your IP address | What you look up |
Cloudflare, as hostiptoawsservice.aroncreates.com |
Every page and file you load from this site | The page address without the fragment (including ?q=… if you used a search box before JavaScript was running), from your IP address |
The fragment, and your results |
Cloudflare DNScloudflare-dns.com |
When you look up a hostname, or click "Look up reverse DNS". Names that public DNS can't answer for, such as localhost, .onion, .local, .internal and EC2 private names, are explained on the page and never sent; single-word and other private-network names are sent only if you ask for it |
The hostname you look up. For reverse DNS, the IP address you asked about, written as a DNS name (for example 10.1.18.3.in-addr.arpa for 3.18.1.10) |
Anything else about your lookup |
Google Public DNSdns.google |
Only when Cloudflare's resolver fails or doesn't answer in time | The same as Cloudflare DNS, for that query | Anything else about your lookup |
RIPE NCCstat.ripe.net |
Only when you click "Check who announces this IP", or automatically if you ticked "Check this and future addresses automatically" (see stored settings) | The IP address being checked, and a tag naming this site, which RIPEstat asks its users to send | Anything else about your lookup |
| GitHub | Only if you follow a link to the source code or issue tracker | A normal visit to github.com | Anything about your lookups |
More detail:
- DNS. When a resolver looks up a hostname, the domain's own DNS servers see a query from the resolver, not from you. When this site asks Google, it switches off EDNS Client Subnet, so Google doesn't pass on which network you're on; Cloudflare's resolver never passes it on.
- Hosting. The site runs on Cloudflare's static hosting. Its Workers request logs are switched off, but Cloudflare still handles every request as the host, and its standard traffic and security analytics can record request details such as the page address, under Cloudflare's own policy.
- Their policies: AWS, Cloudflare, Cloudflare's public DNS resolver, Google Public DNS, RIPE NCC and GitHub.
What is stored on your device
- No cookies.
- One setting in localStorage:
ripeOptIn. It is only created if you tick "Check this and future addresses automatically" under the network check (ticking it also checks the address on screen). While it is set, the page sends every address that isn't in AWS's list to RIPEstat without asking. Untick the box, or clear the site's data (below), to remove it. - A one-time flag in sessionStorage:
lookupFocus, a timestamp set when you use a small search box on another page, so the home page knows to move keyboard focus to your answer. It never contains your query, and the home page deletes it as soon as it loads. - A copy of AWS's public data in IndexedDB: a database named
iptoawsserviceholding the processed IP list with its version and publication date, so the next visit can answer immediately. It contains nothing about you or your lookups. - Your browser's normal cache may keep the site's files and AWS's data file, as it does for any website.
- Results in memory only. Results are kept in the open tab so Back and Forward are instant, and they are gone when you close it.
How to clear it
Clear the site data for iptoawsservice.aroncreates.com. That removes the ripeOptIn setting and the saved copy of AWS's data; the next visit simply downloads AWS's list again.
- Chrome and Edge: click the icon to the left of the web address, open Site settings and choose Delete data. (Chrome help)
- Firefox: click the padlock in the address bar and choose Clear cookies and site data. (Firefox help)
- Safari on a Mac: Safari, Settings, Privacy, Manage Website Data; search for
aroncreatesand remove it. (Safari help) - Safari on iPhone and iPad: Settings, Apps, Safari, Advanced, Website Data.
A private or incognito window keeps none of this after you close it. Lookup links stay in your browser history until you clear it.
Changes and questions
If what this site does with data changes, this page and its date will change with it. The site's code is public on GitHub, so you can check every request it makes. For questions, open an issue; issues are public, so don't include anything you want to keep private.
More: how it works · about this site