http://www.gigaom.com/2005/05/07/google-hacked/
http://www.engadget.com/entry/1234000610042620/

Ne razumem. Cilj teme je bio da se vidi kakav ljudi imaju ping ka google

evo

Google nije bio dostupan par minuta. Prica se da je hakovan
http://www.gigaom.com/2005/05/07/google-hacked/

Google shuts down for 15 minutes
Associated Press

MOUNTAIN VIEW, Calif. - Googling stopped for 15 minutes on Saturday.

The world's leading internet search engine shut down from 6:45 to 7 p.m. eastern time, according to Google spokesman David Krane.

"It was not a hacking or a security issue," said Krane. He said the problem was related to the DNS, or Domain Name System, though Krane did not elaborate. The DNS translates domain names for computers.

"Google's global properties were unavailable for a short period of time," Krane said. "We've remedied the problem and access to Google has been restored worldwide."

On Wednesday, the company, based in Mountain View, launched its Web Accelerator service. It's intended to speed access to Web pages by offering cached or compressed copies of sites from Google's servers.

There are an estimated 200 million Google searches a day.

Meni malopre izadje ovo (pogledaj attachment) kad sam pokusao da trazim nesto... Jel se desilo slicno jos nekom, posto zaista sumnjam da sam inficiran nekim virusom?!

Sezam

Sigurnosni strucnjaci upozoravaju na novu opasnost koja prieti onima koji slucajno pogrešno ukucaju Googleovu adresu.

Nenamerni posetilac stranica koje se nalaze na adresi www.googkle.com bice bombardovan svim vrstama zlocudnih programa, poput trojanskih konja, spyware-ova i pokušaja iskorišcavanja raznih sigurnosnih propusta.

Obzirom da na vecini tastatura slova k i l stoje jedno do drugog, ocekuje se da bi broj onih koji slucajno pritisnu oba tastera prilikom upisivanje Google-ove adrese mogao biti relativno veliki.

Stoga sigurnosni strucnjaci posebno upozoravaju na ovu stranicu, iako na Internetu postoji mnoštvo jednako ili cak više zlocudnih stranica.

Za sada nema komentara iz Google-a na ove informacije, no u prošlosti su obicno veliki portali na Internetu štitili svoje korisnike od ovakvih propusta jednostavno preusmjeravajuci korisnike na prave stranice.

________

O tome vam pricam...

A evo i mog pingovanja....

[att_img]

meni googkle.com ne radi :)

djordje se ispravio prvo je napisao google.net :)

aha, ali nema veze, isti djavo

Upomoć, nestao googkle ;)

Wireless 100k

Ovo je Sezam ADSL@256

C:\>ping www.google.com

Pinging www.l.google.com [66.249.85.99] with 32 bytes

Reply from 66.249.85.99: bytes=32 time=58ms TTL=248
Reply from 66.249.85.99: bytes=32 time=56ms TTL=248
Reply from 66.249.85.99: bytes=32 time=57ms TTL=248
Reply from 66.249.85.99: bytes=32 time=60ms TTL=248

Ping statistics for 66.249.85.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 60ms, Average = 57ms

C:\>ping www.elitesecurity.org

Pinging www.elitesecurity.org [217.26.67.165] with 32

Reply from 217.26.67.165: bytes=32 time=180ms TTL=53
Reply from 217.26.67.165: bytes=32 time=191ms TTL=53
Reply from 217.26.67.165: bytes=32 time=198ms TTL=53
Reply from 217.26.67.165: bytes=32 time=179ms TTL=53

Ping statistics for 217.26.67.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 198ms, Average = 187ms

Modem, 042 210 110
--------------------------------------------------------------
Google
C:\DOCUME~1\ADMINI~1.UFO>ping www.google.com

Pinging www.l.google.com [66.102.9.104] with 32 bytes of data:

Reply from 66.102.9.104: bytes=32 time=201ms TTL=239
Reply from 66.102.9.104: bytes=32 time=189ms TTL=239
Reply from 66.102.9.104: bytes=32 time=185ms TTL=239
Reply from 66.102.9.104: bytes=32 time=177ms TTL=239

Ping statistics for 66.102.9.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 201ms, Average = 188ms
---------------------------------------------------------------
eS
C:\DOCUME~1\ADMINI~1.UFO>ping www.elitesecurity.org

Pinging www.elitesecurity.org [217.26.67.165] with 32 bytes of data:

Reply from 217.26.67.165: bytes=32 time=203ms TTL=51
Reply from 217.26.67.165: bytes=32 time=208ms TTL=51
Reply from 217.26.67.165: bytes=32 time=185ms TTL=51
Reply from 217.26.67.165: bytes=32 time=184ms TTL=51

Ping statistics for 217.26.67.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 208ms, Average = 195ms

aj kad ste navalili

[space@zwer /home\ $]ping -c5 www.google.com
PING www.l.google.com (66.249.85.104) 56(84) bytes of data.
64 bytes from 66.249.85.104: icmp_seq=1 ttl=247 time=30.1 ms
64 bytes from 66.249.85.104: icmp_seq=2 ttl=247 time=29.4 ms
64 bytes from 66.249.85.104: icmp_seq=3 ttl=247 time=30.5 ms
64 bytes from 66.249.85.104: icmp_seq=4 ttl=247 time=31.5 ms
64 bytes from 66.249.85.104: icmp_seq=5 ttl=247 time=32.5 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 29.450/30.842/32.515/1.091 ms

=========================================================
[space@zwer /home\ $]ping -c5 www.elitesecurity.org
PING www.elitesecurity.org (217.26.67.165) 56(84) bytes of data.
64 bytes from l33t.mafia.elitesecurity.org (217.26.67.165): icmp_seq=1 ttl=59 time=31.3 ms
64 bytes from l33t.mafia.elitesecurity.org (217.26.67.165): icmp_seq=2 ttl=59 time=10.0 ms
64 bytes from l33t.mafia.elitesecurity.org (217.26.67.165): icmp_seq=3 ttl=59 time=8.95 ms
64 bytes from l33t.mafia.elitesecurity.org (217.26.67.165): icmp_seq=4 ttl=59 time=7.96 ms
64 bytes from l33t.mafia.elitesecurity.org (217.26.67.165): icmp_seq=5 ttl=59 time=10.9 ms

--- www.elitesecurity.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 7.962/13.862/31.369/8.812 ms

kako vidim najbolji sam :)

Pinging www.l.google.com [66.249.85.104] with 32 bytes of data:

Reply from 66.249.85.104: bytes=32 time=1787ms TTL=240
Reply from 66.249.85.104: bytes=32 time=1156ms TTL=240
Reply from 66.249.85.104: bytes=32 time=1468ms TTL=240
Reply from 66.249.85.104: bytes=32 time=1672ms TTL=240

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1156ms, Maximum = 1787ms, Average = 1520ms




CUVENI Internet CG

56k modem


Pinging www.l.google.com [66.249.85.104] with 32 bytes of data

Reply from 66.249.85.104: bytes=32 time=174ms TTL=243
Reply from 66.249.85.104: bytes=32 time=170ms TTL=243
Reply from 66.249.85.104: bytes=32 time=190ms TTL=243
Reply from 66.249.85.104: bytes=32 time=180ms TTL=243

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 190ms, Average = 178ms

Radijus-vektor 64 kb

Pinging www.l.google.com [216.239.59.147] with 32 bytes of data:

Reply from 216.239.59.147: bytes=32 time=73ms TTL=234
Reply from 216.239.59.147: bytes=32 time=75ms TTL=234
Reply from 216.239.59.147: bytes=32 time=79ms TTL=234
Reply from 216.239.59.147: bytes=32 time=80ms TTL=234

Ping statistics for 216.239.59.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 80ms, Average = 76ms