[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-572767-105":53,"doc-detail-572767-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","google-dorks-collection-of-dorks","Google Dorks - collection of Dorks","","Google Dorks compiles a set of search “dorks” collected from Exploit-db, organized in a table with a title, the exact dork query, and a third description. The document explains what each dork is intended to find, ranging from benign cache and cluster reports to error pages, exposed documentation, and directory listings that can reveal sensitive information. It also discusses practical risks for attackers, including the exposure of intranet links and cached error details.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/google-dorks-collection-of-dorks/572767/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/google-dorks-collection-of-dorks/572767.png","ImageObject",442,249,{"name":88,"@type":89},"Jasmine","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-16","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What does the “Google Dorks” document contain?","Question",{"text":108,"@type":109},"It contains a collection of Google “dorks,” each listed with a title, the exact dork query, and a description of what the query is used to find.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How are the dorks organized in the document?",{"text":113,"@type":109},"They are presented in a table with three main columns: the dork title, the actual dork query, and a description that explains context and potential impact.",{"name":115,"@type":106,"acceptedAnswer":116},"Why does the document mention security risks and misuse?",{"text":117,"@type":109},"Because some dorks can help locate sensitive or internal information exposed via caches, error diagnostics, documentation pages, or directory listings, potentially enabling unauthorized access.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},572767,1792085640,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},2336478487870,"https://ap-avatar.wpscdn.com/davatar_085a072bc5b1113ac321206ff7593b45","Google Dorks  \nHere is a collection of Dorks Submitted to [Exploit-db.com. Collected](Exploit-db.com. Collected) on December 24, 2013 .  \nThis below tables shows the title of the dork, the actual dork that we use and third description of the dork. I copied raw data [from](from www.exploit-db.com. No changes)[ ](from www.exploit-db.com. No changes)[www.exploit-db.com](from www.exploit-db.com. No changes)[. No changes](from www.exploit-db.com. No changes) have done. You are free to use these dorks collection for any purpose.  \n\n| TITTLE | DORK | DESCRIPTION |\n| --- | --- | --- |\n| squid cache server reports | \"cacheserverreport for\" \"This analysis was produced by calamaris\" | These are squid server cache reports. Fairly benign, really except when you consider using them for evil purposes. For example, an institution stands up a proxy server for their internal users to get to the outside world. Then, the internal user surf all over to their hearts content (including intranet pages cuz well, the admins are stupid) Voila, intranet links show up in the external cache report. Want to make matters worse for yourself as an admin? OK, configure your external proxy server asa trusted internal host. Load up your web browser, set your proxy as their proxy and surf your way into their intranet. Not that I've noticed any examples of this in this google list.\u003Cbr>*COUGH* *COUGH* *COUGH* unresolved DNS lookups give clues *COUGH* *COUGH* ('scuse me. must be a furball) OK, lets say BEST CASE scenario. Let's say there's not security problems revealed in these logs. Best case scenario is that outsiders can see what your company/agency/workers are surfing. |\n| Ganglia Cluster Reports | intitle:\"Ganglia\" \"Cluster Report for\" | These are server cluster reports, great for info gathering. Lesse, what were those server names again? |\n| ICQ chat logs, please... | intitle:\"Index of\" dbconvert.exe chats | ICQ ([http://www.icq.com](http://www.icq.com)) allows you to store the contents of your online chats into a file. These folks have their |\n\n\n|  |  | entire ICQ directories online. On purpose? |\n| --- | --- | --- |\n| Apache online documentation | intitle:\"Apache [HTTP Server](HTTP Server)\"\u003Cbr>intitle:\"documentation\" | When you install the Apache web server, you get a nice set of online documentation. When you learn how to use Apache, your supposed to delete these online Apache manuals. These sites didn't. If they're in such a hurry with Apache installs, I wonder what else they rushed through? |\n| Coldfusion Error Pages | \"Error Diagnostic Information\"\u003Cbr>intitle:\"Error Occurred While\" | These aren't too horribly bad, but there are SO MANY of them. These sites got googlebotted while the site was having\"technical difficulties. \" The resulting cached error message gives lots of juicy tidbits about the target site. |\n| Financial spreadsheets:\u003Cbr>finance.xls | intitle:\"Index of\" finance.xls | \"Hey! I have a great idea! Let's put our finances on our website in a secret directory so we can get to it whenever we need to!\" |\n| Financial spreadsheets:\u003Cbr>finances.xls | intitle:index.of finances.xls | \"Hey! I have a great idea! Let's put our finances on our website in a secret directory so we can get to it whenever we need to!\" |\n| sQL data dumps | \"\\# Dumping data for table\" | sQL database dumps. LOTS ofdata in these. So much data, infact, I'm pressed to think of what else an ev1l hax0r would like to know about a target database.. What's that? Usernames and passwords you say? Patience, grasshopper..... |\n| bash_history files | intitle:index.of .bash_history | Ok, this file contains what a user typed at a shell command prompt. You shouldn't advertise this file. You shouldn't flash it to a web crawler. It contains COMMANDS and USERNAMES and stuff... *sigh* Sometimes there aren't words to describe how lame people can be. This particular theme can be carried further to find all sorts of things along these lines like .profile, .login, .logout files, etc. I just got bored ","cbCaie1BgyE3Dp8B","https://ap.wps.com/l/cbCaie1BgyE3Dp8B","pdf",2882412,476,"English","# Google Dorks\n## Dork collection overview\n## Dork table fields (title, dork, description)","[{\"question\":\"What does the “Google Dorks” document contain?\",\"answer\":\"It contains a collection of Google “dorks,” each listed with a title, the exact dork query, and a description of what the query is used to find.\"},{\"question\":\"How are the dorks organized in the document?\",\"answer\":\"They are presented in a table with three main columns: the dork title, the actual dork query, and a description that explains context and potential impact.\"},{\"question\":\"Why does the document mention security risks and misuse?\",\"answer\":\"Because some dorks can help locate sensitive or internal information exposed via caches, error diagnostics, documentation pages, or directory listings, potentially enabling unauthorized access.\"}]","Google Dorks - collection of Dorks | PDF",1791929190,167]