Hacker News new | past | comments | ask | show | jobs | submit login

That's actually a really viable theory, especially given the "can't search for traceroute" thing - that spits out what seems to be a time-based error string.



It’s not, that’s just standard akamai WAF behaviour.

E: sorry, HN is throttling me and I can’t reply below. This is just a silly web application firewall that blocks a list of “suspicious strings”. There’s not much else to be said about it.


Can you explain in more detail? captcha.nsa.goving for more information didn't return anything.


(I've turned off the throttling since your recent comments look to have been fine. Please don't do flamebait/flamewar in the future!)




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: