Url looks suss. Seems kinda sophisticated for the usual ups fishing scam. Here's the text message I got leading here.
"Wishing you a bright and sunny day!"
Lol, I almost want to help this guy by explaining that UPS and American companies in general have disdain for their customers and would never wish them to have anything that would not benefit the company.
What annoys me is when legitimate companies use non-standard URLs in their hyperlinked emails. For example, if you get a message from Facebook taking you to facebookemail.com, that's actually a domain controlled by the real Facebook.
They're essentially teaching their customers to click on links in emails which use unfamiliar URLs which are superficially similar to the usual one.
They probably want to separate their customers from getting up to stupid spammy behaviour and getting the domain blacklisted from their ability to deliver their own official Facebook email notifications. There probably ought to be better ways to do that, but the fact Facebook went "yeah, we gotta register the shitty domain facebookemail.com" makes me think they're working around a crappy limitation of smtp email.
There ought to be no limitation with, say, email.facebook.com. Sure, have the domain facebookemail to prevent bad actors grabbing it, but only use it as a redirection.
I don't think there's mail server software in existence that would choke on a subdomain like that. There might be a few mail admins too easily confused to be able to set it up, but I doubt there are any of those at Facebook.
That said, most people aren't going know that a subdomain is safer than a legitimate looking alternative, so maybe it's all moot.
Tangentially, it seems that someone has squatted on facebook-email.com (note the hyphen), so I expect that Zuck's lawyers are crawling all over whoever's done that.
I'm not up to speed on exactly how spam filters blacklist domains but I strongly suspect if Gmail thought spam was coming from email.facebook.com then it would restrict facebook.com too. That's the only reason I can think of for creating such a clunky domain; it's that a neater looking sub domain won't avoid the problem - hence having to register something completely different.
That sounds like a preference that would be added by whoever configured the server rather than anything else. I've definitely seen situations where a third-level domain has been under the control of (or sold to) a third party and so it wouldn't make sense to block the second-level, or other third-levels branched off from it if only one third-level misbehaved. Edit: And I don't just mean countries that treat second-level as top-level for some uses, like, say .co.uk.
I have no idea what the defaults are for various automatic spam blockers, since both arguments have merit.
Congratulations, you belong to the 3% of users who know what a domain is and why that matters. Everyone else uses Google (or DuckDuckGo because "Google bad") to search for their favorite websites every time.