- 680comments
- 897comments
- 381comments
- 167comments
- 11comments
- 378comments
- 83comments
- 40comments
- 296comments
- 3comments
- 125comments
- 112comments
- 93comments
- 80comments
- 282comments
- 95comments
- 22comments
- 4comments
- 162comments
- 204comments
- 91comments
- 22comments
- 9comments
- 35comments
- 13comments
- 59comments
- 502comments
- 15comments
- 1comments
- 14comments
DMARC-verified-sent from a legitimate [...] domain? -> Someone pwned a mailbox at an agency? I'm sure they would've spun the story into "the government was hacked, not us" in that case.
Or "sent from" a legitimate [...] domain? -> Spoofed envelope sender / FROM? Then Revolut's simply been had by the nose. If the domain is indeed a government domain, and does not publish DMARC records, then a due diligence check on who they're sending such personal info (ie, call that purported government agency up on the phone) would suit them.
After all, they're very pedantic about me running their app on a phone with an unlocked bootloader. I'd then hope that they'd be symmetrically pedantic about verifying whoever they're sending my info to.