Darren Weeks
Coalition to Govern America
January 13, 2016

 

We've been covering the Hammond case and the protesting ranchers at Malheur National Wildlife Refuge. This past Saturday, Vicky Davis and I debunked Establishment media myths and some of the alarmism that the media is trying to drum up to sensationize this event as wacko militia extremists attacking Oregon. Nothing can be further from the truth.

 

Regardless of whether you agree with the tactics of the ranchers — we certainly do not condone illegal activity — the issues that these folks have brought to the forefront are real and must be addressed if we are to have any semblance of freedom to pass down to future generations. I encourage readers to listen to Saturday's show for background on the current situation, then read up on the details. We must know the facts, not media manipulation, distortions, and outright lies.

 

Following this past Saturday's broadcast, I've been noticing a Washington D.C. IP address lingering on our Shoutcast stream for days at a time. The address was 108.45.85.1 and it is owned by the Verizon network. At first, I blew it off because there are people who live in D.C. and it could have been a resident who happens to live there. However, after it continued to linger all weekend, I decided to do a Whois lookup on the address. It traced straight to the seat of oppression.

 

 

After that, there also appeared another IP address from the D.C. area which also lingered. It was 108.45.85.169 which also belonged to Verizon Online, LLC. A Whois lookup on this addressed traced straight to the White House.

 

 

To sum it up, it appears we are being monitored. It seems Washington D.C. realizes the truth media is the only place to turn to find out what's really going on in America, because they certainly won't get the real story from the Establishment media.

 

UPDATE — February 3rd: We now have proof that the entity utilizing the IP address mentioned above (108.45.85.169) has hacked into our Shoutcast D.N.A.S. server. After logging into the server, we noticed that exact address was placed into the "Reserve IP" section, giving them access to our stream — even if the stream is at full capacity. Hence, not only are they monitoring, but they went to the trouble to hack in to make sure they don't get bumped off, in the event we reach capacity.

 

Additionally, when we take the stream down, then bring it back up again, this address connects with multiple connections and different players from that same IP address. In other words, it apparently is programmed to try really hard to get the stream back. This obviously has all of the signs of a highly sophisticated operation.