It looks like you're using an Ad Blocker.

Please white-list or disable AboveTopSecret.com in your ad-blocking tool.

Thank you.

 

Some features of ATS will be disabled while you continue to use an ad-blocker.

 

Check if NSA warrantless surveillance is looking at your IP traffic

page: 4
14
<< 1  2  3    5  6  7 >>

log in

join
share:

posted on Jul, 4 2006 @ 05:14 AM
link   
You're right Buddha.


14 183 ms 181 ms 182 ms eli-gw.abnva.ip.att.net [192.205.32.73]
15 311 ms 313 ms 319 ms tbr2-p012201.sffca.ip.att.net [12.123.13.186]
16 293 ms 316 ms 316 ms tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]


See how the sffca line is not right above or below a non-ATT line? That means that the NSA is not peering into your private life. Whew!




posted on Jul, 4 2006 @ 07:31 AM
link   
thanks watch the rocks, I can only hope you are not trying to decieve me as i wouldn't know better at this stage, I am a trusting person normally sometimes to my detrement but i have a good feeling about what you have said only for my own peace of mind. If you are an Aussie you've gotta be a good bloke in my books.
but lets get this straight, they are keeping tabs on my internet perusal but not my day to day interactions with people. coppers do a good enough job of that i suppose.
Kind Regards
Buddha



posted on Jul, 4 2006 @ 07:41 AM
link   
OK can anyone tell me what this all looks like to them? I don't get the address the op talked about but I do get the nsa over 30 hops thing. Also quest is on here I thought they were one of the phone companies refusing to hand over data. And what is in Charlotte N.C. ? How can I take these numbers and find out anything about who is tracking me? TIA

C:\Documents and Settings\Owner>tracert nsa.gov

Tracing route to nsa.gov [12.110.110.204]
over a maximum of 30 hops:

1 285 ms 171 ms 171 ms nas30.charlotte2.nc.us.da.qwest.net [63.152.3.20
5]
2 168 ms 171 ms 171 ms 65.134.75.254
3 201 ms 182 ms 182 ms dca-edge-13.inet.qwest.net [63.152.125.49]
4 179 ms 182 ms 182 ms dca-core-02.inet.qwest.net [205.171.209.77]
5 179 ms 182 ms 182 ms dcx-core-01.inet.qwest.net [205.171.8.222]
6 179 ms 182 ms 182 ms dcp-brdr-02.inet.qwest.net [205.171.251.34]
7 179 ms 182 ms 182 ms qwest-gw.wswdc.ip.att.net [192.205.32.29]
8 190 ms 193 ms 192 ms tbr1033301.wswdc.ip.att.net [12.123.8.186]
9 178 ms 182 ms 182 ms ar2-a3120s6.wswdc.ip.att.net [12.123.8.65]
10 190 ms 181 ms 182 ms 12.127.209.214
11 201 ms 182 ms 193 ms 12.110.110.131
12 * * * Request timed out.
13 * *



posted on Jul, 4 2006 @ 07:52 AM
link   
Ahh, don't you worry Buddha. Just sit there while I report my disinformation to my section head (jk, jk . . .)

Goose, you are also alright. In fact, 'sffca' doesn't even show up on yours. You lucky thing . . .



posted on Jul, 4 2006 @ 08:02 AM
link   
Great, now I feel all left out.



[edit on 4-7-2006 by goose]



posted on Jul, 4 2006 @ 08:05 AM
link   

Originally posted by watch_the_rocks
Goose, you are also alright. In fact, 'sffca' doesn't even show up on yours. You lucky thing . . .


Why are we so sure this is the only source of concern? It doesn't make sense to me.



posted on Jul, 4 2006 @ 08:42 AM
link   
After googling all the addresses I found more info which makes me think I have not completely been left out apparently according to what I am reading this means they are reading your email, I found on my trace 3 times. Here is also a different way to do the trace much easier for people who are not real familiar with dos.
www.dnsstuff.com...

.wswdc.ip.att.net
.wswdc.ip.att.net
.wswdc.ip.att.net

which I have on my trace I ran, can anyone verify that info, as I am not too sure about it?



prisonplanet.com...
Go to www.dnsstuff.com you will find a range of tests you can perform, quickly and easily, on the right of the second row you will find a red box labeled Traceroute. Let us enter then , say the text ... nsa.gov ... or even their IP address... 12.110.110.204 and press the button.

A list will be returned showing the times and route of the packet - you will in the column labelled HOSTNAME that the signal will travel through a switch labelled like this

tbr1-p013901.wswdc.ip.att.net. or maybe
ar2-a3120s6.wswdc.ip.att.net.



posted on Jul, 4 2006 @ 08:56 AM
link   
I still think it might be interesting to see what traceroute revieled while attempting to access
certain Islamic web sites.

I tried trace route to AlJezeera's contact page and it went from Level 3 Washington
to Level3 Paris then through reverse.completel.net and timed out.



posted on Jul, 4 2006 @ 09:23 AM
link   
Well if you go here www.dnsstuff.com...
and do a search on the IP address from the trace, you get back tons of info I am a total novice on the computer and this is easy, figuring out what it all means is another thing.

I got back that many were registered to BOGUS, some did not exist or was fake and in some when it gave another link to click it went straight to ATT, many were listed as the address to report stuff to like fraud or spam, some went to ATT4 whatever that means?

If you want to see what all those numbers mean go to the website above and also there are a ton of searches you can do at the link listed.

[edit on 4-7-2006 by goose]



posted on Jul, 4 2006 @ 12:21 PM
link   

Originally posted by Imperium Americana

Originally posted by CelticHeart
I don't live near Atlanta. I don't even live in Georgia. I live in North Carolina.


Yeah you will see Atlanta since most all traffic, in the South East, will switch in Atlanta, Georgia Tech.



My mama doesn't live in Atlanta, yet why does mine do that and hers doesn't. In fact she lives on the same street as I.



posted on Jul, 4 2006 @ 01:17 PM
link   

Originally posted by ShadowEyes

Originally posted by watch_the_rocks
Oh yeah, oh yeah, I'm safe, I'm safe.





Ummm, you might want to look at the 5th line in the sequence.

Aren't those the ones that mean you're being watched?
.


Oops. Sorry to scare you. I read another post farther down and it looks like you're o.k. as the sequence has an ATT line both above and below it.

.



posted on Jul, 4 2006 @ 01:27 PM
link   
NSA. GOV



2 35 ms 36 ms 36 ms 207.42.20.1
3 36 ms 37 ms 37 ms 192.168.1.1
4 53 ms 54 ms 53 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 96 ms 129 ms 120 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
6 248 ms 210 ms 119 ms sl-bb20-nyc-8-0.sprintlink.net [144.232.7.13]
7 54 ms 94 ms 88 ms 144.232.8.50
8 59 ms 77 ms 153 ms tbr2031701.n54ny.ip.att.net [12.122.80.238]
9 144 ms 129 ms 83 ms gbr5-p40.n54ny.ip.att.net [12.122.11.26]
10 55 ms 81 ms 77 ms 12.123.214.57
11 98 ms 73 ms 72 ms 12.126.221.90
12 68 ms 75 ms 68 ms 12.110.110.132


CIA.GOV



2 35 ms 36 ms 36 ms 207.42.20.1
3 37 ms 37 ms 36 ms 192.168.1.1
4 62 ms 65 ms 55 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 56 ms 55 ms 149 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
6 54 ms 55 ms 67 ms sl-bb20-nyc-8-0.sprintlink.net [144.232.7.13]
7 61 ms 79 ms 123 ms 0.so-0-0-3.BR2.NYC4.ALTER.NET [204.255.169.121]

8 160 ms 102 ms 63 ms 0.ge-5-1-0.XL3.NYC4.ALTER.NET [152.63.3.125]
9 74 ms 69 ms 88 ms 0.so-4-0-2.XL1.RDU1.ALTER.NET [152.63.27.57]
10 130 ms 69 ms 68 ms 123.ATM7-0.GW6.RDU1.ALTER.NET [152.63.38.221]
11 94 ms 87 ms 94 ms res2rdu1-gw.customer.alter.net [157.130.85.234]


WHITEHOUSE.GOV



2 36 ms 35 ms 36 ms 207.42.20.1
3 36 ms 36 ms 36 ms 192.168.1.1
4 52 ms 54 ms 53 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 62 ms 55 ms 82 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
6 59 ms 62 ms 65 ms sl-bb21-nyc-8-0.sprintlink.net [144.232.7.110]
7 65 ms 66 ms 73 ms sl-bb26-pen-4-0-0.sprintlink.net [144.232.20.142
]
8 65 ms 57 ms 58 ms sl-bb21-pen-9-0.sprintlink.net [144.232.5.245]
9 60 ms 61 ms 61 ms sl-bb23-rly-0-0.sprintlink.net [144.232.20.32]
10 60 ms 61 ms 62 ms sl-gw19-rly-10-0.sprintlink.net [144.232.14.42]

11 63 ms 62 ms 62 ms sl-fema-1-0.sprintlink.net [144.232.184.78]
12 96 ms 70 ms 82 ms 205.160.212.222


FEMA.GOV



2 36 ms 36 ms 36 ms 207.42.20.1
3 36 ms 37 ms 37 ms 192.168.1.1
4 53 ms 58 ms 54 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 73 ms 58 ms 68 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
6 55 ms 56 ms 55 ms sl-bb27-nyc-11-0.sprintlink.net [144.232.13.13]

7 54 ms 54 ms 58 ms sl-bb26-nyc-8-0.sprintlink.net [144.232.7.37]
8 54 ms 55 ms 55 ms so-1-0-0.gar3.NewYork1.Level3.net [4.68.127.185]

9 60 ms 57 ms 60 ms ae-1-55.bbr1.NewYork1.Level3.net [4.68.97.129]
10 60 ms 61 ms 69 ms as-3-0.bbr2.Washington1.Level3.net [4.68.128.206
]
11 62 ms 74 ms 62 ms ge-8-1.hsa1.Washington1.Level3.net [4.68.121.105
]


RENSE.COM



2 36 ms 35 ms 35 ms 207.42.20.1
3 37 ms 37 ms 37 ms 192.168.1.1
4 53 ms 55 ms 53 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 55 ms 56 ms 75 ms sl-bb24-nyc-15-0.sprintlink.net [144.232.7.25]
6 93 ms 106 ms 111 ms sl-bb27-nyc-10-0.sprintlink.net [144.232.13.174]

7 80 ms 63 ms 74 ms sl-bb26-nyc-8-0.sprintlink.net [144.232.7.37]
8 54 ms 73 ms 112 ms so-1-0-0.gar3.NewYork1.Level3.net [4.68.127.185]

9 75 ms * 55 ms ae-31-53.ebr1.NewYork1.Level3.net [4.68.97.94]
10 * 82 ms 135 ms ae-3.ebr2.Washington1.Level3.net [4.69.132.93]
11 104 ms * 78 ms ae-1.ebr1.Washington1.Level3.net [4.69.132.29]
12 * 112 ms 86 ms ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
13 105 ms * 116 ms ae-1.ebr2.Dallas1.Level3.net [4.69.132.46]
14 137 ms 312 ms 174 ms ae-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
15 127 ms 134 ms 152 ms ae-1.ebr1.LosAngeles1.Level3.net [4.69.132.5]
16 156 ms 135 ms 145 ms ae-1.ebr1.LosAngeles1.Level3.net [4.69.132.5]
17 173 ms 127 ms 146 ms unknown.Level3.net [63.209.82.190]
18 131 ms 129 ms 130 ms mail.adminsites.com [216.240.137.183]


ABOVETOPSECRET.COM



2 35 ms 36 ms 36 ms 207.42.20.1
3 36 ms 37 ms 37 ms 192.168.1.1
4 52 ms 53 ms 53 ms sl-gw27-nyc-5-3-TS9.sprintlink.net [144.223.28.2
33]
5 80 ms 79 ms 138 ms sl-bb23-nyc-15-1.sprintlink.net [144.232.7.21]
6 185 ms 175 ms 116 ms sl-bb20-nyc-8-0.sprintlink.net [144.232.7.13]
7 55 ms 54 ms 55 ms 144.232.8.50
8 101 ms 106 ms 101 ms tbr2033001.n54ny.ip.att.net [12.123.0.102]
9 123 ms 117 ms 120 ms tbr2-cl15.wswdc.ip.att.net [12.122.10.54]
10 147 ms 110 ms 105 ms tbr1-cl27.wswdc.ip.att.net [12.122.9.149]
11 154 ms 126 ms 101 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
12 106 ms 110 ms 115 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
13 97 ms 102 ms 106 ms gar1-p3100.dlrtx.ip.att.net [12.123.16.165]
14 174 ms 95 ms 124 ms 12.119.136.18
15 102 ms 98 ms 97 ms vl32.dsr02.dllstx3.theplanet.com [70.85.127.62]

16 97 ms 101 ms 102 ms vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]

17 100 ms 99 ms 98 ms vl1.car02.dllstx6.theplanet.com [12.96.160.23]
18 125 ms 119 ms 105 ms b4.25.344a.static.theplanet.com [74.52.37.180]



posted on Jul, 4 2006 @ 10:38 PM
link   
wow it took me a while to figure out how to do this under osx network unility's. i kept typing # traceroute nsa.gov instead of just nsa.gov

Here is what i came up with

Traceroute has started ...

traceroute to nsa.gov (12.110.110.204), 64 hops max, 40 byte packets
1 * * *
2 1.062.dsl.syd.iprimus.net.au (211.27.252.1) 31.528 ms 29.914 ms 29.786 ms
3 atm3-64.ac02.syd.iprimus.net.au (192.168.63.218) 32.635 ms 32.249 ms 31.181 ms
4 vlan5.sw01.syd.iprimus.net.au (210.50.143.129) 43.017 ms 32.827 ms 29.593 ms
5 ge1-0-0.br01.syd.iprimus.net.au (203.134.2.170) 63.931 ms 30.291 ms 32.835 ms
6 p1-7.cr2-sjc.primustel.com (209.227.129.225) 188.098 ms 189.164 ms 186.924 ms
7 ge4-2.pr1-sjc.primustel.com (209.227.129.193) 185.893 ms 184.876 ms 183.914 ms
8 p3-0.pr1-paix.primustel.com (209.227.129.41) 186.881 ms 187.037 ms 187.133 ms
9 12.118.116.45 (12.118.116.45) 190.090 ms 192.454 ms 195.777 ms
10 tbr2-p014002.sffca.ip.att.net (12.123.12.134) 254.265 ms 252.019 ms 292.200 ms
11 tbr1-cl2.sl9mo.ip.att.net (12.122.10.41) 251.939 ms 253.119 ms 250.733 ms
12 tbr1-cl4.wswdc.ip.att.net (12.122.10.29) 251.897 ms 255.255 ms 250.548 ms
13 ar2-a3120s6.wswdc.ip.att.net (12.123.8.65) 294.449 ms 337.938 ms 459.491 ms
14 12.127.209.218 (12.127.209.218) 259.329 ms 258.146 ms 269.853 ms
15 12.110.110.131 (12.110.110.131) 258.263 ms 272.451 ms 259.074 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * *

Line 10 looks kinda suspect dont you think? So does anyone have any feedback on my readings. Also has anyone ever used peerguradian osx on the mac.

[edit on 4-7-2006 by tarzan]

[edit on 5-7-2006 by tarzan]



posted on Jul, 4 2006 @ 11:10 PM
link   
Ok,

I've been networking for a long time now, so hopefully I can clear up some possible questions you guys might be wondering.

First off, all my friends here in southern california who have cox.net are not, according to Mr. Klein (sp?) being spied upon by the NSA. *whew*

Your results with traceroute will vary, especially depending on server(s) load and network traffic. Modern bandwithd providers (such as ATT, qwest, Level 3, etc) use load balancing and multiple "routes" along their networks to balance network congestion and provide redundancy incase any of their equipment should fail.

Thus your results might very well vary depending upon all of the above mentioned factors. My suggestion, assuming Mr. Klein is correct - is to periodically check your traceroute and see if and/or when the NSA could be spying on your information.

And as previously posted, unless your network traffic is encrypted, it doesn't matter what kind of "software firewall" you use - the NSA can store and read your information. Technically, the NSA could concievably recieve EVERYTHING you send out over the internet (encrypted or not) but all the encrypted information would take a considerable amount of processing power to un-encrypt.



posted on Jul, 4 2006 @ 11:42 PM
link   
I just ran trace route again inserting aljazeera.net

Unlike other runs as posted above, I was pinged twice.

I blocked the pings on my NetBarrier stop list.

For your own protection, it's best to use a personal firewall behind a router.

P/C users that use public P2P servers may want to try using PeerGuardian.

Personally, I stay away from P2P altogether.

As far as NSA and AT&T

It seems much more likely that you would be flagged for visiting a known militant web page
than you would be for a normal .gov web page.



posted on Jul, 5 2006 @ 03:13 AM
link   
Can anyone tell me if I'm alright?

1 22 ms 4 ms 9 ms mygateway [10.1.1.1]
2 48 ms 19 ms 19 ms nme-pow-ibo-tit-2-loo-20.tpgi.com.au [202.7.162.
174]
3 42 ms 23 ms 30 ms nme-pow-ibo-cup-1.tpgi.com.au [202.7.176.209]
4 52 ms 29 ms 22 ms nme-pow-ibo-zeu-1-ge-2-2.tpgi.com.au [202.7.176.
197]
5 61 ms 38 ms 39 ms vlan350.o3mlc76f05.optus.net.au [59.154.11.25]
6 211 ms 207 ms 199 ms 203.208.148.69
7 204 ms 210 ms 204 ms 12.118.42.17
8 266 ms 281 ms 274 ms tbr2-p012901.la2ca.ip.att.net [12.123.222.70]
9 291 ms 276 ms 277 ms tbr2-cl21.sl9mo.ip.att.net [12.122.10.13]
10 389 ms 270 ms 289 ms tbr1-cl24.sl9mo.ip.att.net [12.122.9.141]
11 270 ms 279 ms 278 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
12 267 ms 267 ms 269 ms ar2-a3120s6.wswdc.ip.att.net [12.123.8.65]
13 277 ms 277 ms 273 ms 12.127.209.214
14 275 ms 280 ms 275 ms 12.110.110.131



posted on Jul, 5 2006 @ 03:23 AM
link   
Nventual

I don't see the "magic string" anywhere at all in your trace route.

So I'd say you're safe....for now.



posted on Jul, 5 2006 @ 04:04 AM
link   
Firstly, in reply to Hyacinth,

I'm also in the UK. I haven't bothered doing this because I think it's safe to assume that pretty much everything is monitored, particularly transatlantic traffic. In the past I've also deliberately littered my emails - which are all innocuous, obviously - with a string of keywords followed by a rude message to the watchers.

Anywayyyyy.... the string that caught my eye in your tracert dump was the "bletchley" one: now I don't know what that means specifically, but I do know that bletchley was the MoD site for codebreaking and related activities since WWII. Whether that string has anything to do with it I don't know but it's not an especially good indicator IMO.

On a more general level, many posters here are wondering, why is the government watching? I started this thread because I found a rather interesting article that uses statistical analysis to demonstrate that data mining is useless against terrorists but rather good for surveilling domestic dissent.

You can find the article here.


The whole NSA domestic spying program will seem to work well, will seem logical and possible, if you are paranoid. Instead of presuming there are 1,000 terrorists in the USA, presume there are 1 million terrorists. Americans have gone paranoid before, for example, during the McCarthyism era of the 1950s. Imagining a million terrorists in America puts the base-rate at .00333, and now the probability that a person is a terrorist given that NSA's system identifies them is p=.99, which is near certainty. But only if you are paranoid. If NSA's surveillance requires a presumption of a million terrorists, and if in fact there are only 100 or only 10, then a lot of innocent people are going to be misidentified and confidently mislabeled as terrorists.

The ratio of real terrorists to innocent people in the prison camps of Guantanamo, Abu Ghraib, and Kandahar shows that the US is paranoid and is not bothered by mistaken identifications of innocent people. The ratio of real terrorists to innocent people on Bush's no-fly lists shows that the Bush administration is not bothered by mistaken identifications of innocent Americans.

Also, mass surveillance of the entire population is logically plausible if NSA's domestic spying is not looking for terrorists, but looking for something else, something that is not so rare as terrorists. For example, the May 19 Fox News opinion poll of 900 registered voters found that 30% dislike the Bush administration so much they want him impeached. If NSA were monitoring email and phone calls to identify pro-impeachment people, and if the accuracy rate were .90 and the error rate were .01, then the probability that people are pro-impeachment given that NSA surveillance system identified them as such, would be p=.98, which is coming close to certainty (p_1.00). Mass surveillance by NSA of all Americans' phone calls and emails would be very effective for domestic political intelligence.



posted on Jul, 5 2006 @ 05:10 AM
link   

Originally posted by Indy
This is an incorrect way to check for NSA snooping. If NSA has at&t for their backbone ANY trace to them will show that. Because your package of data has to go through at&t to get to the nsa.com server. Try running a tracert to some off the wall domains to see if at&t shows up in all of them. If you are being monitored all your nslooks to every domain will reference at&t.


This quote is correct.. this is DISINFO from the Original Poster. Trace Route traces the hops a ping takes to a certain location. If you Trace Route to NSA.GOV (who uses ATT as a ISP) of COURSE your going to see ATT on EVERY trace. The ping on trace route has to go to ATT in order to reach the NSA. The reason some people get the "special string" and others don't, is because if you are from a different area, a different ATT ISP location will take control of the connection in order to reach the NSA.


This is disinfo.

[edit on 5-7-2006 by LAES YVAN]



posted on Jul, 5 2006 @ 05:13 AM
link   
oh man i think im gonna stop dlin....."moving pictures" and "war pc entertainment" and stop visiting certain sites....i already knew i was on the fed watchlist cause i have a terrorist charge.....but now i found that the NSA is watchin me too....
grrrr




top topics



 
14
<< 1  2  3    5  6  7 >>

log in

join