So you claim to have discovered the sooper sekrit "hosting" IP by performing a
traceroute? And you claim the hosting IP is 218.30.19.227.

Do you understand how a traceroute to a domain name works?

You posted:

::Wrong AGAIN, dufus!   :(

::Tracert to jngegjlmgk.info

::Generated at 15:26:39 GMT on 24 Jan 2005.

::10 467 ms 477 ms 486 ms 202.97.37.50  [Missing reverse DNS entry] 245
::CHINA Unix: 15:26:42.277
::11 507 ms 527 ms 533 ms 202.97.34.50  [Missing reverse DNS entry] 244
::CHINA Unix: 15:26:43. 30
::12 513 ms 524 ms 533 ms 218.30.19.242  [Missing reverse DNS entry] 243
::CHINA Unix: 15:33:48.575
::13 510 ms 456 ms 469 ms 218.30.19.227  [Missing reverse DNS entry] 241
::CHINA Unix: 15:33:49. 57

::218.30.19.227

Again I note you carefully, or stupidly, snipped the IP your tracert resolved
FROM DNS. Why is that?

For the traceroute to work, the domain name must be resolved to an IP address
(and of course ARP to get the MAC, but that is another matter). Do you know
where the IP address comes from?

DNS!!!

Bwaaaaahahahaha!

So you claim your traceroute was NOT performed to an IP obtained from DNS, but
some mysterious "hosting" IP service, or that someone (perhaps spammy playing
"tricjs") has re-written networking protocols the world over that allows you to
traceroute to a host name without resolving it to an IP address.

In addition to this technical lunacy, you got the "hosting" IP wrong. Show the
web page hosted at the IP you claim is the "hosting" IP (218.30.19.227).

Try these:
http://www.jngegjlmgk.info/
http://jngegjlmgk.info/
http://218.30.21.67/

You get the same page at each of those.

Now try this: http://218.30.19.227/
You get nothing. Why? Because this *router* is not a "hosting" server.

Go to traceroute.org and see if you can identify what is running at
218.30.19.227. I'll bet you anything it aint "hosting" any web sites.

--
--

Paging Snotty Richter, please pick up the red "You're Fucked Now" phone.
Keep the Internet clean, practise spammus interruptus