Offshore 1
$3.09/ month
3 mo $8.346 mo $14.8312 mo $25.95
- 1 vCPU
- 1 GB RAM
- 20 GB NVMe
- 2 TB traffic
Guide · Outbound SMTP
Outbound port 25 is open on every Nymhost VPS, in all 9 cities, with no ticket and no deposit, and you pay in Bitcoin or another coin, as crypto is the only payment method. Here is how to prove it from the server in one command, why most clouds block it, which port does what, and what an open port still does not fix.
Port 25 on Nymhost, in short
On Nymhost, outbound port 25 is open on every VPS, in all 9 cities, with no ticket and no deposit, so your server can deliver mail straight to other mail servers. To check it from the VPS, run nc -vz -w 5 gmail-smtp-in.l.google.com 25: a connection that succeeds means the port is open on the whole path, a timeout means something filters it. Spam and bulk email are forbidden and get the VPS suspended. An open port is not delivery: reverse DNS (ask support), SPF, DKIM and a clean IP address decide whether receivers accept your mail.
A VPS with port 25 open is what you get by default on Nymhost. Every plan in the Offshore range (Amsterdam, Reykjavik, Zurich, Bucharest) and in the Global range (New York, Dallas, Los Angeles, London, Amsterdam, Frankfurt) leaves outbound port 25 open. There is no form to fill in, no use case to justify, no deposit and no account age to reach.
One rule comes with it: no spam and no bulk email, from any server or any address. A VPS used for either is suspended. A misconfigured Postfix that relays for anyone ends up sending spam too, with the same result, and a hacked server is still your server under the abuse rules. Keep the system updated and log in with SSH keys.
What the open port is for:
What it is not for: newsletters to bought lists, cold outreach and mailing lists at scale. For those, a Nymhost VPS is the wrong tool.
Run these checks on the VPS itself. Each one opens a single TCP connection to a public mail server and sends no mail. The examples use gmail-smtp-in.l.google.com, the first of the five MX records of gmail.com on 18 November 2026; the MX host of any large mail provider works the same way. On Debian and Ubuntu, nc comes from the netcat-openbsd package and dig from bind9-dnsutils. On AlmaLinux 10 and Rocky Linux 10, install nmap-ncat and bind-utils; Ncat's manual lists the same -v, -z and -w options.
dig +short MX gmail.com prints each MX host with its preference number. Sending servers try the lowest number first.
nc -vz -w 5 gmail-smtp-in.l.google.com 25. In the OpenBSD nc manual, -z checks for a listening service without sending it any data, -v prints the result and -w 5 gives up after 5 seconds.
openssl s_client -starttls smtp sends the SMTP commands that switch the session to TLS, and -brief prints a short summary. Wrapped in timeout 15, the test cannot hang: timeout exits with code 124 when the time runs out.
Run the same nc test against smtp.gmail.com on ports 587 and 465. If they connect while port 25 times out, a filter aims at port 25 alone.
nc -6 -vz -w 5 gmail-smtp-in.l.google.com 25. Your VPS has a routed IPv6 /64 and Postfix may deliver over it, so test both address families.
Once Postfix runs and your firewall allows port 25, run nc -vz -w 5 203.0.113.10 25 from another server, with your VPS address in place of the example. Do not run it from home: the Mail-in-a-Box guide notes that most residential networks are blocked from sending mail, so a timeout there says nothing about your VPS.
# Debian or Ubuntu: apt install -y netcat-openbsd bind9-dnsutils
# AlmaLinux or Rocky Linux: dnf install -y nmap-ncat bind-utils
dig +short MX gmail.com
nc -vz -w 5 gmail-smtp-in.l.google.com 25
timeout 15 openssl s_client -connect gmail-smtp-in.l.google.com:25 -starttls smtp -brief </dev/null; echo "exit code: $?"
# compare with the submission ports
nc -vz -w 5 smtp.gmail.com 587
nc -vz -w 5 smtp.gmail.com 465
# the same test over IPv6
nc -6 -vz -w 5 gmail-smtp-in.l.google.com 25$ timeout 15 openssl s_client -connect smtp.gmail.com:587 -starttls smtp -brief </dev/null; echo "exit code: $?"
Connecting to 64.233.184.109
CONNECTION ESTABLISHED
Protocol version: TLSv1.3
Ciphersuite: TLS_AES_256_GCM_SHA384
Requested Signature Algorithms: ECDSA+SHA256:RSA-PSS+SHA256:RSA+SHA256:ECDSA+SHA384:RSA-PSS+SHA384:RSA+SHA384:RSA-PSS+SHA512:RSA+SHA512:RSA+SHA1
Peer certificate: CN=smtp.gmail.com
Hash used: SHA256
Signature type: ecdsa_secp256r1_sha256
Verification: OK
Negotiated TLS1.3 group: X25519MLKEM768
250 LIMITS MAILMAX=1000 RCPTMAX=100
DONE
exit code: 0
$ timeout 15 openssl s_client -connect gmail-smtp-in.l.google.com:25 -starttls smtp -brief </dev/null; echo "exit code: $?"
Connecting to 66.102.1.26
exit code: 124| What you see | What it means | Next step |
|---|---|---|
nc reports that the connection succeeded; openssl prints CONNECTION ESTABLISHED and Verification: OK | Port 25 is open from your VPS to that server, and STARTTLS works | Move on to reverse DNS, SPF and DKIM |
nc times out after 5 seconds; timeout ends openssl with exit code 124, as in the port 25 example above | Packets are dropped somewhere: a provider filter, an output rule in your own firewall, or a filter on the network you test from | Run nft list ruleset or ufw status verbose, then test another MX host and port 587 |
| Connection refused | Something answered with a reset: nothing listens on that port, or a firewall rejects instead of dropping | Try another MX host; check your own output rules |
A name-resolution error, or dig prints nothing | DNS failed; port 25 was never tried | Check /etc/resolv.conf and run dig +short MX gmail.com again |
| Port 25 times out while 587 and 465 connect | A filter aimed at port 25 only | On a Nymhost VPS, email [email protected] with the command and its output; elsewhere, read the provider's policy in the table below |
Port 25 is where mail servers hand messages to each other, with no login on that hop. Spam from a hacked or rented server goes out on port 25 and hurts the reputation of the provider's addresses, not only one customer's. So many providers close the port first and open it only for customers they have reviewed. Their help pages give the reasons:
Home connections are filtered too: the Mail-in-a-Box guide says most residential networks are blocked from sending mail. The cost falls on people who run a legitimate server: a ticket, a wait, sometimes a refusal. Nymhost leaves the port open and enforces its rule afterwards: a VPS that sends spam is suspended.
Each row is what the provider's own help page said on 18 November 2026. Open means outbound port 25 works on a new server without asking. Policies change, so every row carries the date its page shows.
| Provider | Outbound port 25 by default | To get it opened | Page date |
|---|---|---|---|
| Nymhost | Open on every VPS, in all 9 cities | Nothing to request; spam and bulk email are forbidden | 18 Nov 2026 |
| OVHcloud (VPS) | Open, but the anti-spam system can block an IP that sends spam. VPS in Local Zones cannot reach any SMTP port; Public Cloud instances are blocked by default | Ask support where the infrastructure allows it; port 587 is suggested instead | 28 May 2026 |
| Hostinger (VPS) | Open: its help page says port 25 is not blocked | Nothing to request; check your own VPS firewall first | 29 Oct 2026 |
| Hetzner (cloud servers) | Blocked: ports 25 and 465 on all cloud servers; 587 open | Request after one month as a customer and a first paid invoice, for a valid use case; decided case by case, per account | 12 Sep 2024 |
| Vultr | Blocked on all new instances | Ticket with your use case, your spam protections (SPF, DKIM, rate limits) and expected volume; approval not guaranteed | 26 Oct 2026 |
| Akamai (Linode) | Blocked on some accounts: ports 25, 465 and 587 on some accounts created after 5 Nov 2019 | Ask support with your name, use case, sending practices and sending domains; each request is reviewed | 1 Mar 2026 |
| DigitalOcean | Blocked: ports 25, 465 and 587 on all Droplets, Reserved IPs included | No unblock route given; a third-party email service is recommended | 7 Apr 2026 |
| AWS (EC2) | Blocked towards public IPv4 and IPv6 addresses; private addresses allowed | Request removal; the page links to AWS's instructions | Not shown |
| Google Cloud (Compute Engine) | Blocked towards destinations outside your VPC network; some projects are not restricted; 587 and 465 are not restricted | No request route on the page | Not shown |
| Microsoft Azure (VMs) | Depends on the subscription: open on Enterprise Agreement and MCA-E, blocked by default on Enterprise Dev/Test, blocked on every other type | Dev/Test: a diagnostic in the Azure portal; other types: an authenticated relay on port 587 | 28 Jul 2025 |
| IONOS | Blocked on Cloud Servers, VPS, VPS+ and dedicated servers in its Cloud Panel | Phone support, once the server has a fixed FQDN, a PTR record and an SPF record | Not shown |
| IncogNET | Blocked on all VPS and vDedi servers | A one-time, non-refundable $5 fee and agreement to basic email rules | Not shown |
An open port is only the first condition: receivers still judge your IP address, as explained in what an open port 25 does not guarantee.
Three ports carry SMTP, and they do different jobs. Port 25 is for servers delivering to servers. Ports 587 and 465 are for your own mail client or application handing a message, after logging in, to the server that will deliver it. RFC 6409 split this submission step from relay so that each could follow its own rules, and left relay on port 25.
| Port | Role | Who connects | Login | Encryption | Defined in |
|---|---|---|---|---|---|
| 25 | Relay: delivery from one mail server to the next, including to your MX when others send you mail | Mail servers | None on this hop | Optional STARTTLS; Gmail asks every sender for TLS | RFC 5321, section 4.5.4.2: a server keeps listening on the SMTP port, assigned by IANA as 25 |
| 587 | Submission: your mail client or application hands mail to its outgoing server | Mail clients and applications | Required: by default the server refuses a message until you log in (RFC 6409, section 4.3) | STARTTLS | RFC 6409, section 3.1 |
| 465 | Submission with implicit TLS, the service named submissions | Mail clients and applications | Same as 587 | TLS from the first byte | RFC 8314, section 3.3 |
RFC 8314 prefers implicit TLS on 465 for submission, asks clients and servers to support both 465 and STARTTLS on 587 during a transition period, and says the two are equally secure when implemented correctly. It leaves relay on port 25 out of its scope.
It depends on which half of email you run.
A relay lends you its reputation, but a third party then handles every message you send, under its own rules and rate limits. With outbound port 25 open you can choose: deliver directly, or relay only the mail that must reach a demanding receiver. The guide to set up Postfix, Dovecot and DKIM step by step builds the direct route; for an application that only sends, see send email from a VPS, with both routes.
An open port means your server can connect. Whether the other side accepts the message is decided there. Four checks matter most:
Every Nymhost VPS has a routed IPv6 /64, and Gmail's mail exchanger has an IPv6 address too (AAAA record, checked 18 November 2026). With both protocols on, Postfix may deliver over IPv6, from an address that has no PTR record. Google's troubleshooting notes say an IPv6 authorization error could mean the sending server's PTR record is not set for IPv6.
The Postfix manual calls smtp_address_preference = ipv4 unsafe and says it does not solve this. Its recommendation: receive over both IPv4 and IPv6, and deliver over IPv4 only. The setup guide keeps Postfix on IPv4 in both directions, which is simpler; the commands below are the split version. Receiving over IPv6 also needs an AAAA record for your mail hostname.
postconf -e "inet_protocols = all"
postconf -P "smtp/unix/inet_protocols=ipv4"
# the manual says to stop and start Postfix after changing inet_protocols
systemctl stop postfix
systemctl start postfix
postconf -P | grep inet_protocolsHetzner says it wants to build trust with new customers before it opens port 25; Nymhost asks for no account history at all. Crypto is the only way to pay, with no card, PayPal or bank transfer, and port 25 is open as soon as a person has built the VPS, usually within minutes of the payment confirming. A Bitcoin top-up is credited after 2 confirmations, about 20 minutes on the checkout; the minimum is $25, and what the plan does not use stays on a balance that never expires. The guide to paying for a VPS with Bitcoin or another coin covers the other six coins.
Outbound port 25 is open on every plan below. For Postfix and Dovecot with a few mailboxes, Offshore 2 ($4.89 a month) or Global 2 ($3.19), both with 2 GB of RAM, is enough; which VPS for a mail server sizes larger setups such as mailcow. Rentals of 3, 6 or 12 months save 10%, 20% or 30%. Compare every plan and city on the pricing page, or read what a Nymhost account keeps about you.
Amsterdam · Reykjavik · Zurich · Bucharest
$3.09/ month
3 mo $8.346 mo $14.8312 mo $25.95
$4.89/ month
3 mo $13.206 mo $23.4712 mo $41.07
$8.19/ month
3 mo $22.116 mo $39.3112 mo $68.79
$13.49/ month
3 mo $36.426 mo $64.7512 mo $113.31
$20.49/ month
3 mo $55.326 mo $98.3512 mo $172.11
New York · Dallas · Los Angeles · London · Amsterdam · Frankfurt
$3.19/ month
3 mo $8.616 mo $15.3112 mo $26.79
$6.39/ month
3 mo $17.256 mo $30.6712 mo $53.67
$9.59/ month
3 mo $25.896 mo $46.0312 mo $80.55
$19.19/ month
3 mo $51.816 mo $92.1112 mo $161.19
$29.39/ month
3 mo $79.356 mo $141.0712 mo $246.87
Prices in US dollars, checked on 18 November 2026. Paid from a crypto balance (minimum top-up $25); 3, 6 and 12 months save 10, 20 and 30%. Every plan: KVM, root over SSH, 1 dedicated IPv4 + /64 IPv6, shared 1 Gbit/s port.
Of the 12 providers in the table above, read on 18 November 2026, three say outbound port 25 is not blocked on a new VPS: Nymhost, OVHcloud and Hostinger. Hetzner, Vultr, Akamai, AWS and IONOS open it on request, under conditions; IncogNET charges a $5 fee; Azure depends on the subscription type; DigitalOcean and Google Cloud give no request route on their pages.
On the VPS, run nc -vz -w 5 gmail-smtp-in.l.google.com 25. If the connection succeeds, outbound port 25 works; a timeout after 5 seconds means something filters it. Test port 587 the same way: if 587 connects while 25 does not, the filter targets port 25.
Yes. Outbound port 25 is open on every Nymhost VPS, in all 9 cities, from the start. You send no ticket, pay no deposit and wait for no review. The one condition is the rule: spam and bulk email are forbidden, and a VPS used for either is suspended.
For sending, yes, if you relay through a service or a server that accepts your login on 587 or 465 and delivers on port 25 for you. For receiving, no: other mail servers deliver to your MX on port 25, so a server that receives mail must accept connections there.
Check your own firewall first: an output rule in nftables or ufw can drop port 25. Then test a second MX host and port 587 to see whether the filter hits port 25 alone. Run the test on the VPS, not from home, where most connections are blocked from sending mail. On Nymhost, send the command and its output to [email protected].
Not by itself. Google asks every sender for SPF or DKIM, valid forward and reverse DNS, TLS and a spam rate under 0.3%. The open port lets your server connect; the PTR record, SPF, DKIM and the reputation of the IP decide where the message lands.
No. Bulk email is forbidden on every Nymhost VPS, newsletters included, and a VPS used for it is suspended. Port 25 is open for your own mail: mailboxes on your domain, mail for a family or a small team, and messages an application sends to its users one at a time.