#323 WAN IP Resolution - banned from whatismyip

Email (18)

The WAN IP Resolution within the E-Mail function shows the following text:


You have been banned from this page.
We've put measures in place to keep people from hitting our site at an unreasonable rate.
We ask that you only hit our site once per every 5 minutes to get your IP address.
Our system must've detected overuse by you and therefore banned you.
Are you running an automated script to get your IP?
Once we figure out what caused the ban and get that fixed, we'll unban you.
Send questions to banned2 at whatismyip dot com.

Please set your code to scrape your IP from www.whatismyip.com/automation/n09230945.asp


Perhaps whatismyip recognizes the footprint of the requester engine?


  • Peter Easdown

    Peter Easdown - 2011-05-26


    As I've stated in an email recently, this problem is only happening because (as I understood your email) you are deliberately triggering alarms to test how iAlertU works. The _free_ service at www.whatismyip.com that iAlertU used to identify the WAN IP address rightly watches how often a given IP address uses it's service. Remember that it's free, and they need some way to prevent the service being abused.

    In normal operation, iAlertU will only use this service if the alarm is triggered, and this should only happen if your mac is being stolen, or if you mistakenly trigger the alarm yourself. This should be a rare event. On this basis, the use of whatismyip should not be excessive and should not result in you being "banned".

    For your IP to be banned, you either have a problem whereby the alarm is bring triggered over and over again in a short space of time, or as you've indicated in your email, you are performing tests that are causing the alarm to be triggered at an unusually high rate.

    The whatismyip service is probably quite justified to bann your IP for a period until you stop triggering the alarm.

    I'm disinclined to change iAlertU regarding this, as it's simply doing what it's designed to do. Regardless of whether your Mac has a static or dynamic IP address, it is the role of the app to try and identify where the mac is physically. To do this it tries to report anything it can about where it is such as the WAN IP address, the geographical location, etc.

    The mechanism suggested by the message from whatismyip is already being used. There's nothing more I can do to iAlertU from that point of view.

    If in fact you're not "testing" iAlertU anymore, and the alarms are triggering over and over again without your doing anything, then this is a problem with iAlertU. If this is happening, then please post or email your console log for analysis.

    Please clarify your situation. Are you testing as described above, or is there actually a problem?


  • Peter Easdown

    Peter Easdown - 2011-05-26
    • assigned_to: nobody --> ezsource
  • Peter Easdown

    Peter Easdown - 2011-05-26

    OK, it's sorry time.

    My previous post was written using an incorrect assumption that this was a duplicate issue to 3305510 from the same person.

    Whilst most of the technical detail of my post is correct, I acknowledge that we haven't had an email conversation thus far.

    I'm guessing though that you are on the same local network as the one used by the author of the other tracker item (3305510). It's too much of a coincidence that you've both hit the same problem so close together.

    I suspect that the testing done by the other user has resulted in everyone on that network being banned.

    again sorry for the confusion. Please provide more detail if I'm still barking up the wrong tree.


  • Peter Easdown

    Peter Easdown - 2011-06-14
    • status: open --> closed-works-for-me
  • Peter Easdown

    Peter Easdown - 2011-06-14

    Not a problem with iAlertU.



Log in to post a comment.