Cloud IP check
See whether an address belongs to a cloud, a CDN or a large platform, and which region and service, using the address lists the providers publish themselves. Paste one address, a list, or lines straight from a log.
Where the data comes from
Each provider publishes its own address list, mainly so customers can write firewall rules. This tool searches a copy of those lists taken on 2026年9月26日. Providers add ranges every week, so a very new address can be missing.
- Amazon Web ServicesCloud · 11,251 ranges
- Microsoft AzureCloud · 61,283 ranges
- Google CloudCloud · 1,103 ranges
- GoogleOnline service · 145 ranges
- Oracle CloudCloud · 1,107 ranges
- DigitalOceanCloud · 1,230 ranges
- Akamai Cloud (Linode)Cloud · 5,505 ranges
- CloudflareCDN · 22 ranges
- FastlyCDN · 21 ranges
- GitHubOnline service · 335 ranges
Provider names are trademarks of their owners. MyIPKit is not affiliated with, or endorsed by, any of them.
完全在你的浏览器中运行 — 不会发送到任何地方
Where the lists come from
Large providers publish machine-readable lists of their address ranges so that customers can write firewall rules without guessing. This tool merges those lists into one index and keeps, for each range, the region and service the provider gives it.
Allow the narrowest range you can
Allowing “all of AWS” through a firewall admits every AWS customer, including anyone who rents a server for an hour. When a rule has to name a provider, name the specific service and region, such as the webhook ranges a service documents. Take the ranges from the provider’s own list, which changes every week, rather than from a copy that goes stale.
Reading a log with it
- Scanners and scrapers mostly run from cloud ranges, because servers there are cheap and disposable.
- A login to a personal account from a cloud address is worth a second look: people rarely browse from a data centre.
- But not always. VPNs, corporate proxies and privacy relays also sit in the cloud, so treat this as one signal, not a verdict.
Why would I want to know this?
Three common reasons. Reading logs: a burst of requests from cloud ranges is usually a script, not a person at home. Writing firewall rules: allowing a service’s webhooks, or only a CDN, in front of a server. And checking your own setup: which provider and region your traffic actually leaves from.
How reliable is the answer?
A match is as reliable as the provider’s own list, because that is what it comes from. No match is weaker evidence: the list may have changed since this copy, and many hosts publish nothing. The date of the copy is under “Where the data comes from”.
Should I block every cloud address?
Usually not. VPNs, corporate proxies, privacy relays and plenty of legitimate services run in the cloud. Treat a cloud address as one signal to weigh alongside what the traffic is actually doing.
Can I paste a whole log?
Up to 100,000 characters. Every IPv4 and IPv6 address in it is picked out, including ip:port forms; duplicates are dropped and the first 1,000 are checked.
Is what I paste sent anywhere?
No. The published lists are downloaded to your browser once and searched there. The addresses you paste are never sent to MyIPKit or anyone else.