Monitoring
Solutions
Resources
Free Tools
Pricing
Products / Server monitoring / SMTP Monitoring
Outgoing mail server

SMTP Monitoring

Outgoing email is easy to forget until customers stop receiving receipts and password resets. Monitor your SMTP server’s availability and encryption so mail keeps flowing.

9 check locations1–120 min check interval8 alert channels10 monitors free
smtp.example.com:587
Connectionestablished
EncryptionSTARTTLS
Authenticationaccepted
Response time204 ms
Illustrative example of a check result.

When SMTP fails, the damage is silent

Order confirmations, invoices, password resets and alerts all leave through SMTP. If the server goes down, nothing on your site looks broken. Customers simply do not get the email.

An SMTP monitor connects to the server the way a mail client does, over the encryption you use, and warns you the moment it cannot.

What Upzilla checks

Every check is stored in a full log, so you can see exactly when and how something changed.

Encryption modes

Not encrypted, SSL/TLS or STARTTLS, matching your configuration.

Authenticated checks

Supply credentials when the server requires login.

Custom port

25, 465, 587 or any other.

Response time

Watch how fast the server greets connections.

How it works

From sign-up to your first alert in a few minutes.

Enter server and port

Match what your application or mail client uses.

Choose encryption

SSL/TLS or STARTTLS as configured.

Get alerted

Any failed connection triggers your notification channels.

Settings you can control

Sensible defaults get you started; every option below can be tuned per monitor.

SettingWhat it does
Domain / IPThe SMTP server to monitor.
PortPort for SMTP communication, e.g. 25, 465 or 587.
EncryptionNot encrypted, SSL/TLS or STARTTLS.
Username & passwordCredentials if authentication is required.
FrequencyHow often the check runs: 1 to 120 minutes. The Free plan checks from every 15 minutes; Premium from every minute.
LocationsRun the check from one or several of 9 locations: Spain, France, United Kingdom, USA (New York, Los Angeles), Australia, Singapore, Japan and Germany.
NotificationsPick any of your pre-configured alert channels: e-mail, SMS, Telegram, Slack, Messenger, voice call, webhooks and more.
Status pageMake the statistics of this monitor public or private.
TagsGroup monitors with tags to keep large accounts tidy.
IP versionForce IPv4, IPv6, or let Upzilla use whichever is available.
Full setup guide in the documentation →

Common use cases

Transactional email

Protect password resets, receipts and notifications.

Self-hosted mail

Monitor your own Postfix, Exim or Exchange server.

Relay services

Check third-party SMTP relays your app depends on.

Marketing sends

Confirm the server is up before a large campaign.

Alerts where your team already is

Create as many notification methods as you like, even on the free plan.

Slack
Telegram
Telegram group
Facebook Messenger
Email
SMS
Voice call
Webhooks

Related monitors and tools

Mail Server MonitoringIMAP MonitoringPOP3 MonitoringDNS MonitoringTCP/UDP port numbers (free tool) →

Questions about smtp monitoring

Which port should I monitor?

Use the port your application sends through: usually 587 (submission with STARTTLS), 465 (implicit TLS) or 25 (server-to-server).

Does it send a test email?

It checks the connection and, if configured, authentication. It does not deliver messages.

Can I monitor incoming mail too?

Yes, add POP3 or IMAP monitors, or see Mail Server Monitoring for the full picture.

Is my password safe?

Credentials are only used for the check you configure. Use a dedicated low-privilege account where possible.

Make sure email keeps leaving

No card required. 10 monitors of any type, free.

Create free account →