Tropo.com HTTP server IP ranges for whitelisting

MarkSewell -

Since Tropo is now a part of Cisco, and we have moved our shared staging and shared production to our new data centers, we have adopted a new policy of not providing a static list of IPs to white-list traffic for these environments. This is a common policy for cloud providers that Cisco, Google, Facebook and others use.

Having said this, while the IPs will always be subject to change, we have provided a DNS record with a TTL of 30 seconds that may be queried to obtain the current set of active IP addresses. With this, you may run a query like this:

nslookup -q=TXT _netblocks.tropo.com 8.8.8.8

Which will return something like this:

Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
_netblocks.tropo.com text = "158.85.28.0/27"
_netblocks.tropo.com text = "169.45.201.240/28"
_netblocks.tropo.com text = "169.55.76.144/28"
_netblocks.tropo.com text = "198.11.254.97/27"
_netblocks.tropo.com text = "199.230.57.181/32"
_netblocks.tropo.com text = "199.230.57.187/32"
_netblocks.tropo.com text = "199.230.57.188/32"
_netblocks.tropo.com text = "199.230.57.189/32"
_netblocks.tropo.com text = "199.230.59.185/32"
_netblocks.tropo.com text = "199.230.59.186/32"
_netblocks.tropo.com text = "64.79.136.21/32"
_netblocks.tropo.com text = "66.193.54.21/32"

NOTE:: Whitelist information is not currently available for Tropo.eu

You may then use this information to update your white-lists. But these are dynamic and subject to change as indicated before. You would need to have something like a cron job that would query this and update your white-list on a periodic basis (again the TTL is 30 seconds).

Here is a high level example of how this type of situation may be handled with AWS IP Addresses / Security Groups as they have a similar policy:

https://gist.github.com/jsgoecke/b2fd21105277441663fc

Have more questions? Submit a request

0 Comments

Article is closed for comments.