Let your email land in the inbox, not the spam folder
Manage transactional email delivery and inbound email security in one place. The sending API is Amazon SES compatible (SigV4) — if you use SES, you only change the endpoint and never touch your code.
If your invoice email does not reach the customer, the service is not working
When password reset, order confirmation and invoice emails land in the spam folder, you usually notice it only when a customer complains. MailGuard measures deliverability, warns you before a problem arises and shows who opened what.
With the SES-compatible API (AWS SigV4), change only the endpoint in your existing AWS SDK; plus SMTP relay and our own REST API.
Track bounce, spam complaint and open rates per domain.
Verify your records from the panel; missing configuration raises a warning.
Detection of spoofed senders and malicious links in inbound emails.
Version your transactional email templates; do not wait for a software deployment.
See pending and failed sends and retry them with a single click.
Integrations
It works without touching your application's sending layer; you only need to change the SMTP details.
Compliance
Packages
Outbound email is priced per 1,000 messages; inbound email security is offered by quote based on your mailbox/user count.
MailGuard — frequently asked questions
No. Our sending API is Amazon SES compatible and accepts AWS SigV4-signed requests. In your existing AWS SDK (boto3, aws-sdk-js, PHP, .NET, Go) you only point the endpoint to MailGuard and use the access key MailGuard provides; your SES send calls work as they are. If you prefer, you can also send via SMTP relay or our own REST API.
Emails mostly land in spam due to missing SPF/DKIM/DMARC records, low IP reputation or unauthenticated sending. MailGuard verifies these records from the panel, signs your sending identity and, by monitoring reputation signals, moves delivery into the inbox.
When you add your domain, MailGuard generates the required SPF, DKIM and DMARC records and shows them for you to add to DNS. Once the records are published, the panel checks verification automatically and warns you of missing or incorrect configuration.
Both are possible. You can point your existing application's SMTP settings to MailGuard or send via the REST API. In environments such as Laravel, Django, Node.js and WordPress, a few lines of configuration change are enough.
MailGuard collects the DMARC feedback reports sent on behalf of your domain and makes them readable. You see who is trying to send email in your name and, by tightening the policy step by step (none → quarantine → reject), block spoofed sending.
In the Sending + Protection plan, inbound emails are also scanned: spoofed sender (spoofing) and phishing attempts are detected, and malicious attachments and links are quarantined. You manage the quarantine from the panel and release anything wrongly flagged.
Yes. You can archive inbound and outbound emails in a tamper-proof form and keep them safely for the retention period you set. You search the archive quickly and, in an audit or dispute, find the relevant correspondence in a short time.
Commercial message consent and opt-out records are kept; consent status is synchronized with the Message Management System (İYS). This way you do not send without permission and stay compliant with KVKK and commercial message legislation.
In the enterprise plan a dedicated sending IP is allocated to you, and to protect its reputation we run the gradual IP warm-up process together. This ensures a consistent delivery rate for high-volume sending.
What teams using MailGuard say
Let us measure your domain's delivery score for free
We scan your SPF, DKIM and DMARC records and report which of your emails land in spam and why.