3 ms·

Broken link - it just says "403 Forbidden"

• exploraz 3mo ago
  Still working for me, your IP or browser request might be flagged by their firewall or anti-bot protection
• ButlerianJihad 3mo ago
  [flagged]
  • inigyou 3mo ago
    I'd like to hear what behavior you imagine I've done. "This is a broken link" is not a "tangential annoyance" and is a valid reason for flagging. It's also appropriate to comment, so that the poster or moderator can fix the link.
    • hunter2_ 3mo ago
      Perhaps the bad behavior is failure to remove a compromised (botnet) device on your network that has been attacking one or more sites that use a popular security solution. "Broken link" is not an accurate way to describe this situation.
      • exploraz 3mo ago
        Other hypotheses: - VPN/Proxy/Datacenter IP/Tor usage - Censorship bypass tools triggering destination server's firewall (suspicious TLS fingerprint or connection characteristics, or bad proxy IP) - Bad ISP (e.g. one ISP IP address or range of addresses shared by so many users that could create collateral damage if one or more user gone rogue) - Actual botnet/hidden residential proxy exit node on the same IP/local network (e.g. TV boxes or SDKs embedded inside apps that users are not aware of) - Strict privacy settings (unlikely to cause 403 straight away), or obscure browsers (also unlikely, but can trigger firewall because of connection fingerprint/characteristics) - Actual bad behavior (scraping, etc)
        • hunter2_ 3mo ago
          Your 4th hypothesis is equivalent, not "other," to mine. But I agree that it could be anything you mentioned, as all of them have crossed my mind as possible reasons why I experience "verifying you are human" and "find the motorcycles / busses / traffic lights" more often on my residential ISP than on my cellular or work ISPs, and the unknown botnet/exit node seems most probable (by far) when considering my own traffic. I never have the 403 problem discussed here, luckily.