Skip to contentSyria: free HTTPS proxies 🇸🇾
Syria HTTPS: 7 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–57 of 57 (working first, then history)
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 8080 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 76 ms | 49% | ||
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 2888 ms | 39% | ||
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 2502 ms | 38% | ||
| 8080 | HTTPS | 🇸🇾Ad Dānā | Transparent | ✓ | 64 ms | 24% | ||
| 8080 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 6404 ms | 22% | ||
| 8080 | HTTPS | 🇸🇾Kafr Baţnā | Transparent | ✓ | 6386 ms | 20% | ||
| 8080 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 6283 ms | 11% | ||
| 8085 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 123 ms | 54% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 2849 ms | 51% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 65 ms | 49% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 70 ms | 48% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 58 ms | 47% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ḩīsh | Transparent | ✓ | 54 ms | 46% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Al Ḩaffah | Transparent | ✓ | 4071 ms | 39% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 7278 ms | 37% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ad Dānā | Transparent | ✓ | 5794 ms | 36% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Irbin | Transparent | ✓ | 82 ms | 35% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Manbij | Transparent | ✓ | 99 ms | 34% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ad Dānā | Transparent | ✓ | 69 ms | 34% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Jarābulus | Transparent | ✓ | 2886 ms | 34% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 2015 ms | 34% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ad Dānā | Transparent | ✓ | 3875 ms | 33% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 58 ms | 30% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Al-Qamishli | Transparent | ✓ | 3694 ms | 30% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ḩīsh | Transparent | ✓ | 77 ms | 28% | not working last alive | |
| 7890 | HTTPS | 🇸🇾Homs | Transparent | ✓ | 6085 ms | 28% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 64 ms | 28% | not working last alive | |
| 3128 | HTTPS | 🇸🇾‘Ayn al ‘Arab | Transparent | ✓ | 4534 ms | 28% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Qadsayyā | Transparent | ✓ | 1848 ms | 27% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Babīlā | Transparent | ✓ | 5216 ms | 27% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 61 ms | 26% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Idlib | Transparent | ✓ | 61 ms | 26% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 2715 ms | 26% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Armanāz | Transparent | ✓ | 66 ms | 25% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Babīlā | Transparent | ✓ | 3156 ms | 24% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 6452 ms | 23% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Manbij | Transparent | ✓ | 4949 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 4220 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 2400 ms | 20% | not working last alive | |
| 8085 | HTTPS | 🇸🇾Damascus | Transparent | ✓ | 57 ms | 20% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Armanāz | Transparent | ✓ | 4052 ms | 19% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 8716 ms | 18% | not working last alive | |
| 8085 | HTTPS | 🇸🇾Ad Dānā | Transparent | ✓ | 6635 ms | 18% | not working last alive | |
| 7890 | HTTPS | 🇸🇾Latakia | Transparent | ✓ | 2855 ms | 17% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Hama | Transparent | ✓ | 3170 ms | 17% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Jarābulus | Transparent | ✓ | 3809 ms | 15% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Kafr Baţnā | Transparent | ✓ | 620 ms | 15% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Kafr Baţnā | Transparent | ✓ | 8640 ms | 14% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Manbij | Transparent | ✓ | 3180 ms | 14% | not working last alive | |
| 7890 | HTTPS | 🇸🇾Babīlā | Transparent | ✓ | 3982 ms | 13% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 3389 ms | 13% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Jaramana | Transparent | ✓ | 6486 ms | 12% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Dārayyā | Transparent | ✓ | 1967 ms | 12% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 86 ms | 11% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Aleppo | Transparent | ✓ | 3890 ms | 5% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Armanāz | Transparent | ✓ | 72 ms | 4% | not working last alive | |
| 8080 | HTTPS | 🇸🇾Ḩīsh | Transparent | ✓ | 61 ms | 4% | not working last alive | |
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
At a glance
This page has 7 entries marked working. Mean recorded check success across these entries is 29%; mean recorded response time, where available, is 3514 ms. By protocol: HTTPS (7). By anonymity level: Transparent (7). The most common ports are 8080. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Syria / HTTPS. Use the recorded status and timestamps to interpret the table, then recheck before use. Availability and anonymity labels do not certify operator trust or privacy.
For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.
Free proxies — FAQ
How often is this free proxy list checked?
Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.
Are free public proxies safe to use?
Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.
How do I use a proxy from this list?
Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
People found this page by searching for
- HTTPS
- HTTPS ip address
- anonymous proxies HTTPS
- proxy server HTTPS
- HTTPS proxy list
- dedicated ip provider
- public proxies tutorial
- socks5 proxy
- socks5 proxies without registration
- free http proxies
- working proxies explained
- free proxy list
- SOCKS5 & HTTP proxies
- what is a SOCKS5 proxy
Real search phrases this page answers — the linked ones open the page that covers them in depth.