Gwajin Yoyon WebRTC (Kwatanta HTTP Proxy IP da UDP STUN Candidates)

Updated: 2026-11-05

An gina WebRTC (Web Real-Time Communication) a cikin Chrome, Edge, Firefox, Brave, da burawzar wayar hannu don kiran murya da bidiyo. Saboda WebRTC na amfani da sabobin UDP STUN (stun.l.google.com, stun.cloudflare.com) don gano hanyoyin hanyar sadarwa, yakan kauce wa daidaitattun saitin HTTP(S) proxy tare da bayyana ainihin adireshin ISP IP na gida ko na LAN ga shafukan yanar gizo. Wannan shafi yana gwada burawzarka kai tsaye da zaran ya bude.

Hada Bayanan Burawzar da Ba Su da Yoyo Tare da Tsabtattun Static IPs

Sayi Proxies na Anti-Detect Free Proxy Checker

HTTP(S) Proxy / Server-Seen IP

216.73.216.191

Seen by websites via TCP / HTTP headers

WebRTC STUN Public IP(s)

No Public WebRTC IP Exposed

Discovered via browser UDP STUN servers

✅ No WebRTC Public IP Mismatch Detected

Your browser either blocks UDP STUN completely or masks WebRTC candidates.

Yadda Zaka Fahimci Sakamakon Gwajin Yoyon WebRTC Dinka

Kwamfutar kariya daga zamba a TikTok Shop, Facebook Business Manager, Shopee, Amazon, da Etsy na gudanar da binciken RTCPeerConnection a asirce yayin shiga asusu. Kwatanta yanayin 'candidates' guda uku masu yiwuwa a kasa:

Nau'in Candidate	Abin da Scripts na Shafin Yanar Gizo Ke Gani	Matakin Hadari	Matakin da Aka Ba da Shawarar Dauka
Public STUN IP ≠ HTTP IP	Dukansu Proxy IP dinka da Ainihin IP dinka na Gida	MAI HADARIN GASKE (Hada Asusu 100%)	Kunna WebRTC Spoofing/Replace a cikin Anti-Detect Browser ko kuma kashe WebRTC
Public STUN IP = HTTP IP	Proxy IP dinka kadai (`srflx` yayi daidai da HTTP)	LAFIYA (Bayanin Burawzar Halitta)	Kyakkyawan yanayi da Genlogin, GoLogin, AdsPower, da Multilogin ke samarwa
mDNS `.local` / An Kashe	Boyayyen UUID `.local` ko babu candidate	LAFIYA (Kariyar Tabbata)	Yana da kyau don bincike na yau da kullum a Chrome/Firefox tare da kari (extensions)

Yadda Ake Gyara Yoyon WebRTC a Dukkan Burawzoyi

Burawzoyin Anti-Detect (Genlogin, GoLogin, AdsPower, Dolphin{anty}): Saita yanayin WebRTC zuwa 'Alter / Replace' domin RTCPeerConnection ya mayar da VinaProxy proxy IP dinka a matsayin public STUN candidate.
Mozilla Firefox: Bude about:config, bincika media.peerconnection.enabled, sannan canza shi zuwa false.
Google Chrome & Microsoft Edge: Saka karin WebRTC Network Limiter na hukuma sannan ka kunna Anonymize local IPs exposed by WebRTC a cikin chrome://flags / edge://flags.

Mataki-mataki

1
Hada ta hanyar proxy ko bayanin martaba na anti-detect
Bude wannan shafi a cikin ainihin bayanin martaba na burawzar da kake amfani da shi don sarrafa asusu.
2
Kwatanta katin HTTP IP da katin WebRTC STUN
Tabbatar cewa katin gefen dama yana nuna 'No Public WebRTC IP Exposed' ko kuma yayi daidai da HTTP Proxy IP dinka a gefen hagu.
3
Duba teburin ICE Candidate don yoyon LAN
Tabbatar cewa an rufe adiresoshin 192.168.x.x ko 10.x.x.x na gida da sunayen masauki na .local mDNS.
4
Danna 'Re-Test WebRTC' bayan daidaita saituna
Tabbatar cewa sanarwar koren launi mai taken 'No WebRTC Public IP Mismatch Detected' ta bayyana kafin ka shiga dandalin da kake bukata.

Tambayoyin da aka fi yi

Me ya sa WebRTC ke fitar da ainihin IP dina yayin da nake amfani da karin Chrome proxy kamar SwitchyOmega ko FoxyProxy?

Karin proxy na HTTP(S) yana tura zirga-zirgar TCP HTTP/HTTPS ne kawai. A tsarin asali, Chrome na tura bukatun hadin WebRTC STUN ta hanyar raw UDP a wajen ramin proxy, sai dai idan wani kari ko burawzar anti-detect ta takaita tafiyar WebRTC UDP.

Shin ya fi kyau a kashe WebRTC gaba daya ko a saita shi zuwa 'Replace / Alter' a burawzoyin anti-detect?

Ga dandamali masu bukatar cikakkiyar amana kamar Facebook Ads, TikTok Shop, da Amazon, saita WebRTC zuwa 'Replace / Alter' (inda STUN ke dawo da proxy IP dinka) ya fi zama na halitta fiye da kashe API din RTCPeerConnection gaba daya.

Menene `.local` mDNS candidate a cikin teburin?

Burawzoyi na zamani suna maye gurbin LAN IPs na sirri (kamar 192.168.1.5) da UUID na wucin gadi mai karewa da .local domin shafukan yanar gizo su kasa gano bayanan rukunin na'urar router dinka.