iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
You can create and verify a sending domain through an email provider’s API without using an SMTP relay for that management work. The APIs can create a domain or identity, show the DNS records to publish, and report verification status; you or your DNS automation still need to publish those records. Domain verification confirms configuration, not inbox placement.
“Without SMTP relay” can also mean submitting messages over an HTTP email API rather than to an SMTP endpoint. That is a separate choice from managing a domain: domain setup and verification use management APIs, while message submission uses the transport you select. Amazon SES, for example, supports SMTP for sending, but its identity-verification workflow is separate.
What the provider APIs can do
Mailgun, Amazon SES, Twilio SendGrid, and Postmark document API workflows for creating or managing sending domains and checking at least some configuration status. Their APIs do not eliminate the DNS step: the domain owner must publish the provider’s records at the authoritative DNS host, unless a separate DNS integration or automation has been granted access.
Recommended Free Tools
The workflow is generally: create a domain or identity through the provider API, retrieve the required DNS values, publish them, then request or poll for verification. Exact records and status fields depend on provider and configuration.
#1 Best Overall
- Fortinet FortiMail-VM virtual appliance for all supported platforms. 8 x vCPU cores
- Fortinet SW FML-VM08
- Manufacturer Part: FML-VM08
Provider workflow comparison
| Provider | API setup and checks | DNS work | Important distinction |
|---|---|---|---|
| Mailgun | The Domains API manages domains and provides a verification operation. | Publish SPF and DKIM TXT records for authentication. A tracking CNAME and inbound MX records apply to optional tracking or receiving functions. | Mailgun says DNS propagation can take 24–48 hours; treat that as its guidance, not a guaranteed or universal interval. See Mailgun domain verification. |
| Amazon SES | SES supports domain identity verification through API calls and status queries such as GetEmailIdentity. | Publish TXT or CNAME records depending on identity and DKIM method. | Verification is separate from the sending transport. SES also supports SMTP for sending. See identity verification and authentication methods. |
| Twilio SendGrid | The domain authentication API documents creation; a separate endpoint validates an authentication setup. | With Automated Security, the docs describe three CNAME records. With it disabled, the documented setup uses TXT and MX records. | Requirements depend on configuration. See validation API and authentication documentation. |
| Postmark | The Domains API can create and list domains, return DNS and status fields, and request DKIM verification. | Publish the DKIM TXT record. A custom Return-Path uses an optional CNAME. | Postmark’s DKIMVerified field means the domain has been verified at some point, not necessarily that the DNS record is still present. Its SPF verification API is deprecated. |
What the DNS records establish
SPF, DKIM, and DMARC do different jobs. SPF is a DNS TXT policy that identifies sending hosts authorized for an envelope domain. DKIM lets the sender sign a message with a private key; receiving systems can use the corresponding public key published in DNS to check that signature. DMARC adds policy and reporting and checks whether SPF or DKIM authentication aligns with the domain visible in the From address. AWS describes DMARC compliance as achievable through SPF or DKIM, while recommending both for stronger protection. See SendGrid’s authentication overview and AWS’s DMARC documentation.
A provider’s “verified” state is a configuration signal, not proof that messages will reach inboxes. The cited provider documentation describes setup and verification, not a comparable independent deliverability benchmark.
Implement the setup loop safely
- Create the domain or identity. Call the provider’s documented endpoint using the correct account credentials and permissions. For SES, this is an email identity; other providers expose domain-oriented operations.
- Read the generated DNS values. Store the record name, type, and value exactly as returned. Record which feature each value supports, since tracking and inbound mail may require records beyond sending authentication.
- Publish records at your DNS host. The email provider generally supplies the records; it does not publish them in your DNS zone unless you have separately connected or authorized a DNS automation system. Avoid creating a second SPF policy at the same hostname. If an SPF record already exists, integrate the provider’s authorization into the existing policy; Mailgun’s setup guide flags this situation for attention.
- Request or poll for verification. Use the provider’s verification or validation endpoint where available. Allow for DNS propagation; repeated checks immediately after publication can still report pending or missing records.
- Interpret status according to that provider. Do not assume that similarly named booleans have identical meaning. Postmark’s DKIMVerified field, for example, reflects whether verification has ever occurred, so an integration should not treat it as a live DNS health check.
How to choose between the workflows
These sources establish documented management capabilities, not a winner for cost, support, sending throughput, or inbox placement. Compare the operational details that affect your implementation:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Whether the API supports the full domain lifecycle you need: creation, record retrieval, verification, status checks, and removal.
- What API credentials and permissions are required, including whether setup can be automated safely in your account and region.
- How many DNS records are required for your chosen configuration, and whether optional tracking or receiving features add records.
- Whether status fields report current DNS state or historical verification, and how the API represents pending, failed, or changed records.
- How DKIM key rotation and custom return-path settings fit your DNS and deployment process.
- How your integration handles propagation delays, retries, and DNS changes after initial verification.
Check each provider’s current documentation for endpoint behavior, account constraints, pricing, and availability; these details can change. Do not use a verified-domain flag as a substitute for monitoring authentication configuration or evaluating actual message outcomes.
Quick Recap
Best Value
- 【Processor & OS】Firewall Mini PC with Intel J4105 CPU up to 2.5GHz, 4Cores4threads 4MB L2 Cache, TDP 10w, supports AES-NI. It tested with pf-sense linux ubuntu and other popular open source OS. ("DEL" key to enter BIOS)
- 【Interfaces】The firewall pc has 4 * Intel 2.5GbE I226 lan ports, 2 * USB3.0 ports, 1 * VGA port, 1 * HD port, 1 * DC port. Equipped with VESA mount, you can install the micro pc behind the monitor to save space.
- 【DDR4 RAM & mSATA SSD】The firewall router equipped with 8G DDR4 RAM, max support 16GB; 240GB mSATA SSD equipped, can be up to 512GB. Not support HDD.
- 【Fanless Design】The small firewall box is only small but powerful. Low power consumption, only 10W; fanless heat dissipation design, aluminum alloy shell, efficient and fast heat dissipation, support 24/7 hours working, no noise. Fanless mini PC, silent, with heat dissipation through the casing, which can withstand temperatures up to 60°C
- 【12 Months Service】You will get 1*mini pc，size:5.27 * 4.98 * 1.43 in weigh:500g. If you encounter any problems during the use, please contact us through Amazon, we have a professional and efficient team dedicated to serving you.
Rank #3
- Model: RHTx-IoT1; SMS(4G/LTE Version) + Email + Cloud hosting to User End | Measuring Parameters: Temperature, Relative Humidity | Temperature Range: 0 to 50°C; Accuracy: ± 0.5°C; Resolution: 0.1°C | Relative Humidity: 0 to 100% RH; Accuracy: ± 2% RH; Resolution: 0.1 %RH |
- Display: 128 X 64 Dot Matrix Graphical Large LCD Display with White Backlight | Operating Temperature: Safe operating temperature of instrument is 0°C to 70°C | Cable Length: Connecting Cable, pre-wired 3 mtrs. Extension between display monitor & sensor.
- Buzzer: Standard In-Built Buzzer for Alarm (External Buzzer also available - Contact Store) | Alarm Type: In built buzzer for Low & High Limit upon temperature set point violation, approx. 50 Decibel | Alarm Limit: User Configurable, freely programmable from 4 front keypad |
- Acknowledgement Key: Provided for user to acknowledge the alarm manually, thus avoiding continuous buzzer alarm sound & user attention | Sensor Type: 1. Polymer sensing for Temperature 2. Capacity polymer sensing for Relative humidity 3. Option of Extending Audio Visual Buzzer to 24/7 Surveillance/Security Rooms | Power Supply: 12 VDC Input with minimum of 2-amp current rating. Adaptor provided alongwith | Enclosure: Wall mounting type ABS
- Supply Scope: 1 Unit of RHTx-IoT Temperature Humidity Monitor, Antenna, Power Adaptor, Instruction Manual and Factory Calibration Certificate | Applications: Server Rooms, Datacenters, Cold Chains, Pharmaceuticals, Bio-Medical, Warehouse, Hospitals, Seed Storages.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
