使用限制
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
許可用途
Safe Browsing API 僅限非商業用途 (即「並非用於銷售或收益產生」) 使用。
如需商業用途的解決方案，請參閱 Web Risk。如需進一步指引，請前往 Google Safe Browsing API 社群論壇，取得常見問題的解答。
用量配額
開發人員在啟用 Safe Browsing API 後，會分配預設用量配額。
您可以在
Google Developers Console 中查看目前的配置和用量。如果您預期耗用的配額會超過目前分配的配額，則可透過
Developer Console 的「配額」介面要求額外配額。我們會審查這些要求，並在申請增加配額時要求聯絡人，確保我們的服務可用性符合所有 API 使用者的需求。使用這個 API 不須支付任何費用。如要進一步瞭解大型非商業性部署作業，請使用上方連結申請更多配額，並說明您的應用程式需求，或是前往 Google Safe Browsing API 社群論壇尋找常見問題的解答。
使用者警示
如果您使用 Safe Browsing API (v4) 向使用者警告特定網頁的風險，請遵循下列規範。
這些規範會明確指出該網頁並非無人知曉，且該警告只是用來識別可能的風險，進而避免您與 Google 受到誤解。
-
向使用者顯示的警告，您不得讓使用者以為確認相關網頁是不安全的網頁資源。當您提及發現的網頁，或可能對使用者產生潛在風險時，必須使用「疑似、可能、可能是，都有可能」等字詞符合警告資格。
-
警告使用者必須前往 www.antiphishing.org 查看社交工程 (網路釣魚和詐欺網站) 警告、Google 搜尋中心是否含有惡意軟體警告，以及垃圾軟體政策中的垃圾軟體警告，可協助使用者進一步瞭解相關資訊。
-
當您針對安全瀏覽服務判定具有風險的網頁顯示警告時，您必須加入「Google 提供的補充公告」行，並且附上安全瀏覽補充公告的連結，明確告知 Google 這項資訊。
如果產品也會根據其他來源顯示警告，請勿在非 Google 資料衍生的警告中附上 Google 註明出處。
建議的警告語言
建議您直接複製產品中的警告用語，或是根據產品稍微修改這段文字 (如需其他資訊，請參閱中繼資料)。
社交工程 (網路釣魚和詐欺網站) 警告：
警告 - 你要瀏覽的是詐騙網站。攻擊者可能會試圖透過 [網站網址] 誘使你做一些危險行為，例如安裝軟體或提供個人資訊 (包括密碼、電話號碼或信用卡資料)。如要進一步瞭解社交工程 (網路釣魚)，請前往
社交工程 (網路詐騙和欺騙性網站) 或 www.antiphishing.org。
惡意軟體警告：
警告：造訪這個網站可能會損害你的電腦。這個網頁似乎含有惡意程式碼，可能會在未經您同意的情況下下載到您的電腦。如要進一步瞭解有害網頁內容 (包括病毒和其他惡意程式碼)，以及如何保護電腦，請前往 Google 搜尋中心。
垃圾軟體警告：
警告：你要瀏覽的網站可能包含有害程式。攻擊者可能會試圖誘騙你安裝對瀏覽體驗造成不良影響的程式，例如變更你的首頁，或是在你造訪的網站上顯示額外廣告。如要進一步瞭解垃圾軟體，請參閱《垃圾軟體政策》。
對於可能有害的 Android 應用程式 (PHA) 警告：
警告：你要瀏覽的網站可能含有惡意軟體。攻擊者可能會試圖在你的裝置上安裝危險應用程式，藉此竊取或刪除你的資訊 (例如相片、密碼、訊息和信用卡資訊)。
資料時間和使用年代
使用 Safe Browsing API (v4) 用戶端擷取資料時，系統一律不使用服務指定內容的資料。具體來說，系統只會在下列情況下顯示警告：
重要事項：在其他情況下，系統不會顯示警告訊息。
使用者防護聲明
根據我們的《服務條款》，如果您向使用者指出您的服務可以防範不安全的網路資源，則須一併告知使用者這項防護機制並非無懈可擊。
通知在啟用保護措施前必須向使用者顯示，且務必告知可能出現誤判情形 (安全網站遭標記為有風險) 和偽陰性 (未標記為有風險的網站)。建議您使用下列語言：
Google 致力於提供最正確且最新的不安全網頁資源相關資訊。
不過，Google 無法保證其資訊完整且沒有錯誤，因此可能無法找出部分有風險的網站，且可能誤認某些安全網站。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：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"]]
