The contains/doesn't contain feature was inspired by all the badly implemented sites I've seen which does not care to return proper HTTP status codes. I actually meant to implement regex matching as well, but sadly such a feature would be hard to protect against pathological DOS attacks.

The "2 click unsubscribe" part was meant to convey the ease of deleting the monitoring subscription if you for some reason would find them bothersome. Why did it not make sense to you?

I understood it when I read it, but now that I look at it, I can see why it might be confusing. Someone could think it is saying "To click, unsubscribe" in IM-speak. Maybe it should be "Two-click unsubscribe."

A combination of the sentence fragment, and thinking it might have been IM speak as roryokane suggested. "2-click" instead of "2 click" would do a lot to clear that up.

I definitely didn't pick up what you meant, but now that its been explained it seems obvious. For maximum clarity, I would change it to:

"We only send email when your site goes down. Unsubscribe in 2 clicks."

i actually don't understand this feature and would have liked some explanation. do i provide a regex that should match the http response? or do i provide a header code or tyep?

I'll look into giving some clearer explanation. The feature does a simple non-regex match of the provided string against the returned HTTP body. I don't think I'll be implementing regex matching since such a feature would be hard to protect against pathological DOS attacks (as I mentioned in another thread).