Summary
ESPs deny direct SNDS access due to a confluence of factors revolving around control, security, potential misuse, and overall deliverability management. Key reasons include the ESP's ownership of the IPs, the inability to revoke access once granted, the risk of customers misinterpreting complex SNDS data leading to harmful actions, the potential exposure of other senders' data due to security vulnerabilities, and the desire to manage the narrative around deliverability. Furthermore, ESPs aim to protect their shared IP pool reputation and shield themselves from legal liabilities arising from customer misuse or violations of terms. Alternatives like Google Postmaster Tools are sometimes promoted for a more holistic view, and aggregated, user-friendly data presentations are preferred to raw SNDS data.
Key findings
- IP Ownership and Control: ESPs own the IPs and need to manage access and data related to them.
- Irrevocable Access: Once SNDS access is granted, it cannot be easily revoked.
- Misinterpretation Risks: Complex SNDS data can be misinterpreted, leading to incorrect actions and strained relationships.
- Data Security and Privacy: Granting direct access increases the risk of data leaks and security vulnerabilities, potentially exposing other senders' data.
- Reputation Management: ESPs need to protect the reputation of their shared IP pools, as unmonitored activity can negatively impact all senders.
- Legal Liability: ESPs want to avoid legal liabilities related to customer misuse or TOS violations.
- Alternative Tools and Data Presentation: ESPs may offer alternative tools (e.g., Google Postmaster Tools) and prefer to present data in an aggregated, user-friendly format.
Key considerations
- ESP Data Access Policies: Understand the specific SNDS access policies of your ESP.
- Data Interpretation Skills: Develop strong data interpretation skills to avoid making incorrect conclusions based on SNDS data.
- Security Measures: Implement robust security measures to prevent compromised accounts and data leaks.
- Deliverability Best Practices: Follow deliverability best practices to minimize negative impacts on shared IP pools.
- Legal Compliance: Ensure compliance with Microsoft's terms of service and all applicable legal regulations regarding SNDS data usage.
- Alternative Data Sources: Consider utilizing alternative data sources like Google Postmaster Tools for a more holistic view of sender reputation.
- Internal Monitoring: Maintain diligent internal monitoring practices to rapidly address any potential deliverability issues.
What email marketers say
9 marketer opinions
ESPs often deny direct SNDS (Smart Network Data Services) access to customers for several key reasons related to data security, potential misinterpretation, and control over their IP reputation. Concerns include the inability to revoke access, the risk of customers misinterpreting complex SNDS data leading to incorrect actions, the potential for data misuse or leakage affecting other senders, security vulnerabilities from compromised accounts, and the desire to manage the narrative around deliverability issues. By acting as intermediaries and providing summarized reports, ESPs aim to protect their infrastructure, maintain the integrity of their data, and offer guidance to ensure customers understand and correctly respond to deliverability insights.
Key opinions
- IP Ownership: ESPs own the IPs and want to control access to data about them.
- Revocation Issues: Once access is granted, it's difficult to revoke, leading to potential data exposure for former customers.
- Data Misinterpretation: Complex SNDS data can be misinterpreted, leading to incorrect actions and support escalations.
- Data Leakage: Granting direct access increases the risk of data leaks affecting other senders.
- Security Vulnerabilities: Compromised customer accounts can expose sensitive data about other senders.
- Control of Narrative: ESPs prefer to manage SNDS data internally to control the narrative and provide guidance.
- Security Improvements: Denying access allows better security implementations.
Key considerations
- Data Accuracy: Ensure any deliverability data provided by the ESP is accurate and comprehensive.
- Guidance and Support: Seek guidance from the ESP on interpreting deliverability data and addressing any issues.
- Alternative Tools: Explore alternative tools like Google Postmaster Tools for additional insights.
- Security Practices: Understand the ESP's security practices and data protection policies.
- Risk Assessment: Consider the potential risks and benefits of direct SNDS access vs. managed reporting.
Marketer view
Email marketer from EmailVendorSelection.com responds that when ESPs deny access, it's often due to concerns about data misuse or misinterpretation. Raw SNDS data can be complex and might lead users to draw incorrect conclusions about their sending reputation, potentially causing unnecessary changes to their email program.
25 Jul 2023 - EmailVendorSelection.com
Marketer view
Marketer from Email Geeks shares that it's not uncommon for an ESP to deny direct SNDS access to customers, as the ESP owns the IPs. He is not acutely aware of any security concerns that would be presented by a customer accessing SNDS, but that doesn't mean none exist.
10 May 2024 - Email Geeks
What the experts say
2 expert opinions
ESPs deny direct access to SNDS (Smart Network Data Services) primarily to safeguard the reputation of their shared IP pools and to mitigate potential liability. Unmonitored customer activities could negatively impact other senders using the same IPs, leading to widespread deliverability issues. Furthermore, ESPs risk being held responsible if a customer misuses SNDS data or violates Microsoft's terms of service.
Key opinions
- IP Reputation Protection: ESPs aim to protect the overall reputation of their shared IP pools.
- Risk of Negative Impact: Unmonitored customer activity can negatively impact other senders.
- Liability Concerns: ESPs could be held liable for customer misuse of SNDS data or violations of terms of service.
Key considerations
- IP Pool Impact: Understand how your email sending practices can affect the reputation of shared IP pools.
- Terms of Service: Adhere to the terms of service of Microsoft and the ESP regarding SNDS data usage.
- Monitoring: Consider the importance of closely monitoring your sending practices to prevent negative impacts on deliverability.
Expert view
Expert from Spam Resource explains that ESPs might deny direct SNDS access to protect the overall reputation of their shared IP pools. Unmonitored customer activity could negatively impact other senders on the same IP, leading to deliverability issues for everyone.
25 Feb 2025 - Spam Resource
Expert view
Expert from Word to the Wise responds that ESPs might deny direct SNDS access due to liability concerns. If a customer misuses SNDS data or engages in activities that violate Microsoft's terms of service, the ESP could be held responsible.
30 Aug 2022 - Word to the Wise
What the documentation says
7 technical articles
ESPs deny direct SNDS (Smart Network Data Services) access for multiple reasons, including the potential exposure of data from other senders sharing the same IP pool, which raises privacy concerns and creates competitive disadvantages. Providing direct access introduces security vulnerabilities, as compromised customer accounts could expose sensitive data. Some ESPs prefer to aggregate SNDS data with other metrics, presenting it in a user-friendly format that focuses on actionable recommendations. They also aim to protect themselves from liabilities associated with customers misusing the data. Additionally, ESPs may encourage the use of alternative tools like Google Postmaster Tools for a more comprehensive view of sender reputation.
Key findings
- Data Exposure: Direct access can expose data of other senders on the same IP pool.
- Privacy Concerns: Sharing data can create privacy issues and competitive disadvantages.
- Security Vulnerabilities: Compromised accounts can expose sensitive data of others.
- Data Aggregation: ESPs prefer to aggregate SNDS with other metrics for a better user experience.
- Liability Protection: Denying access protects ESPs from liabilities related to data misuse.
- Alternative Tools: Alternatives like Google Postmaster Tools provide broader insights.
Key considerations
- Privacy Implications: Understand the privacy implications of accessing shared IP data.
- Security Measures: Assess the ESP's security measures for protecting sensitive data.
- Data Presentation: Evaluate how the ESP presents deliverability data and its actionable insights.
- Liability Risks: Consider the potential liabilities related to using SNDS data.
- Holistic View: Seek a holistic view of sender reputation using multiple tools.
Technical article
Documentation from Amazon states that they do not want to be responsible for customers using information they shouldn't be, therefore they deny SNDS access to protect themselves from liabilities.
21 Nov 2024 - Amazon
Technical article
Documentation from Microsoft explains that SNDS (Smart Network Data Services) provides data regarding your IP address's reputation with Microsoft services, including spam complaint rates and traffic volume. Access is typically granted to IP owners to help them monitor and improve their sending practices.
15 Mar 2023 - Microsoft
Are there any tools available to report on Verizon's new data feeds?
How accurate is Microsoft SNDS data for deliverability monitoring?
How accurate is SNDS and Google Postmaster Tools reputation data?
How can I gain access to Google Postmaster Tools when my ESP controls the subdomain?
How do I grant someone access to my SNDS account?
How should different bounce types be classified and handled by ESPs?
