Setting up an DE endpoint
Generate credentials in the dashboard, set country to DE (and a city if the job needs one), then paste the endpoint into your browser profile or script. SOCKS5 and HTTP(S) share the same login, so switching protocol never means re-buying an IP. Use code OPEN30 on the first order.
Why operators pick DE per-IP
Per-IP billing wins in Germany work where one identity maps to one account. You buy an DE address, assign it to a profile, and it stays yours — no bandwidth meter running in the background while the profile idles.
- Antidetect profiles — one Germany IP per browser profile, held for weeks.
- Marketplace accounts — DE sellers and buyers kept on separate lines.
- Drop and release monitoring — Berlin and Munich exits for regional launches.
- Localized QA — verify what a Germany shopper sees before a campaign ships.
Germany coverage at a glance
| Attribute | 922 S5 in Germany |
|---|---|
| Pool | Part of the 350M+ residential network |
| Cities | Berlin, Munich, Hamburg, Frankfurt, Cologne and more |
| Carriers | Deutsche Telekom, Vodafone, 1&1 |
| Protocols | SOCKS5 / HTTP / HTTPS |
| Billing | Per IP — balance never expires |
| Checkout | Crypto, no KYC |
Frequently asked questions
How much is one Germany IP?
922 S5 sells DE addresses per IP starting at $0.07/IP, and volume tiers lower the unit price. Bought IPs stay on your balance indefinitely.
Can I keep the same Germany IP for a profile?
Yes. That is the point of per-IP billing — assign one DE address to one antidetect profile and reuse it as long as the profile lives.
Which Germany cities are available?
Berlin, Munich, Hamburg, Frankfurt, Cologne and additional metros. City selection is part of the credential, so several DE cities can run at once.
Do you require KYC for Germany proxies?
No. Registration is email-only and checkout is crypto — USDT, BTC, LTC and others. Access activates once the payment confirms on-chain.