[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:socks5-residential-proxy-guide":3,"blog-article:\u002Fblog\u002Fsocks5-residential-proxy-guide":77,"blog-related:\u002Fblog\u002Fsocks5-residential-proxy-guide":1136,"blog-translations:\u002Fblog\u002Fsocks5-residential-proxy-guide":1137},{"available":4,"article":5,"relatedArticles":325,"translations":982},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":116},"strapi",650,"bvllzn6qxp1q431cdz50viu8","zh","socks5-residential-proxy-guide","\u002Fblog\u002Fsocks5-residential-proxy-guide","SOCKS5住宅代理是什么：适用场景、配置方式和选择方法","说明 SOCKS5 住宅代理和 HTTP 住宅代理的区别，以及适合哪些业务。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_SEO_8a9f465f2a.png","2026-06-18T10:29:17.058Z","2026-06-18T10:29:17.024Z","Global Proxies Team",[],false,0,12,"blocks",[24,30,34,38,44,48,52,56,60,65,117,121,125,129,166,170,174,178,182,187,191,195,199,203,207,249,253,257,261,265,269,273,277,281,285,289,293,297,301,305,309,313,317,321],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"搜 `SOCKS5住宅代理` 的人，通常已经遇到过很具体的接入问题，比如网页能打开，但客户端老掉线，登录虽然能过，会话却总是不稳。多数时候，问题并不在“住宅”这两个字本身，而在于协议层和资源层被混在一起判断了，不清楚自己到底是在选一种更通用的流量通道，还是在选底层 IP 资源。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"SOCKS5 住宅代理更像通用流量通道，适合浏览器插件、客户端、脚本和部分非网页流量。只做网页请求时，HTTP\u002FHTTPS 往往更直接，接入和排查都更省事；如果工具更复杂，或者需要更广的协议兼容，再优先考虑 SOCKS5。协议选好之后，再继续判断底层该配静态住宅还是动态住宅，会更不容易走偏。",{"type":25,"children":35},[36],{"text":37,"type":29},"更新时间：2026-06-11",{"type":39,"level":40,"children":41},"heading",2,[42],{"text":43,"type":29},"SOCKS5住宅代理是什么",{"type":25,"children":45},[46],{"text":47,"type":29},"SOCKS5住宅代理更适合优先出现在客户端软件、Telegram、桌面程序和其他非纯网页流量场景里，因为这类任务对协议兼容性的要求通常更高。要是你的任务只是后台登录、普通网页访问和日常管理，HTTP\u002FHTTPS 往往反而更容易接入和排查。",{"type":25,"children":49},[50],{"text":51,"type":29},"很多人误把 SOCKS5 理解成“天然更稳”，这其实不准确。协议本身只是决定怎么转发流量，能不能长期稳定，还要看底层住宅资源是不是适合当前任务。",{"type":39,"level":40,"children":53},[54],{"text":55,"type":29},"SOCKS5住宅代理和 HTTP 住宅代理有什么区别",{"type":25,"children":57},[58],{"text":59,"type":29},"普通网页访问、后台操作和账号日常维护，先看 HTTP\u002FHTTPS，因为兼容更直观，排查也更省时间；桌面客户端、Telegram 和非纯 Web 流量，更值得优先看 SOCKS5。HTTP 和 SOCKS5 的区别不在“谁更高级”，而在你的工具吃哪种协议、会话是否稳定、地区是否持续一致。若把客户端任务硬放到 HTTP，常见结果是能连但掉会话；把纯网页任务全改成 SOCKS5，也未必降低验证码。",{"type":61,"children":62},"code",[63],{"text":64,"type":29},"| 维度 | SOCKS5住宅代理 | HTTP代理 | 判断重点 |\n| --- | --- | --- | --- |\n| 流量类型 | 更适合客户端、浏览器外工具、多协议流量 | 更适合普通网页访问、后台登录 | 先看业务是不是纯 Web |\n| 配置排查 | 需要确认工具是否原生支持 SOCKS5 | 浏览器和常见网页环境更直观 | 先看接入复杂度和团队熟悉度 |\n| 会话与资源搭配 | 常与静态或动态住宅结合判断 | 同样要看底层资源质量 | 协议对了不等于资源就稳 |\n| 适用成本 | 协议更灵活，但不必默认全量上 | 轻量网页任务通常更省排查成本 | 别为了“更高级”就强行升级 |",{"type":66,"image":67,"children":114},"image",{"id":68,"ext":69,"url":70,"hash":71,"mime":72,"name":73,"size":74,"width":75,"height":76,"caption":77,"formats":78,"provider":111,"createdAt":112,"updatedAt":112,"documentId":113,"focalPoint":77,"previewUrl":77,"publishedAt":112,"alternativeText":77,"provider_metadata":77},570,".webp","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f.webp","socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f","image\u002Fwebp","socks5-residential-proxy-guide-seomaster-draft-1.webp",98.5,1619,971,null,{"large":79,"small":87,"medium":95,"thumbnail":103},{"ext":69,"url":80,"hash":81,"mime":72,"name":82,"path":77,"size":83,"width":84,"height":85,"sizeInBytes":86},"\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f.webp","large_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f","large_socks5-residential-proxy-guide-seomaster-draft-1.webp",51.39,1000,600,51386,{"ext":69,"url":88,"hash":89,"mime":72,"name":90,"path":77,"size":91,"width":92,"height":93,"sizeInBytes":94},"\u002Fuploads\u002Fsmall_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f.webp","small_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f","small_socks5-residential-proxy-guide-seomaster-draft-1.webp",20.36,500,300,20360,{"ext":69,"url":96,"hash":97,"mime":72,"name":98,"path":77,"size":99,"width":100,"height":101,"sizeInBytes":102},"\u002Fuploads\u002Fmedium_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f.webp","medium_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f","medium_socks5-residential-proxy-guide-seomaster-draft-1.webp",35.72,750,450,35716,{"ext":69,"url":104,"hash":105,"mime":72,"name":106,"path":77,"size":107,"width":108,"height":109,"sizeInBytes":110},"\u002Fuploads\u002Fthumbnail_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f.webp","thumbnail_socks5_residential_proxy_guide_seomaster_draft_1_a650820d2f","thumbnail_socks5-residential-proxy-guide-seomaster-draft-1.webp",7.21,245,147,7210,"local","2026-06-17T12:33:36.375Z","nzfnvqhlb98pkglrlvf635ad",[115],{"text":116,"type":29},"",{"type":39,"level":40,"children":118},[119],{"text":120,"type":29},"哪些业务适合 SOCKS5 住宅代理",{"type":25,"children":122},[123],{"text":124,"type":29},"只要任务主要跑在桌面客户端、Telegram、社媒辅助工具或其他非纯网页流量里，住宅 SOCKS5 通常更值得先评估，因为协议适配会更顺一些。但如果只是后台登录、表单提交和普通网页访问，HTTP\u002FHTTPS 往往更省排查成本，没必要为了“更全能”就强行切到 SOCKS5。",{"type":25,"children":126},[127],{"text":128,"type":29},"如果你是在做具体软件场景，可以继续看 [Telegram代理IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Ftelegram-proxy-ip-guide) 和 [Google代理IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fgoogle-proxy-ip-guide)；如果问题已经转到长期稳定出口本身，再回到 [静态住宅代理](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fstatic-residential-proxy-ip-guide) 会更清楚。",{"type":66,"image":130,"children":164},{"id":131,"ext":69,"url":132,"hash":133,"mime":72,"name":134,"size":135,"width":75,"height":136,"caption":77,"formats":137,"provider":111,"createdAt":162,"updatedAt":162,"documentId":163,"focalPoint":77,"previewUrl":77,"publishedAt":162,"alternativeText":77,"provider_metadata":77},571,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268.webp","socks5_residential_proxy_guide_seomaster_draft_2_ae25418268","socks5-residential-proxy-guide-seomaster-draft-2.webp",126.38,972,{"large":138,"small":144,"medium":150,"thumbnail":156},{"ext":69,"url":139,"hash":140,"mime":72,"name":141,"path":77,"size":142,"width":84,"height":85,"sizeInBytes":143},"\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268.webp","large_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268","large_socks5-residential-proxy-guide-seomaster-draft-2.webp",65.2,65200,{"ext":69,"url":145,"hash":146,"mime":72,"name":147,"path":77,"size":148,"width":92,"height":93,"sizeInBytes":149},"\u002Fuploads\u002Fsmall_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268.webp","small_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268","small_socks5-residential-proxy-guide-seomaster-draft-2.webp",25.56,25558,{"ext":69,"url":151,"hash":152,"mime":72,"name":153,"path":77,"size":154,"width":100,"height":101,"sizeInBytes":155},"\u002Fuploads\u002Fmedium_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268.webp","medium_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268","medium_socks5-residential-proxy-guide-seomaster-draft-2.webp",44.78,44782,{"ext":69,"url":157,"hash":158,"mime":72,"name":159,"path":77,"size":160,"width":108,"height":109,"sizeInBytes":161},"\u002Fuploads\u002Fthumbnail_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268.webp","thumbnail_socks5_residential_proxy_guide_seomaster_draft_2_ae25418268","thumbnail_socks5-residential-proxy-guide-seomaster-draft-2.webp",8.79,8794,"2026-06-17T12:33:37.047Z","gp4h5l33xw1ug427bny12vs1",[165],{"text":116,"type":29},{"type":39,"level":40,"children":167},[168],{"text":169,"type":29},"哪些场景不适合 SOCKS5",{"type":25,"children":171},[172],{"text":173,"type":29},"做后台登录、普通网页访问或轻量测试，先看 HTTP\u002FHTTPS。原因不是 SOCKS5 不好，而是这类任务更看工具兼容、排查成本和会话是否稳定；若工具本身对 HTTP 支持更稳，硬切 SOCKS5 往往只会增加排查时间，验证码也不一定更少。",{"type":25,"children":175},[176],{"text":177,"type":29},"同样，如果你真正的问题是长期登录不稳、地区频繁跳变，那问题更可能出在资源层，而不是协议层。这个时候盲目换 SOCKS5，并不会替代对静态住宅、独享性和地区一致性的判断。",{"type":39,"level":40,"children":179},[180],{"text":181,"type":29},"SOCKS5住宅代理怎么配置",{"type":39,"level":183,"children":184},3,[185],{"text":186,"type":29},"购买和测试时先查哪些项，才能少走弯路",{"type":25,"children":188},[189],{"text":190,"type":29},"做客户端、Telegram 或社媒工具，先确认 SOCKS5住宅代理是否被工具稳定支持，再看账号密码等认证方式是否兼容；长期账号和店铺，还要盯会话时长、地区一致性与验证码变化。别只测能不能连上，必须到目标站实测登录、停留和切换动作，否则协议能通，业务照样掉会话。",{"type":25,"children":192},[193],{"text":194,"type":29},"更稳的顺序通常是：先确认工具支持什么协议，再确认认证方式，然后做目标站点实测，最后才判断底层更适合静态住宅还是动态住宅。少了中间任何一步，后面都容易重复排查。",{"type":39,"level":183,"children":196},[197],{"text":198,"type":29},"先按这四步走",{"type":25,"children":200},[201],{"text":202,"type":29},"如果你已经确定工具更适合 SOCKS5，可以先按这个顺序配置，不要一上来同时改协议、改地区、改资源类型：",{"type":25,"children":204},[205],{"text":206,"type":29},"1. 先确认工具或客户端原生支持 `SOCKS5`，别把只支持 HTTP 的入口硬拿来测。\n2. 再核对 `host`、`port`、`username`、`password` 这四个字段，尤其别把 HTTP 端口填到 SOCKS5。\n3. 配好后先做一轮最小实测：登录、停留、切换页面或发起一次真实请求，别只看“连接成功”。\n4. 协议能通后，再判断底层应该继续用静态住宅还是动态住宅，不要把资源层问题误判成协议问题。",{"type":66,"image":208,"children":247},{"id":209,"ext":69,"url":210,"hash":211,"mime":72,"name":212,"size":213,"width":214,"height":215,"caption":77,"formats":216,"provider":111,"createdAt":245,"updatedAt":245,"documentId":246,"focalPoint":77,"previewUrl":77,"publishedAt":245,"alternativeText":77,"provider_metadata":77},572,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c.webp","socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c","socks5-residential-proxy-guide-seomaster-draft-3.webp",100.63,1672,941,{"large":217,"small":224,"medium":231,"thumbnail":238},{"ext":69,"url":218,"hash":219,"mime":72,"name":220,"path":77,"size":221,"width":84,"height":222,"sizeInBytes":223},"\u002Fuploads\u002Flarge_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c.webp","large_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c","large_socks5-residential-proxy-guide-seomaster-draft-3.webp",50.03,563,50028,{"ext":69,"url":225,"hash":226,"mime":72,"name":227,"path":77,"size":228,"width":92,"height":229,"sizeInBytes":230},"\u002Fuploads\u002Fsmall_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c.webp","small_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c","small_socks5-residential-proxy-guide-seomaster-draft-3.webp",20.1,281,20096,{"ext":69,"url":232,"hash":233,"mime":72,"name":234,"path":77,"size":235,"width":100,"height":236,"sizeInBytes":237},"\u002Fuploads\u002Fmedium_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c.webp","medium_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c","medium_socks5-residential-proxy-guide-seomaster-draft-3.webp",34.97,422,34970,{"ext":69,"url":239,"hash":240,"mime":72,"name":241,"path":77,"size":242,"width":108,"height":243,"sizeInBytes":244},"\u002Fuploads\u002Fthumbnail_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c.webp","thumbnail_socks5_residential_proxy_guide_seomaster_draft_3_3cab766a6c","thumbnail_socks5-residential-proxy-guide-seomaster-draft-3.webp",7.25,138,7250,"2026-06-17T12:33:37.635Z","zzswvp2i2gxv1c33hdgh9q0x",[248],{"text":116,"type":29},{"type":39,"level":183,"children":250},[251],{"text":252,"type":29},"`host`、`port`、`username`、`password` 分别怎么看",{"type":25,"children":254},[255],{"text":256,"type":29},"很多配置失败，不是代理资源本身有问题，而是字段含义没分清。先把这四项拆开看，再去测连接，排查会快很多。",{"type":61,"children":258},[259],{"text":260,"type":29},"| 字段 | 代表什么 | 一般怎么填 | 常见错误 |\n| --- | --- | --- | --- |\n| `host` | 代理服务器地址，也就是客户端实际连接的入口 | 按服务商提供的域名或 IP 原样填写 | 把目标网站域名填进来，或多复制了 `http:\u002F\u002F` 前缀 |\n| `port` | 对应协议开放的端口 | 填服务商给你的 `SOCKS5` 端口，不和 HTTP 端口混用 | 端口填错协议，或把多个端口规则混在一起测 |\n| `username` | 账号认证字段，常用来标识套餐、地区、会话参数或子账号 | 按服务商给出的用户名格式原样填写 | 漏填附加参数，或把别的协议账号直接照搬过来 |\n| `password` | 与用户名配套的认证密码 | 直接使用对应密码，注意前后不要带空格 | 复制时带了空格、换行，或和别的子账号密码混用 |",{"type":25,"children":262},[263],{"text":264,"type":29},"如果当前套餐走的是 IP 白名单而不是账号密码认证，那 `username` 和 `password` 可能为空；这种情况下，更该先确认本机出口 IP 是否已经被加入白名单，再判断是不是代理本身连不上。",{"type":25,"children":266},[267],{"text":268,"type":29},"如果你是在 Telegram、Google 或其他具体软件里配置，最好先用一组固定参数单独跑通，再去换国家、换资源或换认证方式。这样出问题时，更容易定位到底是工具适配、认证字段还是底层线路不稳。",{"type":39,"level":40,"children":270},[271],{"text":272,"type":29},"SOCKS5、静态住宅、动态住宅怎么组合选择",{"type":25,"children":274},[275],{"text":276,"type":29},"如果任务跑在 Telegram、指纹浏览器插件、桌面客户端或其他原生支持 `SOCKS5` 的环境里，先判断协议是否适配；如果是长期登录店铺、社媒主号、广告账户这类更看重身份连续性的任务，再优先看静态住宅代理IP；如果只是短时测试、批量采集、SERP 抓取或 SEO 监控，动态住宅通常更合适，因为它更适合按请求或按周期切换。`SOCKS5` 解决的是“怎么接进去”，静态住宅和动态住宅解决的是“出去之后像谁、能稳多久、多久换一次”。",{"type":25,"children":278},[279],{"text":280,"type":29},"很多选型失误，恰恰出在把 `SOCKS5` 误当成“更稳的住宅资源”。协议选对了，只代表工具能连上；如果底层 IP 仍然频繁轮换、地区不一致，或者共享噪声太高，会话照样跳变，验证码和二次验证也不会减少。更稳妥的判断顺序是先看工具支持什么协议，再看业务需要多稳定的身份和多快的切换节奏，最后再决定用静态住宅还是动态住宅。",{"type":39,"level":40,"children":282},[283],{"text":284,"type":29},"常见问题",{"type":39,"level":183,"children":286},[287],{"text":288,"type":29},"SOCKS5住宅代理和HTTP代理最核心的区别是什么？",{"type":25,"children":290},[291],{"text":292,"type":29},"先看流量类型，不先看名字。纯网页访问、常见浏览器请求，通常优先看 HTTP 或 HTTPS；客户端软件、非纯网页流量、需要更广协议兼容的场景，更常见 SOCKS5。要注意，SOCKS5 是协议层选择，不代表它天然比 HTTP 代理更稳，稳定性还取决于代理IP类型和资源质量。",{"type":39,"level":183,"children":294},[295],{"text":296,"type":29},"什么业务更适合先选 SOCKS5 代理？",{"type":25,"children":298},[299],{"text":300,"type":29},"客户端软件、社媒工具、浏览器外流量，以及不只是普通网页访问的任务，更适合先看 SOCKS5。它更常见于 Telegram 一类客户端场景，或需要兼容多种请求方式的业务。限制也很明确：如果你的任务只是网页登录、后台查看、基础页面访问，先上 SOCKS5 不一定比 HTTP\u002FHTTPS 更划算。",{"type":39,"level":183,"children":302},[303],{"text":304,"type":29},"协议和静态住宅、动态住宅到底是什么关系？",{"type":25,"children":306},[307],{"text":308,"type":29},"这不是同一层判断。SOCKS5、HTTP、HTTPS 说的是接入协议；静态住宅、动态住宅说的是 IP 资源的分配方式和使用特征。采购时要分开看：先判断你的业务需要长期稳定身份，还是高频切换；再判断软件或工具更适合哪种协议。",{"type":39,"level":183,"children":310},[311],{"text":312,"type":29},"配好 SOCKS5 还是不稳，先查什么问题？",{"type":25,"children":314},[315],{"text":316,"type":29},"先不要把问题都归到 SOCKS5 本身。先查当前工具是否真的支持 SOCKS5，再看地址、端口、账号密码等认证字段有没有填错，然后检查会话是否频繁中断、当前代理IP资源是否适合目标站点。很多“不稳”其实是工具适配、认证错误，或资源和业务场景错配，不只是协议问题。",{"type":25,"children":318},[319],{"text":320,"type":29},"---",{"type":25,"children":322},[323],{"text":324,"type":29},"如果你的任务已经明确更依赖 `SOCKS5` 协议兼容、客户端稳定接入和长期会话表现，下一步不要先比宣传口径，先拿目标国家和目标站点做小范围测试，重点看协议是否原生兼容、地区命中率、验证码频率、成功率和会话稳定性。若你准备直接评估支持 `SOCKS5\u002FHTTP` 的住宅代理资源，可以继续查看 [支持SOCKS5\u002FHTTP的全球静态住宅方案](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-native)，再按账号运营、店铺管理或社媒场景判断是否适合长期使用。",[326,541,812],{"source":6,"id":327,"documentId":328,"translationKey":328,"locale":9,"slug":329,"path":330,"_path":330,"title":331,"description":332,"excerpt":332,"image":333,"publishedAt":334,"updatedAt":335,"author":17,"tags":336,"featured":19,"sortOrder":20,"readingTime":337,"bodyType":22,"bodyBlocks":338,"bodyHtml":116},1450,"ju75n5vv4hql1x4q86c41glb","crawler-403-429-captcha-proxy-ip-troubleshooting","\u002Fblog\u002Fcrawler-403-429-captcha-proxy-ip-troubleshooting","爬虫一直 403、429 或验证码，代理 IP 要怎么排查？","这篇文章是 403、429、验证码主题下的爬虫场景子页，重点解决网页采集中的排查 SOP：先分清状态码和失败类型，再记录并发、重试、单 IP 请求量、UA、headers、Cookie、浏览器是否可复现和代理 IP 类型。只有在低频、完整请求环境下仍然集中失败时，才建议调整动态住宅、静态住宅或数据中心代理 IP 方案。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_SEO_6_2602763c1c.webp","2026-07-28T09:54:31.556Z","2026-07-28T09:54:31.535Z",[],6,[339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,427,431,435,439,443,447,451,455,459,463,467,471,475,479,483,487,490,494,498,502,506,510,514,518,522,526,530,534,538],{"type":25,"children":340},[341],{"text":342,"type":29},"爬虫一直出现 403、429 或验证码时，不要先急着扩大代理 IP 池。采集场景要先按状态码、请求频率、浏览器渲染、UA、headers、Cookie、会话一致性和代理 IP 类型逐项排查。若你需要先看所有代理使用场景的总判断顺序，可回到父页：[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)。本文只处理爬虫和网页采集里的专项 SOP。",{"type":39,"level":40,"children":344},[345],{"text":346,"type":29},"爬虫遇到 403、429 或验证码，先按这 6 步排查",{"type":25,"children":348},[349],{"text":350,"type":29},"遇到 403、429 或验证码时，不要只判断“代理 IP 好不好”。更稳的排查顺序是：",{"type":61,"children":352},[353],{"text":354,"type":29},"| 步骤 | 要确认的问题 | 记录什么 | 下一步判断 |\n| --- | --- | --- | --- |\n| 1. 分清错误类型 | 是 403、429、验证码、空页面、重定向还是超时 | 状态码、返回片段、出现页面 | 决定先查权限、频率还是环境 |\n| 2. 降低请求频率 | 是否并发过高、重试太密 | 并发数、重试次数、单 IP 请求量 | 低频恢复则优先改采集节奏 |\n| 3. 对比浏览器和程序 | 同一代理 IP 下浏览器是否正常 | 浏览器结果、程序结果、Cookie 状态 | 程序失败则查请求环境 |\n| 4. 补齐请求特征 | UA、headers、Referer、Cookie 是否合理 | 请求头、访问顺序、是否需要渲染 | 缺环境先补环境，不先换 IP |\n| 5. 检查会话一致性 | 是否频繁换 IP、换 UA、丢 Cookie | 会话、出口地区、账号或任务 ID | 会话混乱会提高验证码概率 |\n| 6. 再测代理类型 | 动态住宅、静态住宅、数据中心代理 IP 是否匹配 | 成功率、验证码位置、地区命中 | 低频仍失败再调整代理类型 |",{"type":25,"children":356},[357],{"text":358,"type":29},"低频请求恢复正常，优先调整并发、重试和退避策略；浏览器正常但程序失败，优先补齐 UA、headers、Cookie 和访问顺序；低频、完整请求环境下仍集中失败，再判断代理 IP 类型是否不匹配。403、429 和验证码在爬虫里分别指向哪些问题",{"type":25,"children":360},[361],{"text":362,"type":29},"爬虫排查要先看“失败类型”，再看“代理 IP 类型”。403、429 和验证码都可能和代理 IP 有关，但它们不是同一种问题。",{"type":39,"level":183,"children":364},[365],{"text":366,"type":29},"爬虫 403 不一定是代理 IP 被封",{"type":25,"children":368},[369],{"text":370,"type":29},"403 更常见于访问被拒绝，可能是权限、地区、UA、headers、Cookie、Referer、登录态、目标路径或目标站策略问题。它不一定说明代理 IP 被封，也可能是程序请求不像正常浏览器访问。",{"type":25,"children":372},[373],{"text":374,"type":29},"如果浏览器能打开，程序请求却 403，先对比程序是否带了必要请求头、Cookie、Referer 和访问顺序；如果目标页需要 JavaScript 渲染，普通 HTTP 请求可能拿不到正确内容。只有在请求环境已经接近浏览器、但某类出口仍集中 403 时，才进入代理 IP 类型对照。",{"type":39,"level":183,"children":376},[377],{"text":378,"type":29},"爬虫 429 先查频率、并发和失败重试",{"type":25,"children":380},[381],{"text":382,"type":29},"429 通常表示请求频率过高或触发限流。它更常和并发、重试、单 IP 请求量、短时间访问密度有关。继续堆代理 IP 不一定能解决，如果重试策略不改，更多 IP 也会被快速打满。",{"type":25,"children":384},[385],{"text":386,"type":29},"先把并发压低，拉开请求间隔，减少失败后立即重试，记录同一 IP 在单位时间内请求了多少次。如果 429 随低频测试明显下降，优先说明采集节奏是主因。",{"type":39,"level":183,"children":388},[389],{"text":390,"type":29},"验证码变多要同时看 IP 和程序行为",{"type":25,"children":392},[393],{"text":394,"type":29},"验证码说明目标站要求额外验证，常常是代理 IP 类型、访问频率、浏览器指纹、Cookie、行为轨迹共同触发。验证码突然变多时，不要只看“换不换动态住宅代理 IP”，还要看 UA 是否频繁变化、Cookie 是否丢失、访问顺序是否机械、同一会话是否频繁换出口。",{"type":39,"level":40,"children":396},[397],{"text":398,"type":29},"排查前先把失败样本记录清楚",{"type":25,"children":400},[401],{"text":402,"type":29},"排查时不要只写“失败”。建议把 403、429、验证码、空页面、字段缺失、重定向和超时分开记录。不同失败类型对应的处理方式不同，混在一起会让团队误以为只要换代理 IP 池就能解决。",{"type":25,"children":404},[405],{"text":406,"type":29},"建议记录这些字段：",{"type":61,"children":408},[409],{"text":410,"type":29},"| 字段 | 为什么要记录 |\n| --- | --- |\n| 目标站、URL、接口或页面类型 | 判断是公开页、登录页、搜索页还是接口限制 |\n| 状态码和返回片段 | 区分 403、429、验证码、重定向、空页面 |\n| 代理 IP 类型和出口地区 | 判断地区命中和出口类型是否影响结果 |\n| 并发数、重试次数、请求间隔 | 判断是否是频率或退避策略问题 |\n| UA、headers、Cookie、Referer | 判断程序请求是否缺少正常访问特征 |\n| 是否浏览器可复现 | 区分浏览器环境问题和程序请求问题 |\n| 会话或任务 ID | 判断是否多任务共用出口、会话是否混乱 |",{"type":25,"children":412},[413],{"text":414,"type":29},"如果 429 集中出现在高并发时段，优先查频率和退避策略；如果 403 只在程序请求里出现，优先查 headers、Cookie 和访问顺序；如果验证码随单 IP 请求量上升而增加，再进入代理 IP 类型和轮换策略测试。",{"type":39,"level":40,"children":416},[417],{"text":418,"type":29},"429 频繁出现时，先改并发、重试和单 IP 请求量",{"type":25,"children":420},[421],{"text":422,"type":29},"排查 429 时，先看请求频率、并发、重试和单 IP 请求量。很多 429 不是代理 IP 差，而是节奏太密。目标站如果对自动化访问敏感，应先降低频率、增加退避、减少无效重试、拆分任务和控制单会话请求量。否则换成住宅代理 IP，也可能只是把验证码延后出现。",{"type":25,"children":424},[425],{"text":426,"type":29},"建议做一个小样本对照：同一目标站、同一请求条件下，分别测试低频和高频、浏览器和程序、数据中心代理 IP 和住宅代理 IP。先确认是哪一类变量影响最大，再决定是否扩大代理 IP 采购。",{"type":39,"level":183,"children":428},[429],{"text":430,"type":29},"没确定触发原因前，先做小样本对照",{"type":25,"children":432},[433],{"text":434,"type":29},"在没有确定触发原因前，直接扩大代理 IP 池很容易把问题放大。更稳的做法是保持目标站、接口、UA、Cookie、请求间隔和并发不变，每次只改变一个变量，比如代理 IP 类型或单 IP 请求量。",{"type":25,"children":436},[437],{"text":438,"type":29},"一轮小样本至少要记录成功率、状态码分布、验证码出现位置、平均响应时间和结果完整度。只看“能不能打开”不够，因为很多采集问题是在连续翻页、批量查询或重复访问后才出现。",{"type":39,"level":40,"children":440},[441],{"text":442,"type":29},"浏览器能打开但程序 403，先查请求环境",{"type":25,"children":444},[445],{"text":446,"type":29},"浏览器能打开，不代表程序请求能通过。目标站可能检查 JavaScript 渲染、UA、headers、Accept-Language、Cookie、Referer、TLS 指纹、登录态和页面访问顺序。程序请求缺少这些信号时，代理 IP 正常也可能出现 403、空页面或验证码。",{"type":25,"children":448},[449],{"text":450,"type":29},"如果浏览器访问正常、程序访问 403，先补齐请求环境，而不是直接升级代理 IP。比如确认 UA 是否合理，headers 是否缺失，Cookie 是否过期，是否需要先访问首页再访问列表页，是否需要浏览器渲染。更细的程序端验证问题，可继续看[浏览器能打开但程序一直验证码怎么办](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowser-works-program-captcha-proxy)。",{"type":25,"children":452},[453],{"text":454,"type":29},"如果程序和浏览器都在同一代理 IP 下出现验证码，再看代理 IP 类型、地区命中、单 IP 使用强度和会话稳定性。采集 SOP 要把这些记录下来，而不是只记录“代理 IP 可用\u002F不可用”。",{"type":39,"level":40,"children":456},[457],{"text":458,"type":29},"低频访问仍然验证码很多，再判断代理 IP 类型是否匹配",{"type":25,"children":460},[461],{"text":462,"type":29},"如果低频访问仍然频繁出现验证码，且浏览器环境、headers、Cookie 和访问顺序都已经排查过，再重点看代理 IP 类型是否匹配。",{"type":61,"children":464},[465],{"text":466,"type":29},"| 采集条件 | 可先测试的代理 IP 类型 | 判断依据 |\n| --- | --- | --- |\n| 低风控公开页面、基础连通性测试 | 数据中心代理 IP | 看成本、速度和基础成功率 |\n| 多地区公开采集、价格监测、搜索结果采样 | 动态住宅代理 IP | 看地区命中、分散访问和验证码频率 |\n| 登录态、同一账号、长会话采集 | 静态住宅代理 IP | 看地区一致、会话连续和账号验证变化 |\n| 某类出口集中失败 | 换类型做对照 | 同地区、同请求条件下比较状态码分布 |",{"type":25,"children":468},[469],{"text":470,"type":29},"判断代理 IP 类型是否合适时，不要只看单次能不能打开页面。更有价值的是连续请求后的状态码分布、验证码出现位置、地区命中情况和单 IP 使用强度。如果同一套程序在低频、完整请求环境下仍然只对某类出口频繁失败，才说明需要调整代理 IP 类型。",{"type":39,"level":40,"children":472},[473],{"text":474,"type":29},"排查后什么时候该换动态住宅代理 IP",{"type":25,"children":476},[477],{"text":478,"type":29},"[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)适合多地区公开采集、价格监测、搜索结果采样和短会话轮换。它能分散访问来源，减少单一出口被用重的问题。",{"type":25,"children":480},[481],{"text":482,"type":29},"低风控公开站点或基础连通性测试，可以先用[数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdatacenter-proxy)验证成本。如果目标站对机房出口敏感、地区真实性要求高，或多轮后验证码明显增加，再测试动态住宅代理 IP。",{"type":25,"children":484},[485],{"text":486,"type":29},"涉及登录态、同一账号、长会话和稳定地区复查时，不要只靠频繁换 IP，应评估[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)。住宅和数据中心的取舍可继续看[数据采集用住宅代理 IP 还是数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fscraping-residential-vs-datacenter-proxy)。如果想先看通用排障，可参考[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)；如果问题已经进入批量代理 IP 管理和可用率监控，则应单独参考[大规模代理 IP 池](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Flarge-scale-proxy-ip-pool)的维护思路。",{"type":39,"level":40,"children":488},[489],{"text":284,"type":29},{"type":39,"level":183,"children":491},[492],{"text":493,"type":29},"爬虫 429 是代理 IP 被封了吗？",{"type":25,"children":495},[496],{"text":497,"type":29},"不一定。429 更常见于频率、并发、重试和目标站限流策略。先看请求节奏，再判断代理 IP 类型。如果低频、低并发下仍持续 429，再做不同代理 IP 类型和不同出口地区的对照。",{"type":39,"level":183,"children":499},[500],{"text":501,"type":29},"为什么浏览器能打开，爬虫请求却 403？",{"type":25,"children":503},[504],{"text":505,"type":29},"常见原因是程序请求环境不完整，例如缺少 Cookie、Referer、Accept-Language、访问顺序或必要渲染。先把程序请求和浏览器请求对齐，再判断是否需要调整代理 IP 类型。",{"type":39,"level":183,"children":507},[508],{"text":509,"type":29},"验证码突然变多，是不是该换动态住宅代理 IP？",{"type":25,"children":511},[512],{"text":513,"type":29},"不一定。先检查浏览器环境、UA、headers、Cookie、访问顺序、会话连续性和单 IP 请求量。动态住宅代理 IP 对短会话、多地区公开采集可能有帮助，但不能替代请求节奏和目标站规则排查。",{"type":39,"level":183,"children":515},[516],{"text":517,"type":29},"代理 IP 池越大，429 就越少吗？",{"type":25,"children":519},[520],{"text":521,"type":29},"不一定。如果失败后立即重试、并发峰值过高，或多个任务共用出口，扩大 IP 池只是把同样的问题复制到更多出口。先改频率和退避，再根据低频测试结果判断是否需要扩池。",{"type":39,"level":183,"children":523},[524],{"text":525,"type":29},"采集排查和普通代理 IP 连不上有什么不同？",{"type":25,"children":527},[528],{"text":529,"type":29},"采集 SOP 更关注状态码曲线、频率、headers、Cookie、会话和目标站策略；通用排障更关注协议、认证、连通性和代理 IP 配置。需要总排查路径时，可回到[代理出现 403、429、验证码时先查什么](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting)。",{"type":39,"level":183,"children":531},[532],{"text":533,"type":29},"做公开数据采集时，HTTP、HTTPS、SOCKS5 该怎么选？",{"type":25,"children":535},[536],{"text":537,"type":29},"按目标站和程序支持选择。先保证协议、认证和 DNS 行为正确，再比较代理 IP 类型和地区命中。协议选错会导致程序部分请求没走代理 IP，容易把接入问题误判成资源问题。",{"type":25,"children":539},[540],{"text":116,"type":29},{"source":6,"id":542,"documentId":543,"translationKey":543,"locale":9,"slug":544,"path":545,"_path":545,"title":546,"description":547,"excerpt":547,"image":548,"publishedAt":549,"updatedAt":550,"author":17,"tags":551,"featured":19,"sortOrder":20,"readingTime":337,"bodyType":22,"bodyBlocks":552,"bodyHtml":116},1449,"i39t4afhr6uktwvdjmm258fz","proxy-403-429-captcha-troubleshooting","\u002Fblog\u002Fproxy-403-429-captcha-troubleshooting","代理出现 403、429、验证码时先查什么？","这篇文章作为 403、429 和验证码总排查父页，重点讲代理 IP 使用中出现访问失败时的判断顺序：先区分权限、地区限制、请求频率、并发重试、账号状态和浏览器\u002F程序环境差异，再判断问题是否真的来自代理出口或代理 IP 类型。公开采集、程序验证码、Cloudflare\u002FTurnstile、长期账号登录等细分问题，应通过对应子页继续排查。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_cover_afc3715177.webp","2026-07-28T09:54:09.337Z","2026-07-28T09:54:09.314Z",[],[553,557,561,565,569,573,577,581,585,589,593,597,601,643,647,651,655,659,663,667,671,675,679,683,687,691,695,699,703,707,711,715,719,723,727,731,735,739,743,747,751,755,759,763,767,770,774,778,782,786,790,794,798,802,805,809],{"type":25,"children":554},[555],{"text":556,"type":29},"代理出现 403、429 或验证码时，先不要只换代理 IP。更有效的顺序是：先区分 403、429、验证码分别代表什么，再看目标站规则、请求频率、浏览器与程序差异、账号状态和代理 IP 类型是否匹配。若问题发生在爬虫或网页采集任务里，可以继续看[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)；本文先作为通用父页，解决所有代理使用场景里的总排查顺序。",{"type":39,"level":40,"children":558},[559],{"text":560,"type":29},"代理出现 403、429、验证码分别可能代表什么",{"type":25,"children":562},[563],{"text":564,"type":29},"先把 403、429、验证码拆开看：403 多查权限、地区限制、请求特征和账号状态；429 多查频率、并发、失败重试和多人共用出口；验证码变多则要同时看浏览器环境、会话连续性、地区跳变、账号状态和代理 IP 类型。把三类现象混成一句“代理不能用”，后续排查会很难归因。",{"type":61,"children":566},[567],{"text":568,"type":29},"| 现象 | 更常见的原因 | 第一轮先查什么 | 适合继续看的页面 |\n| --- | --- | --- | --- |\n| 403 | 权限、地区、请求特征或账号状态被拒 | 登录状态、目标路径、请求头、Cookie、出口地区 | 程序请求差异、Cloudflare\u002FTurnstile 专项 |\n| 429 | 请求频率、并发、重试或共享出口过高 | 单 IP 请求量、并发峰值、失败后重试、任务是否共用出口 | 爬虫 403\u002F429\u002F验证码专项 |\n| 验证码变多 | 环境可信度下降或验证层级升高 | 账号、设备、浏览器指纹、地区跳变、会话中断 | 程序验证码、账号登录稳定性文章 |\n| 只有某类代理 IP 异常 | 目标站对出口类型更敏感 | 同国家不同类型出口对照、地区命中、IP 使用强度 | 动态住宅、静态住宅、数据中心代理 IP 选型 |",{"type":39,"level":183,"children":570},[571],{"text":572,"type":29},"403 不一定是代理 IP 被封",{"type":25,"children":574},[575],{"text":576,"type":29},"同一代理 IP 在浏览器正常、程序却 403，先查请求头、Cookie、TLS 指纹、目标路径权限和登录状态。这类情况更像请求特征不完整，不一定是 IP 被封。若只在某些国家或数据中心代理 IP 上反复出现，再看地区限制、IP 信誉和目标站对出口类型的风控力度。遇到 Cloudflare、Turnstile 或循环验证，可转到 [Cloudflare Turnstile 验证失败怎么选代理 IP 更稳](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fcloudflare-turnstile-verification-failure-proxy-ip-selection) 继续排查。",{"type":39,"level":183,"children":578},[579],{"text":580,"type":29},"429 先看频率和出口共用",{"type":25,"children":582},[583],{"text":584,"type":29},"429 更常见的是频率、并发和重试失控。先核对单位时间请求数、失败后是否立即重试、多个任务是否共用同一出口；这些问题不改，换更多代理 IP 只会把限流扩散成更高成本。若是公开页面采集、批量查询或爬虫任务，应进入[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)做更细的 SOP。",{"type":39,"level":183,"children":586},[587],{"text":588,"type":29},"验证码变多说明验证层级在上升",{"type":25,"children":590},[591],{"text":592,"type":29},"首次就出验证码，多半是访问行为、浏览器环境或出口类型让目标站觉得可疑；操作几轮后明显变多，常见于地区跳变、会话中断、账号状态异常、多人共用出口，或把动态住宅代理 IP 用在长期登录场景。先记录验证码出现页面、时间、账号、代理 IP 类型和请求方式，再决定是补环境、降频，还是调整代理 IP 方案。",{"type":39,"level":40,"children":594},[595],{"text":596,"type":29},"先判断这是哪一种任务，不要直接扩大代理 IP 池",{"type":25,"children":598},[599],{"text":600,"type":29},"同样是 403、429 或验证码，公开页采集、登录后台、API 请求、多地区检查的根因并不一样。排障第一步不是采购更多代理 IP，而是把任务场景、错误类型和触发时间记录清楚，再做小样本对照。",{"type":66,"image":602,"children":641},{"id":603,"ext":69,"url":604,"hash":605,"mime":72,"name":606,"size":607,"width":608,"height":609,"caption":77,"formats":610,"provider":111,"createdAt":639,"updatedAt":639,"documentId":640,"focalPoint":77,"previewUrl":77,"publishedAt":639,"alternativeText":77,"provider_metadata":77},1155,"https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",64.66,2732,882,{"large":611,"small":618,"medium":625,"thumbnail":632},{"ext":69,"url":612,"hash":613,"mime":72,"name":614,"path":77,"size":615,"width":84,"height":616,"sizeInBytes":617},"\u002Fuploads\u002Flarge_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","large_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","large_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",19.66,323,19658,{"ext":69,"url":619,"hash":620,"mime":72,"name":621,"path":77,"size":622,"width":92,"height":623,"sizeInBytes":624},"\u002Fuploads\u002Fsmall_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","small_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","small_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",7.4,161,7404,{"ext":69,"url":626,"hash":627,"mime":72,"name":628,"path":77,"size":629,"width":100,"height":630,"sizeInBytes":631},"\u002Fuploads\u002Fmedium_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","medium_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","medium_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",13.37,242,13374,{"ext":69,"url":633,"hash":634,"mime":72,"name":635,"path":77,"size":636,"width":108,"height":637,"sizeInBytes":638},"\u002Fuploads\u002Fthumbnail_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5.webp","thumbnail_proxy_403_429_captcha_troubleshooting_1_02a7228f9cea_3ada4e0fc5","thumbnail_proxy-403-429-captcha-troubleshooting-1-02a7228f9cea.webp",2.14,79,2136,"2026-07-28T08:26:28.559Z","snwy3vvzk2l0ykdyjx8pi82s",[642],{"text":116,"type":29},{"type":61,"children":644},[645],{"text":646,"type":29},"| 任务类型 | 容易出现的限制 | 先做的动作 | 建议承接 |\n| --- | --- | --- | --- |\n| 公开页面采集 | 429、验证码、字段缺失 | 降低并发、拉开重试、记录单 IP 请求量 | 爬虫专项排查页 |\n| 浏览器能打开但程序失败 | 403、空页面、程序端验证码 | 对比 headers、Cookie、渲染、代理接入方式 | 程序验证码排查页 |\n| 登录后台或账号任务 | 验证码、二次验证、权限收紧 | 查账号状态、地区一致性、设备和 Cookie | 静态住宅代理 IP 选型 |\n| API 或程序请求 | 429、403、token 限制 | 区分账号\u002Ftoken\u002Fendpoint 限流和出口共用 | 留样后再判断代理类型 |",{"type":39,"level":183,"children":648},[649],{"text":650,"type":29},"公开页面采集先降频，再进入爬虫子页",{"type":25,"children":652},[653],{"text":654,"type":29},"公开页面采集遇到 403、429 或验证码，先把并发、重试和同一 IP 的单位时间请求量压低，观察 429 与验证码是否明显下降。若降频后恢复，说明目标站限流更关键；这时盲目扩大 IP 池，只会把成本放大。采集场景里的 headers、Cookie、渲染、会话和动态住宅代理 IP 使用边界，建议继续看[爬虫一直 403、429 或验证码，代理 IP 要怎么排查](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fweb-scraping-403-429-captcha-proxy)。",{"type":39,"level":183,"children":656},[657],{"text":658,"type":29},"登录后台先查账号状态，不要只查代理 IP",{"type":25,"children":660},[661],{"text":662,"type":29},"店铺后台、广告后台、社媒账号和长期登录任务，更常见的是账号近期频繁换地区、改密码、切 Cookie、换设备或登录方式变化，随后验证层级上升。此时即使用更高成本的住宅代理 IP，也可能继续异常。代理 IP 能改善网络出口和地区一致性，不能替代账号合规运营、设备稳定和平台规则。",{"type":39,"level":183,"children":664},[665],{"text":666,"type":29},"API 或程序请求要区分目标站限流和出口共用",{"type":25,"children":668},[669],{"text":670,"type":29},"如果限制落在账号、token、接口路径或时间窗口，换代理 IP 只能部分缓解，改不了接口规则。另一类问题是多个任务共用同一出口，聚合后频率过高，429 会集中出现。排查时至少保留账号或 token 类型、目标 URL、代理 IP 类型、出口国家、请求方式、状态码、返回片段、并发和时间窗口。",{"type":39,"level":40,"children":672},[673],{"text":674,"type":29},"浏览器能打开但程序失败，采购代理 IP 前先查哪些差异",{"type":25,"children":676},[677],{"text":678,"type":29},"人工点开页面，不等于程序也具备同样访问条件。浏览器会自动处理 Cookie、重定向、JS 执行、缓存、语言、时区和部分安全挑战；程序如果只发基础请求，常见结果就是 403、空白页，或浏览器能打开但程序验证码更密。这个问题应优先按请求环境排查，不要直接算成代理 IP 不稳。",{"type":39,"level":183,"children":680},[681],{"text":682,"type":29},"同一个代理 IP 在浏览器和程序里表现不同，先查接入方式",{"type":25,"children":684},[685],{"text":686,"type":29},"确认程序是否真的完整走了代理 IP。HTTP、HTTPS、SOCKS5 的适配差异、认证方式、DNS 解析和超时设置，只要有一处和浏览器不同，就可能出现页面能开、接口失败，或静态资源绕过代理后暴露本地网络特征。更细的程序端排查，可继续看[浏览器能打开但程序一直验证码怎么办](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fbrowser-works-program-captcha-proxy)。",{"type":39,"level":183,"children":688},[689],{"text":690,"type":29},"程序端验证码更密时，先看行为信号",{"type":25,"children":692},[693],{"text":694,"type":29},"瞬时并发高、失败后立即重试、固定节奏过于机械，或多个账号共用同一会话，都会让验证层级上升：先偶发验证码，再变成高频验证，最后可能直接拦截。此时盲目加动态住宅代理 IP，成本会上去，结果未必改善。更稳妥的判断，是先降频、拆分会话、补齐请求环境，再决定是否调整代理 IP 类型。",{"type":39,"level":40,"children":696},[697],{"text":698,"type":29},"动态住宅、数据中心、静态住宅代理 IP 怎么选",{"type":25,"children":700},[701],{"text":702,"type":29},"代理触发验证码后怎么选 IP 类型，别从“哪种更高级”开始，而要先看任务是不是短会话、是否频繁换地区、是否需要长期保持同一身份。类型选反了，常见结果不是慢一点，而是验证码先变多，再变成权限收紧。",{"type":61,"children":704},[705],{"text":706,"type":29},"| 任务条件 | 优先考虑 | 原因 | 不适合的情况 |\n| --- | --- | --- | --- |\n| 多地区公开采集、SEO 监控、市场调研 | 动态住宅代理 IP | 更适合短会话、多地区、分散访问 | 长期登录、同一账号持续会话 |\n| 公开页面、低风控、重速度或成本 | 数据中心代理 IP | 成本和速度更容易控制 | 目标站明显排斥机房出口 |\n| 店铺后台、广告后台、社媒账号、长期登录 | 静态住宅代理 IP | 更利于地区一致和会话连续 | 账号行为异常时不能单独解决验证 |\n| 高敏感账号、地区一致性要求更高 | 原生静态住宅代理 IP | 更适合对网络身份要求更高的长期任务 | 短时采样或频繁轮换任务 |",{"type":39,"level":183,"children":708},[709],{"text":710,"type":29},"哪些任务更适合动态住宅代理 IP",{"type":25,"children":712},[713],{"text":714,"type":29},"做多地区落地页检查、公开采集、SEO 监控或市场调研时，可以优先评估[动态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdynamic-residential)。这类任务需要分散访问，动态住宅代理 IP 更容易把出口打散，减少多人共用同一出口后的聚合风险。短板也要看清：如果拿它去跑长期账号、店铺后台或持续登录，出口频繁变化会让平台不断识别为新环境，验证码可能从偶发变成高频。",{"type":39,"level":183,"children":716},[717],{"text":718,"type":29},"什么时候值得先测数据中心代理 IP",{"type":25,"children":720},[721],{"text":722,"type":29},"访问公开页面、目标站风控力度较轻、计费模式又卡得紧时，可以先小量测试[数据中心代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fdatacenter-proxy)。它更适合速度和成本优先的任务，但不适合对住宅属性敏感的平台。若 403 和验证码集中出现，继续堆同类 IP 资源通常只会放大失败样本，这时应先换动态住宅代理 IP 做对照。",{"type":39,"level":183,"children":724},[725],{"text":726,"type":29},"长期账号和稳定地区为什么更该看静态住宅代理 IP",{"type":25,"children":728},[729],{"text":730,"type":29},"登录后台、社媒运营、电商店铺这类持续会话，更看重地区一致、出口稳定和身份连续，[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard)更合适。原因不在“更贵”，而在它能减少地区跳变和重复校验。限制也要看清：账号近期改密、频繁切 Cookie 或操作节奏异常时，即使用静态住宅代理 IP，验证码和限制也不会自动消失。",{"type":39,"level":40,"children":732},[733],{"text":734,"type":29},"快速判断：403、429 和验证码出现后，该不该马上换代理 IP",{"type":39,"level":183,"children":736},[737],{"text":738,"type":29},"403 出现后就换代理 IP 吗",{"type":25,"children":740},[741],{"text":742,"type":29},"不一定。先排查账号权限、地区限制、请求特征和登录状态；若这些没问题，再对比更换代理 IP。只换出口不改访问方式，403 往往会继续出现。",{"type":39,"level":183,"children":744},[745],{"text":746,"type":29},"429 出现后要不要继续加 IP 资源",{"type":25,"children":748},[749],{"text":750,"type":29},"多数时候先别加。先降频、拉开重试间隔、拆分并发，再看是否仍集中触发；否则只会把限流从单一出口扩散到更多 IP 资源。",{"type":39,"level":183,"children":752},[753],{"text":754,"type":29},"浏览器正常，为什么程序里验证码更多",{"type":25,"children":756},[757],{"text":758,"type":29},"更常见是程序请求环境、接入方式或会话保持不一致。先校验请求头、Cookie、代理接入和访问节奏，再判断是否要换代理 IP；否则容易误把行为问题当成 IP 问题。",{"type":39,"level":183,"children":760},[761],{"text":762,"type":29},"动态住宅、数据中心、静态住宅代理 IP 怎么挑",{"type":25,"children":764},[765],{"text":766,"type":29},"短会话分散访问优先动态住宅代理 IP；公开页面、低风控且重成本，可先测数据中心代理 IP；长期登录、稳定地区和持续会话，更适合静态住宅代理 IP。",{"type":39,"level":40,"children":768},[769],{"text":284,"type":29},{"type":39,"level":183,"children":771},[772],{"text":773,"type":29},"怎么判断问题来自账号、目标站规则，还是代理出口？",{"type":25,"children":775},[776],{"text":777,"type":29},"做一次小量对照：同一账号、同一路径、同一请求方式下，只更换一个变量。如果换账号恢复，优先查账号状态；如果同账号在不同出口都失败，优先查目标站权限、token 或路径规则；如果只在某类代理 IP 上集中失败，再考虑出口信誉、地区限制或代理类型不匹配。",{"type":39,"level":183,"children":779},[780],{"text":781,"type":29},"排查 403、429、验证码时，应该留哪些样本给售后？",{"type":25,"children":783},[784],{"text":785,"type":29},"至少保留时间、目标 URL、账号或 token 类型、代理 IP 类型、出口国家、请求方式、状态码、返回片段、是否浏览器可复现、并发和重试策略。只说“不能用”很难判断根因；有这些样本，服务商才更容易区分是接入配置、目标站规则、频率过高，还是代理出口异常。",{"type":39,"level":183,"children":787},[788],{"text":789,"type":29},"为什么同一个代理 IP 上午正常，下午就开始异常？",{"type":25,"children":791},[792],{"text":793,"type":29},"先看是否有频率累积、多人共用出口、账号操作变化或目标站风控窗口变化。短时间内请求量升高、失败后连续重试、频繁切换地区，都会让同一出口的风险评分变化；这类问题不能只按“IP 突然坏了”处理。",{"type":39,"level":183,"children":795},[796],{"text":797,"type":29},"测试代理 IP 时，怎样避免把接入问题误判成资源问题？",{"type":25,"children":799},[800],{"text":801,"type":29},"先用一个明确目标站、一个稳定国家、少量并发和短时间窗口测试，确认协议、认证、DNS、超时和程序代理配置都一致。测试还没跑通前，不要同时换国家、换代理类型、改程序参数和提高并发，否则结果很难归因。",{"type":25,"children":803},[804],{"text":320,"type":29},{"type":25,"children":806},[807],{"text":808,"type":29},"排查 403、429 和验证码时，先区分目标站限制、请求频率过高、账号状态异常，还是浏览器与程序访问环境不一致。只有根因接近代理出口、地区一致性或 IP 类型错配时，换动态住宅代理 IP、静态住宅代理 IP 或数据中心代理 IP 才更有意义。",{"type":25,"children":810},[811],{"text":116,"type":29},{"source":6,"id":813,"documentId":814,"translationKey":814,"locale":9,"slug":815,"path":816,"_path":816,"title":817,"description":818,"excerpt":818,"image":819,"publishedAt":820,"updatedAt":821,"author":17,"tags":822,"featured":19,"sortOrder":20,"readingTime":823,"bodyType":22,"bodyBlocks":824,"bodyHtml":116},1447,"yjl0wy95ir38uvf7jl59e3xh","proxy-reseller-commission-vs-resale","\u002Fblog\u002Fproxy-reseller-commission-vs-resale","代理 IP 分佣模式和转售模式有什么区别？","分佣和转售是两种代理合作模式。分佣通常侧重推荐成交和收益分配，转售通常侧重报价空间、套餐组合和客户协作方式，但售前、售后和技术支持责任并不固定，也不是由客户规模单独决定，应按工具支持、使用习惯和具体合作约定确认。判断清楚合作方向后，可以通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再进一步确认申请方式、合作模式和服务分工。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_ip_cover_32c9b152ca.webp","2026-07-28T09:51:53.949Z","2026-07-28T09:51:53.930Z",[],4,[825,829,833,837,841,845,849,853,857,861,865,869,873,877,881,885,889,893,897,901,905,909,913,917,921,925,950,954,958,962,966,970,974,978],{"type":25,"children":826},[827],{"text":828,"type":29},"很多代理商在谈合作时会把代理 IP 分佣模式和转售模式混在一起：都能带来收益，也都和客户成交有关，但真正影响后续合作体验的是客户归属、定价权、结算方式和售前售后协作。简单判断，分佣模式通常更侧重推荐成交后的收益分配，转售模式通常更侧重代理商是否拥有自主报价、套餐组合或客户经营空间。至于售前咨询、技术排障和复杂售后由谁承担，并不是模式天然决定的，也不是由客户规模单独决定的，要以工具支持方式、平台规则、代理商使用习惯和双方合作约定为准。如果你已经在评估代理 IP 合作，可以先通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)了解申请方式、适合人群和合作流程，再结合本文判断更适合分佣还是转售。",{"type":39,"level":40,"children":830},[831],{"text":832,"type":29},"两种合作方式怎么快速区分",{"type":25,"children":834},[835],{"text":836,"type":29},"分佣模式看推荐是否有效、成交如何归因、收益如何结算；转售模式看是否有转售价格空间、套餐组合方式、客户归属和后续协作规则。两者都可以约定不同的售前售后分工，不宜只用“谁承担服务”来判断模式。",{"type":61,"children":838},[839],{"text":840,"type":29},"| 判断项 | 分佣模式重点 | 转售模式重点 |\n| --- | --- | --- |\n| 客户来源 | 谁推荐、如何记录、归属有效期多久 | 是否由代理商持续经营客户、是否允许二次分销 |\n| 收益口径 | 分佣比例、有效订单、结算周期 | 进货成本、转售定价权、续费归属 |\n| 客户关系 | 可偏线索推荐和成交归因，也可约定后续跟进 | 可偏客户经营、复购和套餐组合，也可由平台继续参与服务 |\n| 售前售后 | 可由平台承接更多成交和技术支持，也可约定代理商协助解释 | 可由代理商承接，也可由平台和代理商分工协作，取决于工具支持和合作约定 |\n| 风险边界 | 不把推荐成交写成长期收益保证 | 不把客户业务结果包装成平台承诺 |\n| 下一步动作 | 适合先申请代理商合作，确认分佣归因、结算周期和客户跟进方式 | 适合申请代理商合作后，与商务确认转售价格空间、客户管理和售后分工 |",{"type":39,"level":40,"children":842},[843],{"text":844,"type":29},"代理 IP 分佣模式适合什么样的代理商",{"type":25,"children":846},[847],{"text":848,"type":29},"分佣型适合有推荐能力，希望先从线索推荐和成交归因开始合作的人。常见情况包括有行业内容渠道、社群资源、客户线索、咨询入口，或者能把有代理 IP 需求的客户推荐给平台承接。",{"type":25,"children":850},[851],{"text":852,"type":29},"比如你运营着一个跨境电商社群，群里经常有人问去哪买住宅代理IP，但你暂时只想先做推荐和线索转化，不想马上设计套餐、报价和客户管理流程，这种情况更适合先走分佣。",{"type":25,"children":854},[855],{"text":856,"type":29},"这种模式的重点不是自己定价，而是先验证客户需求和线索质量。具体结算细节见下文“结算和退款影响怎么确认”。如果你目前主要有社群、内容、客户线索或咨询入口，但还不想自己搭建报价和售后流程，可以先从[代理商合作入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再确认分佣归因、结算周期和客户跟进方式。",{"type":39,"level":40,"children":858},[859],{"text":860,"type":29},"转售模式适合什么样的团队",{"type":25,"children":862},[863],{"text":864,"type":29},"转售型更适合希望自主报价、组合套餐，或把代理 IP 和自身服务方案一起交付的团队。它不是简单“拿货再卖”，核心在于是否需要更灵活地组织价格、产品包、客户入口和交付流程。报价解释、产品边界说明、客户预期管理、续费提醒和问题升级路径可以由代理商承担，也可以由平台和代理商按约定分工。",{"type":25,"children":866},[867],{"text":868,"type":29},"客户数量不是唯一标准，也不是转售的前置门槛。即使客户规模不大，只要你的工具、业务流程或客户使用习惯更适合自己报价、组合套餐、统一收款或统一交付，也可以评估转售；如果已经有一批长期采购客户，并且能回答“登录异常先查什么”“测试失败怎么反馈”这类基础问题，只是会让转售推进更顺。",{"type":25,"children":870},[871],{"text":872,"type":29},"转售的收益空间通常更依赖报价组织、套餐设计和协作管理能力。团队可以围绕客户需求组织报价和服务，但不代表所有售前售后都必须自己承担。更关键的是提前形成清晰口径：客户为什么选择某类代理 IP、测试资源如何使用、续费价格是否变化、遇到连接或业务问题时先由谁排查、哪些问题升级给平台。",{"type":25,"children":874},[875],{"text":876,"type":29},"如果这些问题没有提前确认，后续容易把“客户是谁的”“谁来解释产品”“退款是否影响结算”混在一起。代理 IP 本身只解决出口环境，不能替代理商承担客户业务结果。如果你已经有客户管理、套餐组合或统一交付需求，建议通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)进入合作沟通，重点确认转售价格空间、续费归属、售后升级路径和客户边界。",{"type":39,"level":40,"children":878},[879],{"text":880,"type":29},"售前售后责任不是固定模板",{"type":25,"children":882},[883],{"text":884,"type":29},"分佣和转售只是合作模式，不等于售前售后责任已经天然确定。实际合作中，可以约定由平台负责产品介绍、技术排障和资源问题，也可以由代理商负责客户沟通、基础解释、续费提醒，再由平台处理复杂问题。反过来，分佣方也可能参与客户跟进，转售方也可以把部分售前售后交给平台协作，关键看工具能支持什么、双方怎么约定，以及代理商习惯用什么方式管理客户。",{"type":25,"children":886},[887],{"text":888,"type":29},"判断时不要只问“分佣还是转售”，还要问清楚：谁负责售前咨询，谁解释套餐边界，谁处理连接失败，谁收集客户报错，谁负责续费提醒，哪些问题需要升级给平台。",{"type":39,"level":40,"children":890},[891],{"text":892,"type":29},"定价、售后和结算分别怎么确认",{"type":39,"level":183,"children":894},[895],{"text":896,"type":29},"定价权看什么",{"type":25,"children":898},[899],{"text":900,"type":29},"定价权不只是能不能自己报价，还包括折扣空间、续费价格、测试资源和退款影响。分佣模式通常按平台或商务规则执行；转售模式则要提前确认是否能自行报价、是否需要遵守最低价格，以及价格变化时由谁通知客户。",{"type":39,"level":183,"children":902},[903],{"text":904,"type":29},"售后责任怎么分",{"type":25,"children":906},[907],{"text":908,"type":29},"售后责任要看合作约定，而不是只看模式名称。分佣方可以只做线索解释，也可以协助基础沟通；转售方可以承担客户经营和续费提醒，也可以把资源、后台、认证和复杂技术问题升级给平台处理。涉及服务边界时，可以再对照[代理商售后责任分工](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-after-sales-responsibility)。",{"type":39,"level":183,"children":910},[911],{"text":912,"type":29},"结算和退款影响怎么确认",{"type":25,"children":914},[915],{"text":916,"type":29},"结算前要确认有效订单、结算周期、客户归属有效期、退款是否扣减分佣，以及续费是否继续计算收益。退款或业务失败不能直接等同于平台责任，必须回到订单、资源状态、配置问题和客户业务结果边界来判断。",{"type":39,"level":40,"children":918},[919],{"text":920,"type":29},"合作前要准备哪些信息",{"type":25,"children":922},[923],{"text":924,"type":29},"进入合作沟通前，建议先把客户来源、推广记录、预计用量、工具支持方式、使用习惯和结算诉求整理清楚。准备越具体，越容易判断适合分佣还是转售。",{"type":926,"format":927,"children":928},"list","unordered",[929,934,938,942,946],{"type":930,"children":931},"list-item",[932],{"text":933,"type":29},"客户来源、推广链接或首次沟通记录是否可追溯。",{"type":930,"children":935},[936],{"text":937,"type":29},"分佣比例、结算周期、有效订单和退款影响是否明确。",{"type":930,"children":939},[940],{"text":941,"type":29},"转售方是否拥有报价权、套餐组合权、续费沟通权，以及售前售后如何分工。",{"type":930,"children":943},[944],{"text":945,"type":29},"售前解释、基础排障和平台升级支持分别由谁承接。",{"type":930,"children":947},[948],{"text":949,"type":29},"是否已写清不能承诺解封、过审、KYC 或采集成功。",{"type":25,"children":951},[952],{"text":953,"type":29},"准备好这些信息后，下一步不是继续纠结名称，而是进入[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向。平台侧会根据客户来源、合作方式、预期用量和服务分工，进一步确认更适合分佣、转售，还是先从轻量推荐合作开始。涉及归因规则时，再单独确认[客户归属管理](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-customer-attribution)；如果需要完整合作前清单，可以再查看[代理商合作指南](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-reseller-program-guide)。",{"type":39,"level":40,"children":955},[956],{"text":957,"type":29},"FAQ",{"type":39,"level":183,"children":959},[960],{"text":961,"type":29},"转售一定可以自己定价吗？",{"type":25,"children":963},[964],{"text":965,"type":29},"转售方是否可以自己定价，取决于合作协议、产品成本、品牌展示方式和售后责任划分。",{"type":39,"level":183,"children":967},[968],{"text":969,"type":29},"客户归属争议怎么处理？",{"type":25,"children":971},[972],{"text":973,"type":29},"客户归属争议优先回到推广链接、后台记录、首次有效沟通和商务确认规则。",{"type":39,"level":183,"children":975},[976],{"text":977,"type":29},"不确定选分佣还是转售，可以先申请代理商吗？",{"type":25,"children":979},[980],{"text":981,"type":29},"可以。合作前不一定要先把模式完全确定好，建议先通过[代理商入口](https:\u002F\u002Fwww.quanqiudaili.com\u002Fagent)提交合作意向，再根据客户来源、报价需求、售后能力和结算诉求确认合作方式。",[983],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":984,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":985,"bodyHtml":116},[],[986,989,992,995,998,1001,1004,1007,1010,1013,1022,1025,1028,1031,1040,1043,1046,1049,1052,1055,1058,1061,1064,1067,1070,1079,1082,1085,1088,1091,1094,1097,1100,1103,1106,1109,1112,1115,1118,1121,1124,1127,1130,1133],{"type":25,"children":987},[988],{"text":28,"type":29},{"type":25,"children":990},[991],{"text":33,"type":29},{"type":25,"children":993},[994],{"text":37,"type":29},{"type":39,"level":40,"children":996},[997],{"text":43,"type":29},{"type":25,"children":999},[1000],{"text":47,"type":29},{"type":25,"children":1002},[1003],{"text":51,"type":29},{"type":39,"level":40,"children":1005},[1006],{"text":55,"type":29},{"type":25,"children":1008},[1009],{"text":59,"type":29},{"type":61,"children":1011},[1012],{"text":64,"type":29},{"type":66,"image":1014,"children":1020},{"id":68,"ext":69,"url":70,"hash":71,"mime":72,"name":73,"size":74,"width":75,"height":76,"caption":77,"formats":1015,"provider":111,"createdAt":112,"updatedAt":112,"documentId":113,"focalPoint":77,"previewUrl":77,"publishedAt":112,"alternativeText":77,"provider_metadata":77},{"large":1016,"small":1017,"medium":1018,"thumbnail":1019},{"ext":69,"url":80,"hash":81,"mime":72,"name":82,"path":77,"size":83,"width":84,"height":85,"sizeInBytes":86},{"ext":69,"url":88,"hash":89,"mime":72,"name":90,"path":77,"size":91,"width":92,"height":93,"sizeInBytes":94},{"ext":69,"url":96,"hash":97,"mime":72,"name":98,"path":77,"size":99,"width":100,"height":101,"sizeInBytes":102},{"ext":69,"url":104,"hash":105,"mime":72,"name":106,"path":77,"size":107,"width":108,"height":109,"sizeInBytes":110},[1021],{"text":116,"type":29},{"type":39,"level":40,"children":1023},[1024],{"text":120,"type":29},{"type":25,"children":1026},[1027],{"text":124,"type":29},{"type":25,"children":1029},[1030],{"text":128,"type":29},{"type":66,"image":1032,"children":1038},{"id":131,"ext":69,"url":132,"hash":133,"mime":72,"name":134,"size":135,"width":75,"height":136,"caption":77,"formats":1033,"provider":111,"createdAt":162,"updatedAt":162,"documentId":163,"focalPoint":77,"previewUrl":77,"publishedAt":162,"alternativeText":77,"provider_metadata":77},{"large":1034,"small":1035,"medium":1036,"thumbnail":1037},{"ext":69,"url":139,"hash":140,"mime":72,"name":141,"path":77,"size":142,"width":84,"height":85,"sizeInBytes":143},{"ext":69,"url":145,"hash":146,"mime":72,"name":147,"path":77,"size":148,"width":92,"height":93,"sizeInBytes":149},{"ext":69,"url":151,"hash":152,"mime":72,"name":153,"path":77,"size":154,"width":100,"height":101,"sizeInBytes":155},{"ext":69,"url":157,"hash":158,"mime":72,"name":159,"path":77,"size":160,"width":108,"height":109,"sizeInBytes":161},[1039],{"text":116,"type":29},{"type":39,"level":40,"children":1041},[1042],{"text":169,"type":29},{"type":25,"children":1044},[1045],{"text":173,"type":29},{"type":25,"children":1047},[1048],{"text":177,"type":29},{"type":39,"level":40,"children":1050},[1051],{"text":181,"type":29},{"type":39,"level":183,"children":1053},[1054],{"text":186,"type":29},{"type":25,"children":1056},[1057],{"text":190,"type":29},{"type":25,"children":1059},[1060],{"text":194,"type":29},{"type":39,"level":183,"children":1062},[1063],{"text":198,"type":29},{"type":25,"children":1065},[1066],{"text":202,"type":29},{"type":25,"children":1068},[1069],{"text":206,"type":29},{"type":66,"image":1071,"children":1077},{"id":209,"ext":69,"url":210,"hash":211,"mime":72,"name":212,"size":213,"width":214,"height":215,"caption":77,"formats":1072,"provider":111,"createdAt":245,"updatedAt":245,"documentId":246,"focalPoint":77,"previewUrl":77,"publishedAt":245,"alternativeText":77,"provider_metadata":77},{"large":1073,"small":1074,"medium":1075,"thumbnail":1076},{"ext":69,"url":218,"hash":219,"mime":72,"name":220,"path":77,"size":221,"width":84,"height":222,"sizeInBytes":223},{"ext":69,"url":225,"hash":226,"mime":72,"name":227,"path":77,"size":228,"width":92,"height":229,"sizeInBytes":230},{"ext":69,"url":232,"hash":233,"mime":72,"name":234,"path":77,"size":235,"width":100,"height":236,"sizeInBytes":237},{"ext":69,"url":239,"hash":240,"mime":72,"name":241,"path":77,"size":242,"width":108,"height":243,"sizeInBytes":244},[1078],{"text":116,"type":29},{"type":39,"level":183,"children":1080},[1081],{"text":252,"type":29},{"type":25,"children":1083},[1084],{"text":256,"type":29},{"type":61,"children":1086},[1087],{"text":260,"type":29},{"type":25,"children":1089},[1090],{"text":264,"type":29},{"type":25,"children":1092},[1093],{"text":268,"type":29},{"type":39,"level":40,"children":1095},[1096],{"text":272,"type":29},{"type":25,"children":1098},[1099],{"text":276,"type":29},{"type":25,"children":1101},[1102],{"text":280,"type":29},{"type":39,"level":40,"children":1104},[1105],{"text":284,"type":29},{"type":39,"level":183,"children":1107},[1108],{"text":288,"type":29},{"type":25,"children":1110},[1111],{"text":292,"type":29},{"type":39,"level":183,"children":1113},[1114],{"text":296,"type":29},{"type":25,"children":1116},[1117],{"text":300,"type":29},{"type":39,"level":183,"children":1119},[1120],{"text":304,"type":29},{"type":25,"children":1122},[1123],{"text":308,"type":29},{"type":39,"level":183,"children":1125},[1126],{"text":312,"type":29},{"type":25,"children":1128},[1129],{"text":316,"type":29},{"type":25,"children":1131},[1132],{"text":320,"type":29},{"type":25,"children":1134},[1135],{"text":324,"type":29},[],[]]