{"id":24879,"date":"2026-08-05T11:24:13","date_gmt":"2026-08-05T11:24:13","guid":{"rendered":"https:\/\/capskip.com\/?p=24879"},"modified":"2026-08-05T11:24:13","modified_gmt":"2026-08-05T11:24:13","slug":"geetest-v3-csharp","status":"publish","type":"post","link":"https:\/\/capskip.com\/zh\/geetest-v3-csharp\/","title":{"rendered":"\u5982\u4f55\u7528 C# \u8bc6\u522b\u6781\u9a8c v3"},"content":{"rendered":"

GeeTest breaks the mental model most CAPTCHA code is built on. There is no single token to drop into a form field. A solve returns three<\/strong> values that have to be posted back together, and the challenge you started from expires in about a minute. Get either part wrong and the request fails with no useful error.<\/p>\n

Here is the whole flow in C#, including the parts that are easy to get wrong.<\/p>\n

Two inputs, and only one of them is stable<\/h2>\n

GeeTest v3 identifies a site with gt<\/code> and a single attempt with challenge<\/code>. They behave completely differently.<\/p>\n\n\n\n\n\n\n
Value<\/th>\nLifetime<\/th>\nWhere it comes from<\/th>\n<\/tr>\n<\/thead>\n
gt<\/code><\/td>\nStatic for the site. Safe to hard-code or cache<\/td>\nThe site’s GeeTest init response<\/td>\n<\/tr>\n
challenge<\/code><\/td>\nSingle use, expires in roughly 60 seconds<\/strong><\/td>\nThe same init response, fresh every time<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

That expiry is the single most common cause of GeeTest failures. If you fetch a pair, queue the job, and solve it thirty seconds later behind other work, the challenge may already be dead. Fetch it immediately before solving, never from a cache.<\/p>\n

Setup<\/h2>\n
# Targets .NET Standard 2.0, so Framework 4.6.1+ and .NET 6-9 all work.\ndotnet add package CapSkip<\/pre>\n
CapSkip runs on your own machine, so start the app first and point the client at the port from its settings:<\/p>\n
using CapSkip;\n\nvar solver = new CapSkipClient(\n    apiKey: "capskip",        \/\/ any string when key validation is off\n    host: "127.0.0.1",\n    port: 8080,\n    recaptchaTimeout: 300);   \/\/ seconds, and this one covers GeeTest too<\/pre>\n
Note that GeeTest uses recaptchaTimeout<\/code>, not defaultTimeout<\/code>. The latter only applies to image CAPTCHAs.<\/p>\n
Solving it<\/h2>\n
Three positional arguments, in this order:<\/p>\n
var result = await solver.GeetestAsync(\n    "81388ea1fc187e0c335c0a8907ff2625",   \/\/ gt, static per site\n    "7cf6a8b1a2c34d5e6f7089abcdef0123",   \/\/ challenge, fetched seconds ago\n    "https:\/\/example.com\/login");\n\nConsole.WriteLine(result.Challenge);\nConsole.WriteLine(result.Validate);\nConsole.WriteLine(result.Seccode);<\/pre>\n
Those three properties are the answer. result.Code<\/code> is also populated, but for GeeTest it holds the raw JSON string rather than a usable token, so reaching for Code<\/code> out of habit is a mistake. On SolveResult<\/code>, Challenge<\/code>, Validate<\/code> and Seccode<\/code> are GeeTest-only and null for every other type.<\/p>\n
Worth knowing: the challenge<\/code> that comes back is not always the one you sent in. Use the returned value, not your input.<\/p>\n
Posting the answer back<\/h2>\n
Submit all three exactly as the site’s own front end would. Most GeeTest v3 integrations use these field names, though a site can rename them, so check the real form before assuming:<\/p>\n
using System.Net.Http;\nusing System.Collections.Generic;\n\nusing var http = new HttpClient();\n\nvar form = new FormUrlEncodedContent(new[]\n{\n    new KeyValuePair<string, string>("geetest_challenge", result.Challenge),\n    new KeyValuePair<string, string>("geetest_validate",  result.Validate),\n    new KeyValuePair<string, string>("geetest_seccode",   result.Seccode),\n    new KeyValuePair<string, string>("username", "..."),\n    new KeyValuePair<string, string>("password", "..."),\n});\n\nvar response = await http.PostAsync("https:\/\/example.com\/login", form);<\/pre>\n
Sending two of the three, or pairing a fresh validate<\/code> with a stale challenge<\/code>, gets rejected the same way a wrong answer would.<\/p>\n
The whole flow, in order<\/h2>\n
Fetching the pair and solving have to sit next to each other. This shape keeps them there:<\/p>\n
using System;\nusing System.Net.Http;\nusing System.Text.Json;\nusing CapSkip;\n\n\/\/ 1. Fetch a fresh gt\/challenge pair from the site's own init endpoint.\nusing var http = new HttpClient();\nvar initJson = await http.GetStringAsync(\n    "https:\/\/example.com\/geetest\/init?t=" + DateTimeOffset.UtcNow.ToUnixTimeMilliseconds());\n\nusing var doc = JsonDocument.Parse(initJson);\nvar gt        = doc.RootElement.GetProperty("gt").GetString();\nvar challenge = doc.RootElement.GetProperty("challenge").GetString();\n\n\/\/ 2. Solve immediately. Do not queue this or await anything slow in between.\nvar result = await solver.GeetestAsync(gt, challenge, "https:\/\/example.com\/login");\n\n\/\/ 3. Post all three values together.\nConsole.WriteLine($"{result.Challenge} {result.Validate} {result.Seccode}");<\/pre>\n
The cache-busting timestamp on the init call matters more than it looks. GeeTest init endpoints are frequently cached by intermediaries, and a cached response hands you a challenge that was already consumed.<\/p>\n
When it fails<\/h2>\n
using System;\nusing CapSkip;\n\ntry\n{\n    var result = await solver.GeetestAsync(gt, challenge, pageUrl);\n}\ncatch (CapSkip.ValidationException) { \/* missing gt or challenge *\/ }\ncatch (NetworkException)            { \/* CapSkip is not running *\/ }\ncatch (ApiException)                { \/* API error, often a dead challenge *\/ }\ncatch (CapSkip.TimeoutException)    { \/* exceeded recaptchaTimeout *\/ }\ncatch (CapSkipError)                { \/* anything else from the SDK *\/ }<\/pre>\n
Qualify ValidationException<\/code> and TimeoutException<\/code> with the CapSkip<\/code> namespace. Both names also exist in System<\/code>, and with both namespaces imported an unqualified catch binds to the System<\/code> type and silently never fires. Catching the base CapSkipError<\/code> sidesteps the problem entirely.<\/p>\n
In practice most GeeTest failures surface as ApiException<\/code> and mean the challenge died before the solve finished. The fix is fetching later, not retrying with the same values.<\/p>\n
Proxies and concurrency<\/h2>\n
GeeTest is one of the three types that accept a proxy, alongside reCAPTCHA and Turnstile. Image CAPTCHAs do not, because they never touch the target site.<\/p>\n
using System.Collections.Generic;\n\nvar result = await solver.GeetestAsync(gt, challenge, pageUrl,\n    new Dictionary<string, object?>\n    {\n        ["proxy"] = new Proxy("HTTPS", "user:pass@1.2.3.4:3128"),\n    });<\/pre>\n
Running several in parallel works, but each one needs its own freshly fetched pair. Do not fetch a batch of challenges up front and then solve them together, because the last ones will have expired before their turn.<\/p>\n
\/\/ Correct: fetch and solve inside the same task.\nvar tasks = urls.Select(async url =>\n{\n    var (gt, challenge) = await FetchPairAsync(url);\n    return await solver.GeetestAsync(gt, challenge, url);\n});\n\nvar results = await Task.WhenAll(tasks);<\/pre>\n
Frequently asked questions<\/h2>\n
\n\n
Why is result.Code not a usable token?<\/h3>\n<\/summary>\n
Because GeeTest’s answer is three values, not one. Code<\/code> keeps the raw JSON string for completeness, while the SDK expands the useful parts into Challenge<\/code>, Validate<\/code> and Seccode<\/code>. Use those three.<\/p>\n<\/details>\n
\n\n
Can I cache the challenge to save a request?<\/h3>\n<\/summary>\n
No. It is single use and expires in about a minute. Caching it is the most common reason GeeTest integrations work in testing and fail under load, because queueing delay pushes the solve past the expiry window. The gt<\/code> value is safe to cache.<\/p>\n<\/details>\n
\n\n
Does this work for GeeTest v4?<\/h3>\n<\/summary>\n
The GeetestAsync<\/code> method targets v3, the slide-puzzle version built around the gt<\/code> and challenge<\/code> pair. v4 changed the parameter model, so check the current API documentation<\/a> for what is supported before assuming the same call works.<\/p>\n<\/details>\n
\n\n
Do I need a proxy?<\/h3>\n<\/summary>\n
Only when the site is geo-sensitive or already treats your address as suspicious. Solve and submit from the same network path when you do use one, otherwise the mismatch can itself trigger a re-challenge.<\/p>\n<\/details>\n
Summary<\/h2>\n
Fetch gt<\/code> and challenge<\/code> immediately before solving, call GeetestAsync<\/code> with both plus the page URL, then post Challenge<\/code>, Validate<\/code> and Seccode<\/code> back together. Treat the challenge as perishable, use the returned challenge rather than your input, and catch CapSkipError<\/code> to avoid the namespace collision.<\/p>\n
Method signatures for the other languages are on the GeeTest solver<\/a> page, the full .NET surface is on the C# CAPTCHA solver<\/a> page, and you can try a live puzzle on our GeeTest v3 demo<\/a>. CapSkip handles captcha bypass<\/a> locally, so solve volume costs nothing per request.<\/p>\n","protected":false},"excerpt":{"rendered":"
\u6781\u9a8c\u4e0d\u4f1a\u53ea\u4ea4\u56de\u4e00\u4e2a token\u3002\u5b83\u8fd4\u56de\u4e09\u4e2a\u5fc5\u987b\u4e00\u8d77\u63d0\u4ea4\u7684\u503c\uff0c\u800c\u4e14\u4f60\u6240\u4f9d\u636e\u7684\u6311\u6218\u7ea6\u4e00\u5206\u949f\u540e\u8fc7\u671f\u3002<\/p>","protected":false},"author":1,"featured_media":24878,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Solve GeeTest v3 in C# (.NET) | CapSkip","rank_math_description":"To solve GeeTest in C# you need a fresh challenge, then three values posted back together. Here is the .NET code, and the 60-second expiry that breaks it.","rank_math_focus_keyword":"solve geetest in c#","footnotes":""},"categories":[70],"tags":[],"class_list":["post-24879","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-captcha"],"_links":{"self":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/24879","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/comments?post=24879"}],"version-history":[{"count":1,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/24879\/revisions"}],"predecessor-version":[{"id":24880,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/posts\/24879\/revisions\/24880"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media\/24878"}],"wp:attachment":[{"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/media?parent=24879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/categories?post=24879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/capskip.com\/zh\/wp-json\/wp\/v2\/tags?post=24879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}