IPv4 is the classic network protocol that has been the foundation of the public internet for over 40 years. An address looks like this: 203.0.113.42. Any device and any service can work with IPv4, making it the basic standard for websites, APIs, and mail servers.
Why You Need IPv4 on VPS
Without a public IPv4, your server is inaccessible from the internet.
DNS first translates the domain to an address via A record, then the browser connects to this address.
HTTPS works via SNI, meaning one IPv4 can serve multiple domains with different certificates.
Email is sensitive to sender reputation, meaning the address must be "clean" with correct PTR and SPF/DKIM/DMARC records.
How Many IPv4 Addresses Are Enough
For typical projects, one address is sufficient:
- Web server serves hundreds of domains through virtual hosts
- Control panel adds domains in a couple of clicks, all domains respond on one IP
Additional addresses are useful if you need service isolation (e.g., separating web and mail), separate mailing streams, or specific integrations with external systems.
Dedicated IPv4 vs Shared
On VPS, you get a dedicated IPv4:
- Reputation depends only on your actions
- You can configure PTR, convenient for email signing
- No risks from IP neighbors
Shared IP is typical for shared hosting, where neighboring sites can cause blocklists and reverse zone issues.
Reputation and Reverse Zone (PTR)
Any mail server checks IPv4 against RBL databases on entry. Bad history = spam or rejection.
You need correct PTR: 203.0.113.42 → mail.example.com. Reverse record is created by the range owner, request through support.
Before launching mailings, check the address through reputation aggregators and request a new one if necessary.
When to Change IPv4
- Persistent blocklist hits
- Bans on external platforms due to previous owners
- Targeted DDoS on specific address
After replacement, don't forget to update domain A records, PTR, firewall rules, and integrator allow-lists.
Geography and Speed
IP is tied to datacenter location, meaning latency to users depends on physical distance.
Local SEO and regulatory requirements also consider geography.
European audience will get lower ping with European hosting and vice versa.
NAT vs Public IPv4
Normal VPS gets a public address. NAT is found in ultra-budget solutions and creates limitations: harder to configure incoming connections, reverse zone unavailable, some protocols work unstably. For serious infrastructure, you need real public IPv4.
Diagnostics and Verification
External address:
curl ifconfig.meInterfaces and bound addresses:
ip addr showAvailability:
ping yourdomain.tld
traceroute yourdomain.tldDNS and reverse zone:
dig A yourdomain.tld
dig -x 203.0.113.42Our Address Policy
Every VPS includes 1 × IPv4 free.
IPv6 /64 — €1 per month for those who need dual-stack and future-readiness. Mention in case full stack is needed.
Additional IPv4 issued on request and billed separately. For large pools, brief task justification helps: mail isolation, separate mailing channels, partner integrations.
Pre-Production Checklist
- Deploy server with public IPv4, verify availability via ping and ports 80/443
- Configure domain A records, set up HTTPS
- For email: request PTR, enable SPF, DKIM, DMARC, check RBL
- Restrict incoming traffic in firewall, leave required ports
- Document address, location, contacts for urgent changes
FAQ
How many sites can run on one IPv4?
As many as the server allows. Virtual hosts remove limitations, everything depends on resources.
Do I need separate address for each certificate?
No. SNI allows serving different certificates on one IP. Exceptions are rare.
Does IPv4 affect site speed?
Indirectly through geography and network. The closer the datacenter to the audience, the lower the latency.
What to do if address inherited bad reputation?
Open ticket for replacement and update DNS. Clean address solves the problem faster than lengthy unban procedures.