Alerts

⚠️ mail.et Is Currently Non-Functional — DNSKEY Failure at the .et Registry

2026-04-16 15:00:00 · 1 Views · Edited at 2026-04-16 18:26:51

⚠️ mail.et Is Currently Non-Functional

Affected domain: @mail.et
First observed: January 2026
Status: Unresolved — awaiting response from the .et registry

Dear Mail.sb Users,

We owe the mail.et community a long-overdue public update. Since January 2026, mail.et has been effectively non-functional for email due to a DNSKEY / DNSSEC chain-of-trust failure at the .et registry level. We've known about this from very early on, we've tried repeatedly to get it fixed on our side, and we have so far been unable to get a reply from the .et registry. We're sorry — both for the service impact and for how long this notice has taken to post.

What's actually broken

The DNSSEC chain is signed at each level: the root delegates to .et, and .et delegates to mail.et. For DNSSEC-validating resolvers to trust records under mail.et, the .et registry must publish a matching DS record for our DNSKEY. That delegation is currently wrong — the DS at the registry doesn't match our active DNSKEY — so any validating resolver returns SERVFAIL when looking up mail.et.

In practice this means:

  • Outbound mail fails. Receiving mail servers that validate DNSSEC (and most large providers do, either directly or via DANE/MTA-STS lookups) cannot resolve our SPF, DKIM, or MX records, so mail from @mail.et is rejected or silently dropped as unauthenticated.
  • Inbound mail fails. Sending mail servers cannot reliably resolve the mail.et MX records for the same reason, so messages addressed to @mail.et bounce at the sender's side before ever reaching us.
  • Webmail and login sometimes fail. Users on DNSSEC-validating networks may also be unable to reach webmail.mail.et / API endpoints on the mail.et hostname.

What is not affected

Your mailbox data is safe and untouched. The domain itself is still registered and fully under our administrative control — this is not a domain loss, not a hijack, and not a data issue. Specifically:

  • All stored mail, folders, filters, contacts, and settings remain intact on our servers.
  • Your account credentials continue to work — you just can't currently exchange mail over the @mail.et identity.
  • If you also hold addresses on other mail.sb domains (@mail.sb, @mail.ss, @mail.tl, etc.), those are unaffected and continue to operate normally.

What we've tried

Since first recognising the problem in January we have:

  • Re-rolled our DNSKEY set and re-submitted matching DS records to the registry, multiple times.
  • Tested via independent DNSSEC validators (Verisign DNSViz, Google dns.google, Cloudflare 1.1.1.1) to confirm the break is at the .et zone cut — not in our authoritative servers.
  • Contacted the .et registry repeatedly through every official channel we could identify.

To date we have not received any reply. The technical fix is a single registry-side operation, but without their cooperation we cannot force it through.

What happens next

As soon as we get a response from the .et registry and the DS delegation is corrected, full service on @mail.et will restore automatically — typically within one DNS TTL window after the fix. We will post a follow-up announcement the moment that happens.

In the meantime, if @mail.et is your primary address and you need working mail right now, we recommend adding an alias on one of our other domains from your dashboard and using that as your active sending/receiving identity until this is resolved.

We're genuinely sorry for the disruption. Thank you for your patience.

— Mail.sb Team

Comments (0)

No comments yet. Be the first!

Leave a comment

FAQS

Got questions?
Well, we've got answers.

Icon
General inquiries

New around here? Start with the basics.

Icon
Permissions & Privacy

Rule by doing nothing.

Icon
Pricing & Plans

Visible at mail.sb/i/ after login.

Icon
General inquiries

New around here? Start with the basics.

What is mail.sb(@mail.sb)?

mail.sb (@mail.sb) is a basic mail service provider, we put privacy at the very first place. We gurantee that we do NOT save / record your password in plaintext in any way, we won't be able to see your password. We do NOT ask for any personal information to create an account with @mail.sb, THIS IS WHAT WE AIMED.

WHO can create a @mail.sb account?

Any species.

If you are a recipient of a email that sent from @mail.sb, you should know:

Carefully check the authenticity of the content of the email, and check the identity and credibility of the letter. Due to mail.sb's policy of highly respecting privacy, we cannot confirm the personal information of the mail holder and its authenticity for you. Please be very vigilant with your contacts on the Internet. To report serious abuse, please contact [email protected].

Will I not be sanctioned if I spam or abuse the @mail.sb service in any way?

Absolutely wrong! If you have this kind of thinking, it means that you have or have tried this at the same time, which is very unethical and dangerous, because it means that you will also engage in similar behavior on other platforms. Although @mail.sb does not use any content analysis AI (privacy first), the official staff of @mail.sb will not obtain your email content in any way, but if we receive reports of inappropriate emails sent by your mailbox In all cases, we will ask the complainant to reply to [email protected] with the content of the inappropriate email. After verification, your mailbox will be permanently banned. Email functionality. If you are dissatisfied with how @mail.sb has been banned, you can file a complaint and a reply will be posted at mail.sb/i / at Shown within 24 hours.

Icon
Permissions & Privacy

Rule by doing nothing.

@mail.sb knows my password and monitors my email activity.

You are wrong, we are not FBI or CIA. We have no intention of peeking at your content, not even if we had the time. From a cost standpoint, no one wants to spend time reading your emails, time could be better spent elsewhere. From an ethical standpoint, we promote the concept of privacy when providing this service. If we violate this principle, we should not continue and will not to operate. Technically, from the moment you sign up, your password is encrypted using one-way AES-256, and we cannot recover it, nor can you log into your mailbox. While it has been explained above how our privacy is paramount, there are always people who believe in conspiracy theories, (even the board members of this site believe in some conspiracy theories, XD). If you don't believe it, don't use @mail.sb. This is the position and statement of this site. If you do not agree, you can refuse to use the services of this site.

Icon
Pricing & Plans

Visible at mail.sb/i/ after login.

Pricing & Plans

Visible at mail.sb/i/ after login.

Your privacy matters

We use cookies to provide our services and for analytics and marketing. To find out more about our use of cookies, please see our Privacy Policy and Cookie and Tracking Notice. By continuing to browse our website, you agree to our use of cookies.
Settings