Fintech giant Revolut says my DNS failed — Cloudflare, can you verify?
Hi all,
I’m looking for guidance on a mail delivery issue with Revolut (fintech company, sends from no-reply@revolut.com
On 2 Sept 2025, Revolut claimed they couldn’t deliver verification emails to my domain due to:
421 4.4.4 [internal] Domain Does Not Resolve
Their tech team insisted their systems (including DNS resolvers) were fully operational.
But here’s what happened:
My DNS/MX records haven’t changed in years and validate fine.
I receive mail instantly from Gmail, banks, test services.
Revolut’s emails eventually arrived, but only hours later in a batch — looks like sender-side resolver/cache refresh, not my DNS.
Logs show no delivery attempts from Revolut during the failure window.
MX records (unchanged well before the issue):
exampledomain.com route3.mx.cloudflare.net 11 DNS only Auto
exampledomain.com route2.mx.cloudflare.net 97 DNS only Auto
exampledomain.com route1.mx.cloudflare.net 86 DNS only Auto
What I’d like confirmed: Are these MX (plus A/AAAA/SPF/DNSSEC) healthy/propagated? Could Cloudflare resolvers have shown issues around 19:55–23:10 BST, 2 Sept 2025? Any chance of negative caching/delegation issues on Cloudflare’s side, or does this clearly point to Revolut? I’d really appreciate it if someone from the Cloudflare team could DM me with an on-record acknowledgement that Cloudflare’s DNS/email services were working correctly, so I can take that back to Revolut support. I can also provide headers from the delayed Revolut emails if useful. Thanks in advance.
exampledomain.com route2.mx.cloudflare.net 97 DNS only Auto
exampledomain.com route1.mx.cloudflare.net 86 DNS only Auto
What I’d like confirmed: Are these MX (plus A/AAAA/SPF/DNSSEC) healthy/propagated? Could Cloudflare resolvers have shown issues around 19:55–23:10 BST, 2 Sept 2025? Any chance of negative caching/delegation issues on Cloudflare’s side, or does this clearly point to Revolut? I’d really appreciate it if someone from the Cloudflare team could DM me with an on-record acknowledgement that Cloudflare’s DNS/email services were working correctly, so I can take that back to Revolut support. I can also provide headers from the delayed Revolut emails if useful. Thanks in advance.
1 Reply
Any chance of negative caching/delegation issues on Cloudflare’s side, or does this clearly point to Revolut?It can point in any direction, which would be impossible to say for sure, without knowing the actual domain name.
I’d really appreciate it if someone from the Cloudflare team [...]If you insist on the actual team, you may have ended up in a wrong place, as this is a "community" Discord... In a such case, you will need to create a ticket. Assuming though, that you're willing to continue here, for a potential speedier "look" at your case: What is the actual domain name, that Revolut has issues sending to?