Skip to content

2026-10-08

Relay aliases scored on what they show, 23 more alias domains, and Amazon SES told apart from the rest of AWS

mailbox_confidence on a relay alias no longer counts the relay operator's DMARC, SPF and domain age. Surfshark Alternative ID, IronVest Masked Email, Erine.email, Alias Email, Guard Email and more Addy.io and 33Mail domains answer as relays. Only Amazon's inbound mail hosts read as amazon-ses, and a delivery report no longer says a domain is not catch-all.

  • mailbox_confidence on a relay alias stays at 50. It used to add the relay operator's DMARC, SPF, mail provider and domain age, and to score the alias's name, which says nothing about whether one alias exists, so a made-up alias at bravealias.com scored 75. Now only evidence against the alias moves it: a bounce rate of 50% or more among the sends reported for the domain takes 20 off, and a plus-tag takes 10. A sending policy with a min_mailbox_confidence above 50 may now hold catch-all relay aliases it used to let through; the default policy sets no floor.

  • 23 more alias domains answer as relays. They are:

    • Surfshark Alternative ID: ten domains, such as flounderfantasy.com and dontsp.am.
    • IronVest Masked Email: opayq.com, and Abine's older abinemail.com, blurmail.net, blurme.net and maskmemail.com.
    • Erine.email: erine.email and erine.eu.
    • Alias Email: bumpmail.io.
    • Guard Email: m.guardemail.com and m1.guardemail.com.
    • Addy.io: 4wrd.cc and addy.to.
    • 33Mail: 33m.co.

    Several sat on the open burner list, so an address there could answer disposable with the 80-point weight and no mailbox check. They now answer is_relay true with their relay_service. Cloaked's identity domains are not listed, because Cloaked keeps identity mail in its own inbox unless the owner turns forwarding on. Lookups already logged were relabelled for the email statistics.

  • Only Amazon's inbound mail hosts read as amazon-ses. Any mail host named under amazonaws.com used to answer mx_provider amazon-ses and mx_provider_type transactional, including an EC2 instance, a load balancer or an SES Mail Manager gateway. Now only inbound-smtp.{region}.amazonaws.com, which SES receiving and WorkMail use, does; the rest answer other. Domain monitors start a fresh provider baseline for the domains they last saw as amazon-ses, so the relabelling sends no alert. The mx-provider-patterns version is 2026-10-08.

  • A delivery report no longer says a domain is not catch-all. An address your account reported delivered answers as a confirmed mailbox. Its catch_all used to read false, even at a domain known to accept every address. It is now null, because the report says nothing about the rest of the domain. The verdict, score and billing are unchanged.

  • Domain pages describe relay domains as alias services. The domain checker pages called a relay domain an organisation's own domain, and called Amazon SES "a transactional or application setup". They now name the relay service and say it forwards each alias to its owner's inbox.

  • The forwarding-services dataset version is 2026-10-08.

markdown version: /changelog/2026-10-08-relay-confidence-23-more-alias-domains-and-amazon-ses-told-apart-from-the-rest-of-aws.md · atom feed: /changelog.atom

All releases