Testing $12/year hosting: ServerByt email, SPF, DKIM and DMARC
I tested ServerByt Blaze with my own domain, external authoritative DNS, and real Gmail delivery checks to see whether ultra-low-cost hosting could provide technically sound custom-domain email.
Why I tested it
The ServerByt Blaze plan was unusually inexpensive at $12/year when I purchased it. My main question was not whether I could create a mailbox, but whether mail from that domain could reach a major provider with proper authentication and land in the inbox.
Test environment
- Hosting: ServerByt Blaze
- Control panel: StackCP-based interface
- Email infrastructure: Stackmail
- Test domain: sziget.me
- Authoritative DNS: Spaceship
- Delivery target: Gmail
I intentionally kept authoritative DNS at Spaceship instead of moving the domain's nameservers to ServerByt. That meant the records ServerByt generated had to be published in the actual authoritative DNS zone.
sziget.me | +-- Authoritative DNS: Spaceship | +-- MX --------> Stackmail | +-- SPF -------> authorized senders | +-- DKIM ------> public key | +-- DMARC -----> authentication policy | +-- webmail ---> StackCP | +-- Email hosting: ServerByt / Stackmail
SPF
I published the Stackmail authorization in DNS:
v=spf1 include:spf.stackmail.com a mx -all
Gmail result: SPF: PASS.
DKIM
I generated DKIM through ServerByt's Domainkeys interface using selector s1, then published the public key at the authoritative DNS provider.
Gmail result: DKIM: PASS.
DMARC
For the initial test I used a p=none monitoring policy with relaxed DKIM and SPF alignment. This let me validate alignment without immediately requesting quarantine or rejection of failures.
After DNS propagation, Gmail reported DMARC: PASS.
Final result
One Gmail test reported roughly 3 seconds of delivery time. The message landed directly in Inbox rather than Spam. A reverse Gmail-to-Stackmail test also arrived essentially immediately.
What worked well
- Fast outbound delivery to Gmail
- Inbox placement during the test
- SPF, DKIM and DMARC all passed
- Working webmail
- Standard IMAP and SMTP support
- Multiple-domain support
- One-click WordPress and other applications available
Quirks I encountered
External DNS
ServerByt shows a DNS Zone inside its control panel, but those records are not authoritative when the domain uses different nameservers. Because Spaceship remained authoritative for sziget.me, I had to publish the required mail records there.
Webmail redirect
The Webmail button for a mailbox on a secondary domain initially tried to open the webmail hostname of the hosting account's primary domain. Opening the correct webmail.sziget.me hostname directly worked.
Payment process
Checkout was not completely smooth in my case. I had to repeat the payment process several times before the purchase completed.
What this lab demonstrated
The most useful lesson was the separation of roles between registrar, authoritative DNS provider, web host and email provider. A DNS record shown inside a hosting control panel does not matter to the public Internet unless it exists in the authoritative DNS zone.
Initial verdict
For $12/year, the first technical result was surprisingly strong:
SPF PASS + DKIM PASS + DMARC PASS + Gmail Inbox
This is still an initial hands-on test, not a long-term endorsement. Before using the service for business-critical workloads, I would want longer testing of uptime, backups, support and application performance.
Next tests
- 30-day uptime experience
- WordPress installation and performance
- SSL/HTTPS behavior
- Backup and restore
- Support response time
- IMAP/SMTP on Android and iPhone
- Longer-term Gmail and Outlook deliverability