Google Hacking – Using “Google Dorks”


This article is about Google hacking with the help of the dorks, I’m sure after reading this you will thank me for the particular info which I am going to provide you. The best part is you cannot be traced! Those who are new to the phase “Google Dorks” let me give you an introduction to Google search engine and Google dorks. Google is the most used search engine in this world because of it’s most efficient response.  Google has some bots which crawl all over the net and copy almost all content available on databases to Google’s database. Therefore, it gives you the response when you type a word on Google search, it just checks its database and gives the response as you desire!

For making response more efficient Google has provided few functional words called dorks. Here is an example of how a dork looks like: “site:“. This particular is used for finding out the websites with a particular word in their domain name. Such as if you search in Google as  ”site: uk” you will find the sites which belong to United Kingdom (U.K.) only! This makes your search response very accurate when you are searching something, especially related to a country.

Suppose you want to find some information regarding a site then you have the dork “”. Just replace the by the site whose information you need to know! And the most good thing is you can use several dorks at a time to make your result even more accurate.

You might be wondering why have I called this article as Google hacking when this a just a simple technique to make the Google response accurate. Actually you know the answer, I have told you in the starting itself…. Yes the Google bots I’m talking about! What happens here is the Google bots copy almost everything available on internet, that is they even copy sensitive information like usernames, passwords and credit cards numbers etc…

And other shocking thing is that you can also access unsecured webcams using Google dorks!

Isn’t that what you actually looking for?

So now you will definitely ask me how to get them?

The answer is dorks, we are going to use some best dorks available and extract the sensitive juicy info from the Google’s database.

Here are few examples of dorks with explanation which will help you finding some sensitive info:

Dorks for finding usernames and passwords:

auth_user_file.txt                                                        Gives you list of crackable passwords

“login: *” “password: *” filetype: xls                   Gives passwords file in saved in excel

filetype:log inurl:”password .log”                        Clear text password files

Dorks for finding Credit cards:

“ATM PIN” ReZult                                                          Credit card dumps by phishers

Dorks for MYSQL dumps:

?intitle:index.of?”.mysql_history                        Gets you the MySQL  history files

Input validation vulnerabilities:

intext:”Powered by X-Cart: shopping cart software”

These were just simple dorks which will get you some juicy info, but there are thousands more which will give you access to very confidential data.


7 thoughts on “Google Hacking – Using “Google Dorks”

  1. Pingback: micro jobs online

  2. The article provides established beneficial to me personally.
    It’s quite educational and you’re naturally very experienced in this field. You have got exposed my own eye to be able to numerous thoughts about this subject matter together with intriquing, notable and sound written content.

  3. I simply want to tell you that I’m beginner to blogs and truly loved you’re web blog. More than likely I’m going to bookmark your blog . You absolutely have incredible posts. Thank you for sharing your web-site.

  4. After I initially left a comment I appear to have clicked on the -Notify me when new comments are added- checkbox and from now on whenever a comment is added I get 4 emails with the same comment. Perhaps there is a means you are able to remove me from that service? Appreciate it!

  5. An air taxi crashed at the Soldotna Municipal Airport on Sunday morning, killing all 10 people onboard in the worst aviation accident in Alaska in more than a decade.
    The de Havilland DHC-3 Otter airplane crashed at 11:20 a.m. at the Soldotna Airport, according to the Alaska State Troopers and Soldotna Police Department.
    The plane was operated by Rediske Air, according to the Federal Aviation Administration.
    The National Transportation Safety Board described the flight as an air taxi, but on Sunday evening was still trying to confirm who was onboard and where they were going.
    The NTSB’s Clint Johnson said an initial report from someone at the small airport indicated the plane was taking off.
    The person saw the plane taxiing out for takeoff but didn’t see any actual takeoff attempt.
    “The next thing they knew is they saw it on fire, unfortunately, after the accident,” Johnson said. The investigation is still in early stages and nothing is confirmed about what went wrong, he said.
    The Soldotna Airport is a municipal airstrip with a single paved 5,000-foot long runway adjacent to the Kenai River. The airport is busy in the summer months with fishing, hunting and sight-seeing flights that take off from the Kenai Peninsula town.
    Fire crews got the call for help at 11:24 a.m. and were the first to get to the burning plane, said Capt. Lesley Quelland of Central Emergency Services, which handles fire and medic calls from Cooper Landing to Clam Gulch.
    “We saw the plume immediately when we left the station,” Quelland said Sunday evening. It was a big, black cloud of smoke visible from the station, about three driving miles from the airport, she said. Campers at the nearby Klondike RV Park also saw smoke, owner Al Belknap said.
    When fire crews got to the airport about [url=]Dodgers 16 Andre Ethier Road Cool Base Grey 2010 All Star Jerseys[/url] 11:30 a.m., “the aircraft was crashed off the side of the runway and it was fully involved in flames,” she said.
    It took crews about 10 minutes to put out the fire and look for survivors. There were none, and no one made it out. Everyone died inside the plane, she said.
    Quelland said she knows of no eyewitnesses to the crash.
    Names of the crash victims have not yet been released, pending positive identification of their bodies by the state medical examiner and notification of their next-of-kin, said the Soldotna Police Department.
    The pilot was Walter Rediske, said Andrew Harcombe, who identified himself as a spokesman for Rediske Air. Public records list Rediske’s age as 42.
    Rediske Air is a family-owned business on the Kenai Peninsula that offers air charter services, Harcombe said.
    The company is registered to Lyla and Walter Rediske, with an address in Nikiski, according to the state’s Division of Corporations, Business and Professional Licensing. It was formed in 1991.
    Harcombe said Rediske was a “highly experienced” pilot and lifelong Alaskan.
    The de Havilland DHC-3 Otter airplane had a single turbo-prop engine and was manufactured in 1958, according to FAA records.
    The cause of the crash has not been determined. The weather was reported to be cloudy with a light wind at the time of the crash, troopers said.
    Much of the plane burned, said Johnson, the head of the NTSB’s Anchorage office.
    NTSB investigator Chris Shaver was at the scene looking for witnesses and clues, Johnson said.
    A national NTSB “go-team” was on its way to Alaska on Sunday night to investigate the crash because of the number of fatalities, he said. A team of at least eight people from Washington, D.C., will handle the investigation, led by accident investigator Dan Brower.
    The crash is one of the deadliest in decades in a state with many fatal aviation accidents.
    In 2001, a Peninsula Airways commuter plane bound for King Salmon crashed in Dillingham, killing all 10 people aboard.
    In 1987, a Beechcraft 1900C Ryan Air flight crashed in Homer, killing 18 people.
    The last major crash at the Soldotna airport was in 1985, when a North Pacific Air Beechcraft 65-A80 crashed, killing nine.
    Some notable Alaska plane crashes
    July 7, 2013 — Rediske Air de Havilland DHC-3 Otter crashed at Soldotna Airport, killing 10
    Aug. 9, 2010 — GCI-registered de Havilland DHC-3T Otter crashed in Southwest Alaska, killing 5 people including Alaska Sen. Ted Stevens
    Oct. 10, 2001– Peninsula Airways Cessna 208 Caravan commuter plane crashed shortly after takeoff from Dillingham, killing 10
    July 30, 2001– LAB Flying Service Piper PA-32-300 crashes at Haines, killing 6
    Feb. 5, 2000– Iliamna Air Cessna [url=]Cardinals 29 Chris Carpenter Road Cool Base Grey 2010 All Star Jerseys[/url] U206G crashes at Iliamna, killing 6
    Dec. 7, 1999– Grant Aviation Cessna 207 crashed at Nightmute, killing 6
    Nov. 8, 1997– Hageland Aviation Cessna 208B crashed at Barrow, killing 8
    Sept. 22, 1995–Air Force E3B AWACS crashed at Elmendorf AFB, killing 24
    Jun. 22, 1994– Wings of Alaska DeHavilland DHC-3 crashed at Juneau, killing 7
    Nov. 12, 1992– Alaska National Guard C-12F Beechcraft crashed near Juneau, killing 8
    Dec. 23, 1987– Southcentral Air Piper PA-31 crashed in Kenai, killing 6
    Nov. 23, 1987– Ryan Air Beechcraft 1900C crashes in Homer, killing 18
    Aug. 25, 1985– Flightseeing Cessna 180H and Piper J5A spotting sheep collided near Knik Glacier, killing 12
    Feb. 4, 1985– North Pacific Air Beechcraft 65-A80 crashes in Soldotna, killing 9
    A previous version of this article mistakenly said that the 2001 Peninsula Airways crash killed 9 people. It killed all 10 people aboard. It also mistakenly said that a 1999 Grant Aviation crash occurred in Bethel. It occurred near Nightmute.

    Reach Michelle Theriault Boots ator 257-4344. Reach Lisa Demer ator 257-4390.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s