Proof of Internet Censorship by Security Agencies – Here’s How

1169ckCOMIC-surveillance(Click image to enlarge)

“We had a real eye opener last week. Many people had trouble reaching, but some people had no problems whatsoever. The servers were all operating normally; what could cause this problem? I won’t get overly technical, but I think you’ll find the evidence to be persuasive that we’re now entering a new stage of internet censorship, done a bit differently than you might have expected…”

If there is anything online here at WRSA (or at the old site) that you need, you should already have an offline (and preferably paper) copy of it.

Ditto for any other online resource.

If it is online, it has already been compromised by the National Socialist Surveillance State.

Of where you reside, along with its allies.

Screw NSA, GCHQ, and the ilk.

Right in the trachea.

18 responses to “Proof of Internet Censorship by Security Agencies – Here’s How

  1. Sorry, but without the “before” (or even “after”) traceroutes, this is sensationalist BS. I could as easily claim that when my cable goes out it’s Mossad. Get a grip.
    Internet centralized to a couple hundred IXPs ( – news at 11.
    The point may still stand that you need offline copies – but hatriot please, just because you aren’t multihomed doesn’t mean you’re important enough to shut off.

  2. I’m curious what Denninger has to say about this. There aren’t many that understand the bowels of how the internet works as he does.

    I’ll cross-post over on MT.

  3. Oh please.

    Look, I’m all for claims that things are happening if they really are, but….

    As someone who ran an ISP for nearly a decade and has built networks for a living for a lot longer than that, this is poorly-researched nonsense. Please understand what you’re looking at and how the Internet actually works BEFORE leveling such accusations.

    You need to do a lot more homework.

    • Questions to you and LastBox:

      Given your (presumably founded) disdain for the thesis of the article, it is still possible that there are ways for .gov to restrict access to certain sites/search terms so as to degrade service, right?

      And if so, would not one of the primary defenses against such an attack be to have offline versions of all essential info?

      That was the point of the post, at least from the editorial perspective here.

      Appreciate all of the work that both of you do for freedom.

      • And if so, would not one of the primary defenses against such an attack be to have offline versions of all essential info?

        No. A personal collection of downloads is not a substitute for a working Internet. What the Bad People want is for you to continually reduce your lifestyle until you willingly reduce yourself back to chattel slavery. By preparing to retreat from the Internet, you are complying. You complied when they banned inexpensive cars and private communications. You complied when they banned saving for retirement. You complied when they set up checkpoint Charlies called TSA strip searches. You complied when they banned inexpensive healthcare. You complied by agreeing that freedom of travel and employment, otherwise called open borders, is bad. You plan for there to be no end to your complying. There is a straight line of compliance between your former prospects decades ago and getting on the boxcars, and you are on that path.

        So, no. If you download offline copies you are actively retreating. If you were advancing then you would work today to expand the Internet. You would give up Windows for Linux, TAILS, and Namecoin. You would be a pioneer and move this blog to the censorship-resistant alternatives which already exist.

        • More detail and an implementable plan.


          • More detail and an implementable plan. / Please.

            Let me suggest that setting up a blog on a TOR hidden service is about as complex as changing the crankshaft bearings in your car’s engine. Many people already know how to do this; in your youth hotrodding was a major hobby of young men. However, if you aren’t already a good mechanic, I can’t fit a foolproof recipe in a comment.

            I urge you to find a Linux techie local to you, who you can work with face to face on this project. The high level steps are to: create a Linux server, add TOR to it, add a web server to it, make the web server hidden, add wordpress to it, export your existing wordpress site, and import it to the new server. The first try might take a solid week of work. Here is an overview of the TOR parts:


            For the first pass you could use an old laptop sitting on your or the techie’s home Internet connection. Your techie will make notes as he walks through the recipes and gets a hidden server working. Then, follow the notes and do it again on one of the inexpensive, techie-friendly hosting services such as or

            At that point you will have two blog sites, the old one which everybody including you knows how to use, and the new experimental TOR one. At that point I’d suggest you don’t do duplicate updates to the TOR blog, you can always catch it up with another wordpress export. Instead, take about a month to urge the readership to figure out how to interact with the new blog. In this interim, documenting the server creation process you followed so that others could do it would be a great source of blog posts. Ask blog readers to give TAILS a try. You can read .onion from the normal web with although there is no additional protection to the reader. After you are comfortable with the hidden service being the primary blog, do a last update from the existing wordpress and then leave a “we moved” sign.

            Estimated budget: $50/month hosting fees. One fairly recent laptop to set up a prototype server on at home. One solid week of techie work to set up that first server. One calendar month of blog topic detour while you help the readership debug their new access route to the new server. A relationship with a techie to debug problems that come up, perhaps a weekend of fussing with every few months.

          • set up a mirror-site(s), like Rawls @ SurvivlaBlog did. There are various online sites you can plug into that will facilitate this. Can’t get to my e-mail right now, but will cite a good one after I get off work…

          • Backups of server data are static snapshots. Maintaining comms for as long as possible is more important than stale data, is Anon’s point, I believe.

            Agree that taking servers to darknet gets around censorship *as far as we know*. Nearest analogy might be numbers stations, though decentralized. Takes moderate technical chops, but in no way out of reach to someone with a will. Route that person to me.

            Other course of actions?

            Set up a wallet and post the public address – start accepting donations. Buy a solvent trap with what you receive – document touching the monolith for others.

            Establish an IRC channel/server for people here to communicate in in real time. I maintain one on the darknet, but perhaps a clearnet channel would be best to start.

            Establish an informal RF freq / schedule. Sparks probably has ideas on this lightyears ahead of anything I could offer.

            Take all interested parties in crowdsourced intel and push them to grok news aggregation sites such as Reddit. allows anyone to vote and publish links of interest.


        • Dear Anon: I would wager that you don’t get around very well in the woods.



          • There are no woods in the city. I’m overweight and eat soda and Cheetos while sitting on the couch watching TV sitcoms about men who are confident enough to talk to women. After a few disasters in high school I’ve never had a real date with a woman, and men find me both abrasive and ignorant. I have few friends, and no good friends. I’m just like that computer guy portrayed in the movie Jurassic Park; everyone knows Hollywood tells only the truth.

            Go out and meet your local Linux user group in meatspace, you may be surprised how many of the hardcore computer techies don’t fit the stereotype you have in mind. Popular hobbies include rock climbing, kayaking…and guns.

  4. From a technical point of view it is interesting that the site is dropping packets at very specific points during the transmission of the packet. I am assuming they are having these issues with TCP/IP as wll as PING. TCP/IP is a connection oriented protocol or a “reliable” protocol. During TCP/IP connection if a packet is dropped the protocol will determine what packet was dropped and request the packet be sent again from the sending source. This will ensure that all packets are received and combined on the receiving end.

    As you know we normally don’t see TCP/IP connections when dealing with certain streaming protocols, streaming video, Voice Over IP VOIP and other protocols will use a stateless protocol, the protocol will not “guarantee” delivery of every packet. You could imagine if while watching a live streaming video if all of a sudden one of those dropped packets was resent and then displayed, it would be out of sync with the picture and the live streaming feed.

    The interesting part of this is that it seems the packets are being dropped at the ISP or Cloud provider or whomever. Several things could cause this, all of which are very normal. A network layer driver could be corrupted or require an update, depending if Fiber is being used the optic could be dirty, the fiber channel could be configured wrong, the fiber wiring itself could be wrapped to tightly or crimped (imagine a water hose folded over on itself, only a trickle of water can get through the crimped piece.

    To me this looks like a bottle neck, something is causing the packets to load up and basically wait in line to get through the switch. Again a misconfiguration could account for this, also using the Monitor port on a switch could account for this. Switches direct traffic to specific ports VS. a Hub which sends all traffic to all ports. For someone to monitor all traffic on a switch they need to configure the “Monitor” port. This port will direct all traffic or specified traffic traversing the switch into the Monitor port. This port acts as a shunt which sends the selected traffic off usually for analysis by Network Intrusion Detection (NIDS) / Intrusion Prevention (IPS) software or hardware. The traffic is examined in real time looking for signature matches usually trying to prevent malicious behavior.

    On the flip side the traffic being analyzed can also be examined for content as well, such as his site, everything there is being sent over HTTP:// basically clear text, all comments, posts, pages visited…everything is seen as it is, no decryption needed. (I suggest to all webmasters to run HTTPS:// all the time on every page they serve up, in this day and age it isn’t expensive and it will add to the overall layers of security that help prevent data leakage.

    So a couple things, misconfiguration, bad equipment, and configurations in order to sniff traffic could all cause this symptom. Not saying they aren’t a victim of targeted Denial of Service (DoS) or Distributed Denial of Service (DDoS), just saying they have got to start investigating a little more. If security and privacy are their real concern then they need to dive into the service providers, find out what type of equipment they use, if they patch the equipment when known or suspected attack vectors are found, if the patching only occurs at the customers request, how does the customer find out what vulnerabilities are on the equipment his traffic passes through? There are tons of due diligence questions that must be asked of service providers and then those questions must be followed up with validation of a 3rd party or yourself…trust but verify.

    And really… buying an SSL/TLS certificate for you site isn’t all that expensive these days and running everything in HTTPS:// is really a requirement these days. We don’t have to make it easy for people to sit on a switch and sniff traffic, lets at least make them work for it. I would much rather see some .gov jackhole spend all his time and resources decrypting my gibberish blog comments than have that same .gov jackhole be able to just run a tool and see everything we write or surf as clear text so they can then move on to other things…make them earn every piece of data they scrap from the net, don’t freely give them anything.

  5. It’s actually pretty simple to stop routing by controlling the DNSs. Many providers use Google DNS servers, and Google has already been known to tamper with directs to various domains. Anyone trying to connect using those compromised DNS servers can be redirected or stopped cold. There are ways around this like DNSCrypt with OpenDNS (, but those could be commandeered as well under the patriot act. A good out of country DNS would be a nice alternative.

  6. DOS attacks on IXPs and ISPs are pretty common. When an IXP is attacked it will knock out communications through that exchange quite handily, so users who have a default route through that IXP will experience data loss until the routers update their routing tables, assuming that the routers in question are using a protocol that sends link load statuses to neighbors. Anyways, it takes time for networks to reach convergence due to a DOS attack, so in the absence of actual evidence that the reason for loss can be traced back to some government agency, it remains supposition of censorship, nothing more.

  7. anyone here recall what happened to ALL the .geocities sites a few years back? Tens of thousands of wonderful history and etc. sites? Got the Helen Thomas treatment. Disappeared. Vaporized all at at once. Why? Billionaire ZOGsters at Yahoo (currently, Larry Page/Melissa Meyer and co.) bought out the creators, making them all minor millionaires, then decided there wasn’t enough porn to make $$$ and pulled the plug on the servers. Recently Yahoo bought Tumblr and, since that’s mostly porn, it’ll survive. Next on the ZOG hit list: blogspot, wordpress. In the largest sense, that how collectivist-globalist ‘net censorship does/will work.

    • If you can’t stand over the backup/export copies of your blog while holding a gun, you don’t own it.