[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# User warnings\n=============\n\nIf you use Web Risk to warn users about risks from particular\nwebpages, the following guidelines apply.\n\nThese guidelines help protect both you and Google from misunderstandings by\nmaking it clear that the page is not known with 100% certainty to be an unsafe\nweb resource, and that the warnings merely identify possible risk.\n\n- In your user visible warning, you must not lead users to believe that the page\n in question is, without a doubt, an unsafe web resource. When you refer to the\n page being identified or the potential risks it may pose to users, you must\n qualify the warning using terms such as: suspected, potentially, possible,\n likely, may be.\n\n- Your warning must enable the user to learn more by reviewing information at\n one of the following sites:\n\n - Social engineering (phishing and deceptive sites) warnings: [www.antiphishing.org](https://www.antiphishing.org)\n - Malware warnings: [Google Search Central](https://developers.google.com/search/docs/advanced/security/malware)\n - Unwanted software warnings: [Unwanted Software Policy](https://www.google.com/about/company/unwanted-software-policy.html)\n- When you show warnings for pages identified as risky by the Web Risk\n Service, you must give attribution to Google by including the line \"Advisory\n provided by Google,\" with a link to the [Web Risk Advisory](/web-risk/docs/advisory).\n If your product also shows warnings based on other sources, you must not\n include the Google attribution in warnings derived from non-Google data.\n\n### Suggested warning language\n\nWe encourage you to just copy this warning language in your product, or to\nmodify it slightly to fit your product.\n\n#### For social engineering warnings\n\n\n**Warning: Deceptive site ahead.** Attackers on \\[site URL\\] may trick you into\ndoing something dangerous like installing software or revealing your\npersonal information (for example, passwords, phone numbers, or credit cards).\n\n\u003cbr /\u003e\n\n\nYou can find out more about social engineering (phishing) at\n[Social Engineering (Phishing and Deceptive Sites)](https://support.google.com/webmasters/answer/6350487) or from\n[www.antiphishing.org](http://www.antiphishing.org).\n\n#### For malware warnings\n\n\n**Warning: Visiting this web site may harm your computer.** This page appears\nto contain malicious code that could be downloaded to your computer without your\nconsent. You can learn more about harmful web content including viruses and\nother malicious code and how to protect your computer at\n[Google Search Central](https://developers.google.com/search/docs/advanced/security/malware).\n\n#### For unwanted software warnings\n\n\n**Warning: The site ahead may contain harmful programs.** Attackers might\nattempt to trick you into installing programs that harm your browsing\nexperience (for example, by changing your homepage or showing extra ads on\nsites you visit). You can learn more about unwanted software at\n[Unwanted Software Policy](http://www.google.com/about/company/unwanted-software-policy.html).\n\n#### For Android potentially harmful application (PHA) warnings\n\n\n**Warning: The site ahead may contain malware.** Attackers might attempt to\ninstall dangerous apps on your device that steal or delete your information\n(for example, photos, passwords, messages, and credit cards).\n\n### Age of data and usage\n\nWhen retrieving data using Web Risk, clients must never use data\nolder than what is specified by the service. Specifically, a warning can only be\nshown if the following is true:\n\n- Lookup API: In the [`uris.search` HTTP GET response](/web-risk/docs/lookup-api#http_get_response) a URL matches a threat entry and the cached response is still valid at the time a warning is shown.\n- Update API: In the [`hashes.search` HTTP POST response](/web-risk/docs/update-api#http_get_response-1) a URL matches a full-length hash and the cached response is still valid at the time a warning is shown.\n\n| **Warning:** Under no other circumstances may a warning be shown.\n\nUser protection notice\n----------------------\n\nOur Terms of Service require that if you indicate to users that your service\nprovides protection against unsafe web resources then you must also inform them\nthat the protection is not perfect. This notice must be visible to them\nbefore they enable the protection, and it must inform them that there is a\nchance of both false positives (safe sites flagged as risky) and false\nnegatives (risky sites not flagged). We suggest using the following language: \nGoogle works to provide the most accurate and up-to-date information about unsafe web resources. However, Google cannot guarantee that its information is comprehensive and error-free: some risky sites may not be identified, and some safe sites may be identified in error."]]