Google은 10년 이상 reCAPTCHA를 사용하여 수백만 개의 사이트를 보호해 왔습니다. reCAPTCHA는 고급 위험 분석 기법을 사용하여 사기를 감지합니다. reCAPTCHA를 사용하면 스팸 및 악용으로부터 웹사이트 또는 모바일 애플리케이션을 보호하고 사용자 인증 정보 반복 입력, 계정 탈취(ATO), 자동 계정 생성과 같은 다른 유형의 사기 활동을 감지할 수 있습니다. reCAPTCHA는 보다 세분화된 점수, 위험한 이벤트의 이유 코드, 모바일 앱 SDK, 비밀번호 유출/누출 감지, 다중 인증(MFA), 기업 비즈니스 보호를 위한 사이트별 모델 조정 기능을 사용하여 향상된 감지를 제공합니다.
reCAPTCHA 등급
reCAPTCHA는 사용량을 기반으로 Enterprise, Standard, Essentials 등 3가지 등급을 제공합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-05-07(UTC)"],[],[],null,["# reCAPTCHA overview\n\nGoogle has been defending millions of sites with reCAPTCHA for\nover a decade. reCAPTCHA uses advanced risk analysis techniques\nto detect fraud. With reCAPTCHA, you can protect your websites or mobile applications\nfrom spam and abuse, and detect other types of fraudulent activities, such as\ncredential stuffing, account takeover (ATO), and automated account creation.\nreCAPTCHA offers enhanced detection with more granular scores,\nreason codes for risky\nevents, mobile app SDKs, password leak detection, Multi-factor\nauthentication (MFA), and the ability to tune your site-specific model to\nprotect enterprise businesses.\n\nreCAPTCHA tiers\n---------------\n\nreCAPTCHA offers three usage-based tiers: Enterprise, Standard,\nand Essentials.\n\nTo learn about the features that are available in these tiers, see\n[Compare features between reCAPTCHA tiers](/recaptcha/docs/compare-tiers).\n\nHow reCAPTCHA works\n-------------------\n\nWhen reCAPTCHA is deployed in your environment, it interacts\nwith your backend and client (web pages or mobile applications).\n\nWhen an end user visits a web page or uses a mobile application,\nthe following events are triggered in a sequence:\n\n1. The client loads the web page from the backend or launches the mobile application.\n2. The web page or mobile application initializes the reCAPTCHA JavaScript API or mobile SDK, which begins collecting signals.\n3. When the end user triggers an action protected by reCAPTCHA such as login, the reCAPTCHA JavaScript API or the mobile SDK in the client requests a verdict from reCAPTCHA.\n4. reCAPTCHA returns an encrypted reCAPTCHA token to the client for later use.\n5. The client sends the encrypted reCAPTCHA token to the backend for assessment.\n6. The backend sends the create assessment (`assessments.create`) request and the encrypted reCAPTCHA token to reCAPTCHA.\n7. reCAPTCHA returns a verdict to the backend based on the risk evaluated for this request. This verdict consists of scores from 0.0 through 1.0 and reason codes.\n8. Depending on the verdict, you (as the developer) can determine the next steps to take for that specific user request or action.\n\nThe following sequence diagram shows the graphical representation of the\nreCAPTCHA workflow:\n\nWhat's next\n-----------\n\n- [Test reCAPTCHA in a demo website](/recaptcha/docs/quickstart-app).\n- [Get started with reCAPTCHA](/recaptcha/docs/getting-started).\n- To get started with plugins, [find the legacy reCAPTCHA secret key](/recaptcha/docs/create-key-website#find-key)."]]
