SNDS authorization only shows AWS RDAP contacts instead of reverse DNS postmaster/abuse addresses for AWS Elastic IP

Harsh Gandhi 0 Reputation points
2026-08-03T11:59:19.4933333+00:00
  1. Why is SNDS not offering ******@domain.com or ******@domain.com even though the reverse DNS is correctly configured and forward-confirmed?
  2. Is this expected behavior when using AWS Elastic IPs for a self-hosted mail server?
  3. Is there an alternative verification method for customers using dedicated AWS Elastic IPs to complete SNDS registration?
  4. Since JMRP requires SNDS access, how can customers using AWS-hosted mail servers complete the verification process and enroll in JMRP if only AWS RDAP contacts are presented?
Outlook | Web | Outlook.com | Account management, security, and privacy
0 comments No comments

1 answer

Sort by: Most helpful
  1. Chloe-V 13,790 Reputation points Microsoft External Staff Moderator
    2026-08-11T08:48:32.14+00:00

    Hi Harsh Gandhi

    I understand how difficult this situation is, especially when your reverse DNS is correctly configured but SNDS still shows only AWS RDAP contacts.

    Since the Elastic IP is registered to AWS, the authorization options may be based on AWS’s IP ownership information rather than the postmaster or abuse addresses for your domain. In this case, please contact Microsoft Sender Support and explain that SNDS is showing only AWS RDAP contacts, preventing you from completing SNDS authorization and JMRP enrollment.

    When submitting the request, include the affected IP address, the reverse DNS hostname, confirmation that forward and reverse DNS match, and evidence that the Elastic IP is assigned to your AWS account. Please note that Support can review the situation, but a manual authorization or alternative verification method cannot be guaranteed.

    You may also need to contact AWS Support, as AWS remains the registered owner of the underlying IP range.

    Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas only.

    Thank you for your understanding. 


    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.