If you're working from a school, it's likely that you need some of our pages to be whitelisted; your system admins can take care of that for you. Just send them this list to be whitelisted so you can access everything on Shmoop:
- www.shmoop.com
- schools.shmoop.com
- media1.shmoop.com
- video.shmoop.com
- blog.shmoop.com
- d395x7ewlfzo3v.cloudfront.net
- d2f3klyjhomdpt.cloudfront.net
- d32v6r6fgi4k49.cloudfront.net
- support@shmoop.com
- id.shmoop.com
- cdn.jsdelivr.net
- learnosity.com
You might be wondering why we can't give you a list of IP addresses to whitelist (or, uh, maybe you're not wondering that?).
Answer: the Shmoop web site is built upon an elastic infrastructure that is designed to expand or contract in capacity as demand fluctuates. Additionally, many site resources, such as videos and images, are cached in geographically distributed locations to facilitate faster delivery. These features greatly improve the site's responsiveness, but they also mean that Shmoop content originates from broad, frequently-changing ranges of IP addresses.
For this reason, we strongly recommend whitelisting us by DNS name (listed above) instead of by IP address. For anyone who must whitelist by IP, our hosting company, AWS, provides a way to programmatically pull the current range of IP addresses in JSON format. For more information, see the following two links:
Note, however, that these lists include all AWS servers, not just Shmoop's.