Suspended AWS account, root email broken because Route 53 domain stopped resolving, verification document upload link can only go to root email — what can I do?

I’m in a really strange situation and I’m hoping someone here has seen this before.

My AWS account was suspended pending verification. AWS says the account is still in a recoverable state and can be reinstated if I submit the required verification documents. The problem is that the required secure upload link can only be sent to my root user email address. Unfortunately, my root email address uses a custom domain that is registered through Route 53, and after the suspension, the domain stopped resolving. External DNS lookups for the domain return nothing (NS, MX, and TXT all come back empty), so email to that address is bouncing.

So I’m stuck in this loop:

• AWS Account Verification says they can only send the secure upload link to the root email
• They say they cannot change the root email while the account is suspended
• Route 53 / domain-related help was basically deferred because the account verification issue has to be resolved first

One AWS support rep told me an exception had been approved to upload documents directly through the support case, but when I did that, another rep deleted the message and said documents can only be accepted via the secure link.

AWS support has since confirmed:

• the verification email they sent bounced back
• my account is still recoverable for up to 90 days from suspension
• if I can complete verification, I should be able to regain access

I’ve already:

• provided proof of address, ID, payment instrument proof, and business registration docs
• repeatedly explained that the root email is unreachable because the Route 53 domain/email path is broken

At this point I’m trying to figure out:

1. Has anyone seen a way out of this kind of deadlock?
2. Is there any AWS support path that can actually help restore the root email delivery path while the account is suspended?
3. Is there any known way to get Account Verification to honor an alternate submission method when the root email itself is inaccessible?

I just want to know whether there’s a legitimate support path or escalation route that can break the circular dependency. Any advice would be greatly appreciated.