Source
Features page (SMTP relay) — Elastic Email API
Checked for Elastic Email API on 1 Nov 2026
- Page
- https://elasticemail.com/smtp
- Checked
- 1 Nov 2026, 09:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:420ada7c563b0ee77f02cbdad9a7ce1fbf2e4f50851a5754ab1ede41e1e387ad
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Smtp relay Report an error
“Powerful SMTP Relay Service A reliable SMTP relay with fast setup, strong deliverability, and real-time logs. No code required to get started.”
-
Smtp free tier Report an error
“100 emails/day free”
-
Setup time Report an error
“Get your SMTP credentials in under a minute”
-
Smtp setup steps Report an error
“Sign up or log in to your Elastic Email account 02 Go to Settings → SMTP and click “Create credentials” 03 Copy your host, port, username, and password and paste it wherever you need”
-
Transactional emails Report an error
“Send transactional email — receipts, password resets, one-time codes — straight from your app or server via SMTP.”
-
Campaigns via smtp Report an error
“Send campaigns through self-hosted tools like Sendy or MailWizz, and pay only for emails sent, not contacts stored.”
-
In house mta Report an error
“Maximize your email reach with our own in-house made mail transfer agent that ensures high deliverability and inbox placement rates.”
-
No coding required Report an error
“Empower your email sending that requires zero programming knowledge. Simply create SMTP credentials and add them to your domain.”
-
Unlimited credentials Report an error
“There is no limit to the number of SMTP credentials you can create.”
-
Video guide Report an error
“Discover the power of our SMTP relay through our comprehensive video guide. Watch step-by-step how to create and configure SMTP credentials, and launch an SMTP connection on the example of WordPress.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Agency Lead Sending API, SMTP & developer experience
- The Data Protection Officer Sending API, SMTP & developer experience
- The Shop Operator Sending API, SMTP & developer experience
- The Platform Engineer Sending API, SMTP & developer experience
- The SaaS Developer Sending API, SMTP & developer experience
- The Skeptic Sending API, SMTP & developer experience