Why can't I see the correct email addresses for SNDS verification?

This can happen due to issues like Microsoft's internal systems being unable to query RIPE data, which prevents the SNDS portal from displaying the appropriate postmaster or abuse email addresses for verification. It means the automatic authorization process is hindered.

What is the RIPE block and how does it affect SNDS?

The RIPE block refers to a situation where Microsoft's IPs were reportedly blocked at the RIPE NCC, an internet registry. This can prevent Microsoft's SNDS system from performing necessary rDNS and WHOIS lookups to verify IP ownership and authorize access requests, leading to errors and missing verification options in the portal.

How should I request SNDS access if I use Salesforce Marketing Cloud?

If you use Salesforce Marketing Cloud (or other ESPs), SNDS access for dedicated IPs is typically managed by the ESP. You should follow your ESP's specific procedures to request access or inquire about deliverability for those IPs. If you're encountering issues, contact Salesforce support directly .

Can I manually request SNDS access from Microsoft?

No, the SNDS system is designed to be fully automatic for signup and maintenance. Manual requests are generally not processed. This means you must rely on the system's ability to automatically identify the correct verification email addresses.

What should I do if my SNDS data is not displaying or delayed?

If your SNDS data is not displaying or delayed , first check if there are known widespread issues affecting Microsoft's services . If you rely on an ESP, contact their support. Additionally, ensure your DNS records (SPF, DKIM, DMARC) are correctly configured and monitored with a tool like Suped.

Is Microsoft SNDS experiencing issues with access requests? - Troubleshooting - Email deliverability - Knowledge base

Many email senders rely on Microsoft's Sender Network Data Services (SNDS) to monitor their sending reputation and ensure emails reach

Outlook.com inboxes. However, there have been recent reports and discussions indicating that Microsoft SNDS might be experiencing issues, specifically with access requests and the visibility of required email addresses for verification. This can be particularly frustrating for those managing email deliverability, especially when dealing with large-scale sending through an Email Service Provider (ESP).

The core of the problem appears to stem from various factors, including reported blocks of Microsoft's IPs at RIPE, an internet registry. This ripple effect can lead to a breakdown in the automated processes that govern SNDS access, leaving senders in a difficult position. We'll dive into what's happening and explore potential avenues for resolution.

Understanding Microsoft SNDS and its authorization mechanics

SNDS is designed to provide insight into your sending reputation with Microsoft services. Access is granted automatically based on your IP addresses or ranges. When you request access, the system uses reverse DNS (rDNS) and WHOIS data to determine ownership and authorize specific email addresses, typically postmaster@domain.com and abuse@domain.com, to receive verification emails. This automated process relies heavily on accurate and accessible DNS information.

Problems arise when this automated system encounters discrepancies or blockages. For example, if the reverse DNS records for your sending IPs aren't consistently pointing to your domain or a subdomain, SNDS might not correctly identify the appropriate addresses for authorization. The SNDS FAQ explicitly states that manual requests for access cannot be processed, emphasizing the reliance on these automatic checks.

For senders using an Email Service Provider (ESP), the situation is often more complex. ESPs typically own the IP addresses from which your emails are sent. This means that SNDS access for those IPs is usually managed by the ESP themselves, or they provide a specific procedure for clients to gain delegated access. When issues arise, it can complicate troubleshooting because the sender's domain might not directly align with the IP owner's verified email addresses.

Current challenges with SNDS access requests

Recent reports highlight a significant hurdle: Microsoft's IPs have reportedly been blocked at RIPE, the Regional Internet Registry for Europe, the Middle East, and Central Asia. This block disrupts the normal communication channels that SNDS uses for verification. If

Microsoft cannot properly query rDNS or WHOIS information due to these blockages, the SNDS portal may fail to present the necessary postmaster or abuse email addresses in its dropdown list for access requests.

This situation is particularly challenging for Marketing Cloud users. When you're trying to gain SNDS access for dedicated IPs owned by

Salesforce, the SNDS portal's inability to show valid abuse@exacttarget.com or similar addresses creates a dead end. Even if Salesforce has correctly configured SNDS for their IP ranges, the underlying RIPE block prevents the Microsoft portal from displaying these options, trapping users in a frustrating loop.

Direct IP owner

Direct control: You manage the rDNS and WHOIS records, allowing Microsoft's automated system to find your verification addresses.
Troubleshooting: Easier to check and adjust your own DNS configurations if verification emails are delayed or not received, as discussed in our article about SNDS authorization emails.

ESP managed IP (e.g., Salesforce Marketing Cloud)

Delegated control: The ESP manages the IP infrastructure and associated DNS records. Access typically requires coordinating with their support.
Dependency: Your ability to access SNDS is tied to the ESP's procedures and their relationship with Microsoft, making troubleshooting more complex.

This issue points to a broader concern about the reliability of SNDS data and access, which can lead to inconsistent email deliverability. For more insights on this, you might find our article on SNDS data reliability helpful.

Troubleshooting and workarounds

When facing these SNDS access issues, especially for IPs managed by an ESP, your first step should be to engage your ESP's support team. They are often best equipped to address problems specific to their infrastructure and their established relationship with

Microsoft. They might have alternative methods for monitoring deliverability or be able to apply internal workarounds.

In situations where the SNDS portal isn't displaying necessary information, it’s crucial to document the exact error messages and any missing options. Providing this detailed information to your ESP's support team can help them escalate the issue with Microsoft more effectively. Our guide on common SNDS issues provides further context on typical problems.

Key steps when SNDS access fails

Verify IP ownership: Confirm that the IPs you are trying to register are indeed associated with your domain or your ESP's designated ranges.
Check rDNS: Ensure your rDNS records are correctly configured and resolving, even if the primary issue is with Microsoft's internal systems.
Contact ESP support: If using an ESP, open a support case with them to investigate the SNDS access blockage. Salesforce, for example, has its own procedures.
Monitor broader issues: Stay informed about any widespread outages or known issues affecting Microsoft's email infrastructure.

Beyond SNDS, implementing and monitoring DMARC is vital for understanding your email ecosystem. A robust DMARC policy with reporting gives you visibility into email authentication results across all receivers, including Microsoft, even if SNDS access is temporarily hindered. Suped offers the most generous free plan for DMARC reporting and monitoring, providing crucial insights into your email deliverability and helping you identify potential issues proactively.

Views from the trenches

Best practices

Maintain accurate rDNS records for your sending IPs, aligning them with your domain ownership.

Always have a dedicated contact within your ESP for deliverability issues and SNDS access.

Leverage DMARC reporting tools like Suped for comprehensive deliverability insights, complementing SNDS data.

Regularly check for official announcements from Microsoft or your ESP regarding platform status.

When encountering issues, gather screenshots and detailed error messages to expedite support.

Common pitfalls

Assuming SNDS data is always real-time and perfectly accurate for all Microsoft services.

Attempting to gain SNDS access for ESP-owned IPs without following the ESP's specific procedure.

Overlooking broader internet infrastructure issues, such as RIPE blocks, affecting SNDS functionality.

Not having alternative monitoring strategies in place when SNDS data or access is unavailable.

Relying solely on SNDS without also monitoring DMARC reports for a complete picture.

Expert tips

If Microsoft's SNDS portal isn't showing the correct verification email addresses, it's often an external issue, such as a RIPE block affecting their ability to query DNS.

For ESP-managed IPs, the ESP should already have SNDS access configured. Attempting to set it up yourself might inadvertently remove their access.

Sometimes trying to access or verify an IP after midnight RIPE server time can offer a brief window before renewed blockages occur.

Microsoft support might acknowledge issues with their SNDS portal directly, so opening a ticket is worthwhile.

Always consult your ESP first regarding SNDS access for their shared or dedicated IPs, as they control the underlying infrastructure.

Expert view

Expert from Email Geeks says Microsoft has experienced issues with their IPs being blocked at RIPE, which is causing problems for SNDS access requests.

2025-09-05 - Email Geeks

Marketer view

Marketer from Email Geeks says that when using an ESP like Salesforce Marketing Cloud, the SNDS access procedure typically requires selecting the ESP's postmaster or abuse email, but this option may be missing due to the underlying RIPE block.

2025-09-05 - Email Geeks

Navigating SNDS complexities

The recent difficulties with Microsoft SNDS access requests highlight the intricate and sometimes fragile nature of email deliverability tools. While SNDS provides valuable data for Microsoft's ecosystem, its reliance on external factors like RIPE registry integrity means that disruptions can occur.

For senders, especially those utilizing ESPs like Salesforce Marketing Cloud, the key takeaway is the need for persistent communication with your provider and a clear understanding of the access procedures for shared or dedicated IPs. While waiting for Microsoft to resolve internal issues, proactive monitoring and a multi-faceted approach to deliverability remain essential.

Tools like Suped's DMARC monitoring offer a crucial layer of visibility, providing comprehensive reports that can help you identify authentication failures and deliverability challenges across all mailbox providers. This provides a safety net when specific tools like SNDS face temporary setbacks.