Instead of using wildcard or catch-all on a domain, I usually recommend folks use a nonsensical (not easy to guess) alias "address" and sub-address aliasing. So, like
com+apple@domain.com, where "com" is the address alias, and addresses are kind of in "reverse Java notation", only with "+" instead of ".". This makes it much easier to clamp down on all the garbage you get using wildcard/catch-all, while keeping all the benefits of filtering. Can use b2c+ or whatever. Then block delivery to messages sent only to the alias address.
HOWEVER… although iCloud allows "+" sub-address aliasing, apparently this Custom Domain feature does NOT, according to a poster over at 9to5Mac who tested it for me. Which is lamentable. A missed opportunity, IMHO.
Outlook-dot-com allows aliases and "+" sub-address aliasing; Gmail only supports "+" sub-address aliasing. (Providers using qmail will use "-" instead of "+; which I prefer, since "-" had been in use for quite a while, so truncating addresses on the "-" generally gets you a failed delivery, whereas dropping the "+" and "tag" gets you a legit Gmail address.) Really need to support both for things to work best. So Apple is supporting aliasing… but not sub-address aliasing… yet, I hope.
Others are also reporting that Custom Domain doesn't allow single-letter addresses. Which I use. Grrrr. Not sure why that would matter.