使用限制
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
允许的使用情形
Safe Browsing API 仅适用于非商业用途(即“不作销售或创收之用”)。如果您需要适用于商业目的的解决方案,请参阅 Web Risk。如需进一步的指导,请访问 Google Safe Browsing API 社区论坛查看常见问题的答案。
用量配额
开发者启用 Safe Browsing API 后,系统会为其分配默认的用量配额。您可以在
Google Developer Console 中查看当前的分配和使用情况。如果您预计使用的配额会超过当前分配的配额,可以从
开发者控制台的配额界面申请更多配额。我们会审核这些请求,并在申请增加配额时要求联系人,以确保我们的服务可用性满足所有 API 用户的需求。使用此 API 无需支付任何费用。如需详细了解大型非商业性部署,请使用上面的链接申请更多配额,并说明您的应用需求,或在 Google Safe Browsing API 社区论坛中查找常见问题的解答。
用户警告
如果您使用安全浏览 API (v4) 向用户发出警告,以发现特定网页存在的风险,请遵循以下指南。
这些准则明确指出网页并非 100% 确定是否为不安全的 Web 资源,并且这些警告仅标识可能的风险,从而帮助您和 Google 避免误解。
-
在用户可见的警告中,您不得让用户相信相关网页毫无疑问是不安全的 Web 资源。在提及要识别的网页或它可能会给用户带来的潜在风险时,您必须使用以下字词来限定警告资格,例如“疑似”“可能”“很有可能”。
-
您的警告必须让用户能够通过查看 www.antiphishing.org 上针对社会工程学(钓鱼式攻击和欺骗性网站)警告、Google 搜索中心中针对恶意软件警告以及垃圾软件政策中有关垃圾软件警告的信息进行了解详情。
-
当您针对安全浏览服务识别为有风险的网页显示警告时,您必须注明“Google 提供的安全建议”行,并附上指向安全浏览建议的链接,以注明内容来自 Google。
如果您的商品还根据其他来源显示警告,则不得在源自非 Google 数据的警告中包含 Google 提供方说明。
建议的警告语言
我们建议您只在产品中复制此警告用语,或对它稍作修改,使其适合您的产品(请参阅元数据,了解可能适用的其他信息)。
对于社会工程学攻击(钓鱼式攻击和欺骗性网站)警告:
警告 - 您要访问的是诈骗网站。[site 网址] 上的攻击者可能会诱使您执行一些危险的操作,例如安装软件或泄露您的个人信息(例如密码、电话号码或信用卡信息)。
如需详细了解社会工程学(钓鱼式攻击),请访问
社会工程学(钓鱼式攻击和欺骗性网站)或 www.antiphishing.org。
对于恶意软件警告:
警告 - 访问此网站可能会损害您的计算机。此网页似乎包含恶意代码,这些代码可能会在未经您同意的情况下下载到您的计算机。您可以前往 Google 搜索中心,详细了解包含病毒和其他恶意代码在内的有害 Web 内容,以及如何保护您的计算机。
对于垃圾软件警告:
警告 - 您要访问的网站可能包含有害程序。攻击者可能会试图诱使您安装会损害浏览体验的程序(例如,通过更改您的主页或在您访问的网站上展示额外的广告)。如需详细了解垃圾软件,请参阅垃圾软件政策。
对于 Android 潜在有害应用 (PHA) 警告:
警告 - 您要访问的网站可能包含恶意软件。攻击者可能会试图在您的设备上安装危险应用,以窃取或删除您的信息(例如照片、密码、消息和信用卡信息)。
数据时代和用量
在使用安全浏览 API (v4) 检索数据时,客户端绝不能使用早于服务指定时间的数据。具体来说,只有在满足以下条件时,系统才会显示警告:
重要提示:在任何情况下,系统都不会显示警告。
用户保护通知
我们的《服务条款》规定,如果您告知用户您的服务会针对不安全的 Web 资源提供保护,那么您还必须告知用户这项保护并不完美。他们必须在启用该保护功能前向其显示此通知,同时还须告知他们可能会出现误报(标记为有风险的安全网站)和假负例(未标记有风险的网站)的可能性。我们建议您使用以下语言:
Google 致力于提供有关不安全网络资源的最准确和最新信息。
不过,Google 无法保证其信息全面且没有错误:一些有风险的网站可能未被识别出来,而一些安全网站也可能会被错误地识别。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThe Safe Browsing API is for non-commercial use only; commercial users should refer to Web Risk.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers receive a default usage quota, which can be increased upon request through the Google Developer Console.\u003c/p\u003e\n"],["\u003cp\u003eWarnings to users about potentially risky websites must use qualifying language and include attribution to Google with a link to the Safe Browsing Advisory.\u003c/p\u003e\n"],["\u003cp\u003eWarnings should follow the suggested language provided or be slightly modified to fit the product's context.\u003c/p\u003e\n"],["\u003cp\u003eUser protection notices are required to inform users that the protection offered is not perfect and may have false positives or negatives.\u003c/p\u003e\n"]]],["The Safe Browsing API is for non-commercial use; commercial users should use Web Risk. Developers have a default quota, viewable and adjustable via the Developer Console, with no usage cost. When warning users about potential web risks, warnings must qualify the risk as \"suspected,\" \"potential,\" etc., and provide links to resources like antiphishing.org and Google Search Central. Attribution to \"Advisory provided by Google\" is required for Google-derived warnings. Data shown must not be older than specified by the service. Users must be informed protection is not perfect.\n"],null,["# Usage Restrictions\n\nPermitted use\n-------------\n\nThe Safe Browsing API is for non-commercial use only (meaning \"not for sale or revenue generating purposes\").\nIf you need a solution for commercial purposes, please refer to [Web Risk](https://cloud.google.com/web-risk). For further guidance, please visit the [Google Safe Browsing API](https://groups.google.com/forum/#!forum/google-safe-browsing-api) community forum for answers to common questions.\n\nUsage Quota\n-----------\n\nDevelopers are allocated a default usage quota upon enabling the Safe Browsing API.\nCurrent allocation and usage can be viewed in the [Google Developer Console](https://console.developers.google.com/apis/api/safebrowsing.googleapis.com/quotas). If you expect to use more than your currently allocated quota,\nyou may request additional quota from the [Developer Console's Quota interface](https://console.developers.google.com/apis/api/safebrowsing.googleapis.com/quotas). We review these requests and require a contact when\napplying for an increased quota to ensure that our service availability meets the needs of all\nAPI users. There is no cost for use of this API. For more information about large\nnon-commercial deployments, please apply for additional quota using the link above and\ndescribe your application needs or find answers to common questions in the [Google Safe Browsing API](https://groups.google.com/forum/#!forum/google-safe-browsing-api) community forum.\n\nUser warnings\n-------------\n\nIf you use the Safe Browsing APIs (v4) to warn users about risks from particular\nwebpages, the following guidelines apply.\n\nThese guidelines help protect both you and Google from misunderstandings by making clear that\nthe page is not known with 100% certainty to be an unsafe web resource, and that the warnings\nmerely identify possible risk.\n\n- In your user visible warning, you must not lead users to believe that the page in question is, without a doubt, an unsafe web resource. When you refer to the page being identified or the potential risks it may pose to users, you must qualify the warning using terms such as: suspected, potentially, possible, likely, may be.\n- Your warning must enable the user to learn more by reviewing information at [www.antiphishing.org](//www.google.com/url?q=http://www.antiphishing.org&usg=AFrqEzdc43cbWnGpYdvxqO6R0Xvs3hrtSQ) for social engineering (phishing and deceptive sites) warnings, [Google Search Central](//www.google.com/url?q=https://developers.google.com/search/docs/advanced/security/malware) for malware warnings, and [Unwanted Software Policy](http://www.google.com/about/company/unwanted-software-policy.html) for unwanted software warnings.\n- When you show warnings for pages identified as risky by the Safe Browsing Service, you must give attribution to Google by including the line \"Advisory provided by Google,\" with a link to the [Safe Browsing Advisory](/safe-browsing/v4/advisory). If your product also shows warnings based on other sources, you must not 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 modify it slightly\nto fit your product (see [Metadata](/safe-browsing/v4/metadata)\nfor additional information that may apply).\n\n**For social engineering (phishing and deceptive sites) warnings:**\n\n\n**Warning---Deceptive site ahead** . Attackers on \\[site URL\\] may trick you into doing\nsomething dangerous like installing software or revealing your personal information (for example,\npasswords, phone numbers, or credit cards).\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)\nor from\n[www.antiphishing.org](//www.google.com/url?q=http://www.antiphishing.org&usg=AFrqEzdc43cbWnGpYdvxqO6R0Xvs3hrtSQ).\n\n**For malware warnings:**\n\n\n**Warning---Visiting this web site may harm your\ncomputer** . This page appears to contain malicious code that could be\ndownloaded to your computer without your consent. You can learn more about harmful web content\nincluding viruses and other malicious code and how to protect your computer at\n[Google Search Central](//www.google.com/url?q=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 attempt to\ntrick you into installing programs that harm your browsing experience (for example, by changing\nyour homepage or showing extra ads on sites you visit). You can learn more about unwanted software\nat [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 install\ndangerous apps on your device that steal or delete your information (for example, photos,\npasswords, messages, and credit cards).\n\n### Age of data and usage\n\nWhen retrieving data using the Safe Browsing APIs (v4) clients must never use data older than what\nis specified by the service. Specifically, a warning can only be shown if the following is true:\n\n- Lookup API (v4): In the [threatMatches.find HTTP POST response](/safe-browsing/v4/lookup-api#http-post-response) a URL matches a threat entry and the cached response is still valid at the time a warning is shown.\n- Update API (v4): In the [fullHashes.find HTTP POST response](/safe-browsing/v4/update-api#http-post-response_2) a URL matches a full-length hash and the cached response is still valid at the time a warning is shown.\n\n**Important:** Under no other circumstances may a warning be shown.\n\nUser protection notice\n----------------------\n\n\nOur Terms of Service require that if you indicate to users that your service provides protection\nagainst unsafe web resources then you must also let them know that the protection is not perfect.\nThis notice must be visible to them before they enable the protection, and it must let them know\nthat there is a chance of both false positives (safe sites flagged as risky) and false\nnegatives (risky sites not flagged). We suggest using the following language:\n\n\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.\n\n\u003cbr /\u003e"]]