Skip to content

Guide · Outbound SMTP

VPS with port 25 open, paid in Bitcoin: test it, then run your own mail

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.

Updated By Nymhost LLC16 min read

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.

Port 25 on a Nymhost VPS: open by default, with one rule

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:

  • your own mail server, for you, your family or a small team;
  • a send-only Postfix for an application or a website on your own domain;
  • delivery tests and checks of your own mail servers.

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.

Nymhost checkout location step: Amsterdam, Reykjavik, Zurich and Bucharest open, the US, London and Frankfurt greyed out
The location step of the Nymhost checkout lists the 9 cities, and outbound port 25 is open in each of them. The US cities, London and Frankfurt are greyed out here because an Offshore plan is selected.

How to test whether outbound port 25 is open

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.

  1. 01

    Find a mail exchanger

    dig +short MX gmail.com prints each MX host with its preference number. Sending servers try the lowest number first.

  2. 02

    Open a TCP connection on port 25

    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.

  3. 03

    Check that STARTTLS works

    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.

  4. 04

    Compare with ports 587 and 465

    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.

  5. 05

    Repeat over IPv6

    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.

  6. 06

    Test inbound port 25 from another server

    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.

Outbound port 25 test, run on the 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
Example output with OpenSSL 3.5 on 18 November 2026, from a network that filters port 25 but not 587
$ 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
How to read the port 25 test, from the nc, openssl-s_client and timeout manuals, read 18 November 2026
What you seeWhat it meansNext step
nc reports that the connection succeeded; openssl prints CONNECTION ESTABLISHED and Verification: OKPort 25 is open from your VPS to that server, and STARTTLS worksMove 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 abovePackets are dropped somewhere: a provider filter, an output rule in your own firewall, or a filter on the network you test fromRun nft list ruleset or ufw status verbose, then test another MX host and port 587
Connection refusedSomething answered with a reset: nothing listens on that port, or a firewall rejects instead of droppingTry another MX host; check your own output rules
A name-resolution error, or dig prints nothingDNS failed; port 25 was never triedCheck /etc/resolv.conf and run dig +short MX gmail.com again
Port 25 times out while 587 and 465 connectA filter aimed at port 25 onlyOn a Nymhost VPS, email [email protected] with the command and its output; elsewhere, read the provider's policy in the table below

Why most VPS providers block port 25

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:

  • Akamai (Linode) restricts ports 25, 465 and 587 on some accounts created after 5 November 2019, to fight spam.
  • DigitalOcean blocks ports 25, 465 and 587 on all Droplets to prevent spam and other abuse, and advises against running your own mail server at all.
  • Vultr blocks port 25 on all new instances to prevent abuse such as spam and to protect the IP reputation of its network.
  • Google Cloud blocks connections to port 25 outside your VPC network because of the risk of abuse.
  • Microsoft Azure blocks outbound port 25 on most subscription types, citing the security of its customers, the protection of its platform and industry standards.
  • Hetzner blocks ports 25 and 465 on cloud servers by default and says it wants to build trust with new customers before it opens them.

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.

Port 25 policy at 12 VPS providers, from their own pages

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.

Outbound port 25 at 12 providers, from each provider's own page, all read 18 November 2026; the last column is the date the page shows.
ProviderOutbound port 25 by defaultTo get it openedPage date
NymhostOpen on every VPS, in all 9 citiesNothing to request; spam and bulk email are forbidden18 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 defaultAsk support where the infrastructure allows it; port 587 is suggested instead28 May 2026
Hostinger (VPS)Open: its help page says port 25 is not blockedNothing to request; check your own VPS firewall first29 Oct 2026
Hetzner (cloud servers)Blocked: ports 25 and 465 on all cloud servers; 587 openRequest after one month as a customer and a first paid invoice, for a valid use case; decided case by case, per account12 Sep 2024
VultrBlocked on all new instancesTicket with your use case, your spam protections (SPF, DKIM, rate limits) and expected volume; approval not guaranteed26 Oct 2026
Akamai (Linode)Blocked on some accounts: ports 25, 465 and 587 on some accounts created after 5 Nov 2019Ask support with your name, use case, sending practices and sending domains; each request is reviewed1 Mar 2026
DigitalOceanBlocked: ports 25, 465 and 587 on all Droplets, Reserved IPs includedNo unblock route given; a third-party email service is recommended7 Apr 2026
AWS (EC2)Blocked towards public IPv4 and IPv6 addresses; private addresses allowedRequest removal; the page links to AWS's instructionsNot shown
Google Cloud (Compute Engine)Blocked towards destinations outside your VPC network; some projects are not restricted; 587 and 465 are not restrictedNo request route on the pageNot 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 typeDev/Test: a diagnostic in the Azure portal; other types: an authenticated relay on port 58728 Jul 2025
IONOSBlocked on Cloud Servers, VPS, VPS+ and dedicated servers in its Cloud PanelPhone support, once the server has a fixed FQDN, a PTR record and an SPF recordNot shown
IncogNETBlocked on all VPS and vDedi serversA one-time, non-refundable $5 fee and agreement to basic email rulesNot 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.

Port 25 vs 587 vs 465: which port does what

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.

SMTP ports and their roles, from RFC 5321 (October 2008), RFC 6409 (November 2011) and RFC 8314 (January 2018), read 18 November 2026
PortRoleWho connectsLoginEncryptionDefined in
25Relay: delivery from one mail server to the next, including to your MX when others send you mailMail serversNone on this hopOptional STARTTLS; Gmail asks every sender for TLSRFC 5321, section 4.5.4.2: a server keeps listening on the SMTP port, assigned by IANA as 25
587Submission: your mail client or application hands mail to its outgoing serverMail clients and applicationsRequired: by default the server refuses a message until you log in (RFC 6409, section 4.3)STARTTLSRFC 6409, section 3.1
465Submission with implicit TLS, the service named submissionsMail clients and applicationsSame as 587TLS from the first byteRFC 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.

Do you need port 25, or is port 587 enough?

It depends on which half of email you run.

  • Receiving mail for your domain always uses port 25 inbound: other servers deliver to your MX there. A relay service does not change that, unless a third party also receives your mail for you.
  • Sending directly to the recipient's server needs port 25 outbound. That is what Nymhost leaves open.
  • Sending through a relay, a smarthost you pay for or another server of yours, uses port 587 or 465 with a login, and the relay does the port 25 delivery. Azure, Hetzner, Vultr and OVHcloud point customers to this route when port 25 is closed.

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.

What an open port 25 does not guarantee

An open port means your server can connect. Whether the other side accepts the message is decided there. Four checks matter most:

  1. Reverse DNS (PTR). Google's sender guidelines ask every sender to Gmail for valid forward and reverse DNS, and the sending IP must match the IP of the hostname in its PTR record. A PTR record is set by whoever controls the IP range, not in your domain's DNS. Reverse DNS is not a published Nymhost feature: email [email protected] with your IP address and mail hostname, and ask what is possible before you rely on the server. A person answers within 12 hours.
  2. SPF or DKIM, and TLS. Google asks every sender for SPF or DKIM and a TLS connection. The setup guide configures both, plus DMARC.
  3. IP reputation. Your IPv4 address is dedicated to your VPS, but it may have been used before. The Mail-in-a-Box guide warns that a new server can get an address that is already on a spam blocklist; look yours up before you move mail to it, and ask support if it is listed. Nymhost cannot promise how any receiver treats your mail, and no provider can.
  4. Volume. Google recommends raising volume slowly and keeping the spam rate reported in Postmaster Tools below 0.3%.

The IPv6 trap

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.

Postfix: receive over IPv4 and IPv6, deliver over IPv4 only
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_protocols

Port 25 open from your first Bitcoin payment

Hetzner 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.

VPS plans with port 25 open

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.

Nymhost Offshore

Amsterdam · Reykjavik · Zurich · Bucharest

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
Deploy Offshore 1

Offshore 2

$4.89/ month

3 mo $13.206 mo $23.4712 mo $41.07

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 4 TB traffic
Deploy Offshore 2

Offshore 4

Best balance

$8.19/ month

3 mo $22.116 mo $39.3112 mo $68.79

  • 2 vCPU
  • 4 GB RAM
  • 80 GB NVMe
  • 8 TB traffic
Deploy Offshore 4

Offshore 8

$13.49/ month

3 mo $36.426 mo $64.7512 mo $113.31

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Offshore 8

Offshore 16

$20.49/ month

3 mo $55.326 mo $98.3512 mo $172.11

  • 8 vCPU
  • 16 GB RAM
  • 320 GB NVMe
  • 20 TB traffic
Deploy Offshore 16

Nymhost Global

New York · Dallas · Los Angeles · London · Amsterdam · Frankfurt

Global 2

$3.19/ month

3 mo $8.616 mo $15.3112 mo $26.79

  • 1 vCPU
  • 2 GB RAM
  • 40 GB NVMe
  • 2 TB traffic
Deploy Global 2

Global 4

$6.39/ month

3 mo $17.256 mo $30.6712 mo $53.67

  • 2 vCPU
  • 4 GB RAM
  • 65 GB NVMe
  • 2 TB traffic
Deploy Global 4

Global 6

$9.59/ month

3 mo $25.896 mo $46.0312 mo $80.55

  • 2 vCPU
  • 6 GB RAM
  • 120 GB NVMe
  • 6 TB traffic
Deploy Global 6

Global 8

$19.19/ month

3 mo $51.816 mo $92.1112 mo $161.19

  • 4 vCPU
  • 8 GB RAM
  • 160 GB NVMe
  • 12 TB traffic
Deploy Global 8

Global 24

$29.39/ month

3 mo $79.356 mo $141.0712 mo $246.87

  • 8 vCPU
  • 24 GB RAM
  • 400 GB NVMe
  • 12 TB traffic
Deploy Global 24

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.

Port 25 on a VPS: questions

Which VPS providers have port 25 open by default?

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.

How do I check if port 25 is open on my VPS?

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.

Is port 25 open on Nymhost without a support ticket?

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.

Can I use port 587 instead of port 25?

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.

Why does port 25 still time out on a VPS where it should be open?

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].

Will my mail reach Gmail if port 25 is open?

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.

Can I send newsletters from a Nymhost VPS?

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.

Sources

  1. RFC 5321: Simple Mail Transfer Protocol (section 4.5.4.2) IETF
  2. RFC 6409: Message Submission for Mail (sections 3.1 and 4.3) IETF
  3. RFC 8314: Cleartext Considered Obsolete, TLS for Email Submission and Access (section 3.3) IETF
  4. nc(1) manual page OpenBSD
  5. nc.openbsd(1), package netcat-openbsd 1.229-1 Debian
  6. Ncat Reference Guide Nmap Project
  7. openssl-s_client (-connect, -starttls, -brief) OpenSSL
  8. timeout(1) manual page (exit status 124) man7.org (Linux man-pages)
  9. postconf(5): inet_protocols and smtp_address_preference Debian (Postfix manual)
  10. Email sender guidelines Google
  11. Mail-in-a-Box setup guide Mail-in-a-Box
  12. Amazon EC2 service quotas: restriction on email sent using port 25 Amazon Web Services
  13. Sending email from an instance Google Cloud
  14. Troubleshoot outbound SMTP connectivity in Azure Microsoft
  15. Send email on Akamai Cloud Akamai
  16. Why is SMTP blocked? DigitalOcean
  17. Why is SMTP blocked? Vultr
  18. Cloud servers FAQ (blocked mail ports) Hetzner
  19. How to prevent your emails from being marked as spam (blocked SMTP port) OVHcloud
  20. Is SMTP port 25 blocked on VPS? Hostinger
  21. Unblocking port 25 for sending emails IONOS
  22. Is port 25 open or closed by default? IncogNET
  23. AlmaLinux 10 AppStream packages (nmap-ncat, bind-utils) AlmaLinux
  24. Package dnsutils, provided by bind9-dnsutils Debian