My website got blocked by TMNET/Security Commision ?

[karhoe]

My website, hosted at http://karhoe.byethost33.com seems to be down. At first I thought it was down.

Then I contacted my host, and they told me they are able to access the website. I tried using international proxy server and I manage to access my website.

I can access my hosting control panel which is at htp://cpanel.byethost33.com (without proxy). But I cannot access the FTP and the website itself.

I did some google to find other website hosted at byethost33.com , and I cannot access any at all.

My question is, is this a DNS error with their server, or they ban my website ( or my domain ) ?

I won't want to email TMNET because their reply would be pure copy and paste, and they have no idea what is DNS.

I also did some google with the word byethost33 and HYIP and I do see some HYIP sites hosted on the free server.

Could it be that the SC is trying to ban the HYIP sites, but they just banned the entire server?

I tried accesing the IP address directly, hence I do not need to go through the DNS, and still it failed.

I also posted my problem in another forum, and some of them using Maxis, UK broadband, Pacific Internet broadband are able to access. But, Jaring broadband also can't access the site.

What could be the problem?

Thanks

[zy]

it could be DNS problem.

[Adrian Wong]

Most likely DNS cache problem. Try this :

1. Ask those who can access it to ping the domain, see what IP they are getting.

2. Ping the domain on your end and compare the IPs.

Can you post the tracert?

[karhoe]

Tracing route to karhoe.byethost33.com [209.51.196.242] with 32 bytes of data
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 131 ms 149 ms 199 ms 192.168.0.1
3 31 ms 105 ms 169 ms 219.93.218.177
4 23 ms 17 ms 18 ms 219.93.216.133
5 192 ms 159 ms 107 ms 210.187.132.81
6 113 ms 236 ms 431 ms 219.94.12.141
7 212 ms 214 ms 331 ms 210.187.143.1
8 169 ms 231 ms 244 ms 210.187.141.30
9 * * * Request timed out.
10 * * * Request timed out.
11 * *

This is what I got, what about the rest of you who can access ?

[Dashken]

Ermm...

Pinging karhoe.byethost33.com [209.51.196.242] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.51.196.242:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[karhoe]

I did an online tracert using Singapore Pacific Internet trace route tool, it worked, same IP

Time of Capture : 17:43:14 on 25/07/2007
The Address entered : http://karhoe.byethost33.com
Traceroute Type Selected : TCP Traceroute
Port Nos Selected : HTTP


Entered Name is equivalent to :
IP Address : 209.51.196.242
TRACEROUTE Result for : 209.51.196.242

1 scipk005-vl1.pacific.net.sg (203.120.90.5) 0.257 ms 0.222 ms 0.213 ms
2 scipk007.pacific.net.sg (203.120.91.7) 0.336 ms 0.341 ms 0.323 ms
3 scipk004-vl12.pacific.net.sg (203.120.91.132) 0.378 ms 0.371 ms 0.451 ms
4 203.208.143.29 (203.208.143.29) 0.572 ms 0.588 ms 0.603 ms
5 ge-4-0-1-0.sngc3-cr2.ix.singtel.com (203.208.172.165) 0.541 ms 0.451 ms 0.453 ms
6 203.208.182.134 (203.208.182.134) 193.382 ms 193.476 ms 193.720 ms
7 ge-2-1-2-0.laxow-dr1.ix.singtel.com (203.208.171.42) 203.862 ms 203.452 ms 203.531 ms
8 * * *
9 64.209.101.122 (64.209.101.122) 243.841 ms 243.571 ms 243.466 ms
10 GIG5-2-CISCO-ONE-XLHOST.xlhost.com (206.222.25.18) 260.568 ms 260.534 ms 260.627 ms
11 Gig-E-1.demarc.byethost.com (206.222.7.10) 246.133 ms 245.590 ms 246.322 ms
12 209.51.196.242 (209.51.196.242) [open] 244.218 ms 244.227 ms 244.533 ms

Compared to trace route via TMNET

Tracing route to karhoe.byethost33.com [209.51.196.242]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 192.168.0.1
3 33 ms 49 ms 59 ms 219.93.218.177
4 456 ms 190 ms 118 ms 219.93.216.133
5 16 ms 18 ms 17 ms 210.187.133.82
6 18 ms 17 ms 48 ms 219.94.12.141
7 22 ms 70 ms 60 ms 210.187.143.1
8 18 ms 17 ms 17 ms 210.187.141.30
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * *

So, it worked on other ISP, with the same destination IP, which means that the DNS is perfectly alright

[Adrian Wong]

Hmm.. Looks like the last relay is a TMNet server. The connection was lost after that.

[bug]

Hop IP Address Host Name Sent Recv RTT Av RTT Min RTT Max RTT % Loss

1 *.*.*.* launchmodem 1 1 0ms 0ms 0ms 0ms 0%
2 *.*.*.* [Unknown] 1 1 24ms 24ms 24ms 24ms 0%
3 *.*.*.* [Unknown] 1 1 30ms 30ms 30ms 30ms 0%
4 65.83.239.128 ixc01jax-pos-5-0-0.bellsouth.net 1 1 36ms 36ms 36ms 36ms 0%
5 205.152.187.64 ixc00jax-ge-0-0-0.bellsouth.net 1 1 36ms 36ms 36ms 36ms 0%
6 65.83.239.74 axr00asm-so-2-0-0.bellsouth.net 1 1 45ms 45ms 45ms 45ms 0%
7 65.83.236.9 axr01asm-ge-5-0-0.bellsouth.net 1 1 34ms 34ms 34ms 34ms 0%
8 65.83.238.38 axr00aep-so-1-0-0.bellsouth.net 1 1 43ms 43ms 43ms 43ms 0%
9 65.83.238.37 axr01aep-ge-5-1-0.bellsouth.net 1 1 44ms 44ms 44ms 44ms 0%
10 65.83.236.192 xer00lax-so-0-1-0.bellsouth.net 1 1 42ms 42ms 42ms 42ms 0%
11 64.215.195.237 ge3-27-1000M.ar1.ATL2.gblx.net 1 1 55ms 55ms 55ms 55ms 0%
12 64.209.101.122 [Unknown] 1 1 64ms 64ms 64ms 64ms 0%
13 64.209.101.122 [Unknown] 1 1 83ms 83ms 83ms 83ms 0%
14 206.222.7.10 Gig-E-1.demarc.byethost.com 1 1 64ms 64ms 64ms 64ms 0%
15 --- [No response] --- --- --- --- --- --- ---
16 --- [No response] --- --- --- --- --- --- ---
17 --- [No response] --- --- --- --- --- --- ---
18 --- [No response] --- --- --- --- --- --- ---

[zy]

1 1 ms <1 ms 1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 73.216.40.1
3 6 ms 8 ms 6 ms ge-2-18-ur01.lowell.ma.boston.comcast.net [68.87.155.237]
4 8 ms 8 ms 10 ms po-21-ar01.needham.ma.boston.comcast.net [68.87.144.157]
5 13 ms 13 ms 10 ms po-10-ar01.springfield.ma.boston.comcast.net [68.87.146.22]
6 21 ms 16 ms 13 ms po-11-ar01.chartford.ct.hartford.comcast.net [68.87.146.26]
7 * 17 ms * 68.86.90.69
8 14 ms 15 ms 15 ms 64.215.24.85
9 29 ms 29 ms 28 ms 64.209.101.122
10 41 ms 29 ms 28 ms GIG5-2-CISCO-ONE-XLHOST.xlhost.com [206.222.25.18]
11 33 ms 30 ms 29 ms Gig-E-1.demarc.byethost.com [206.222.7.10]
12 * * * Request timed out.

[Adrian Wong]

Hmm... Looks like the last server is a byethost.com server. If so, it can't be filtering by our government.