Suped

What format does the SNDS REST API /api/report/status/ip endpoint return?

Published 7 Jul 2026
Updated 7 Nov 2026
13 min read
Summarize with
Headerless CSV response from the Microsoft SNDS /api/report/status/ip endpoint.
Updated on 7 Nov 2026: We clarified SNDS CSV parsing and the access checks needed before treating a 404 as missing data.
The SNDS REST API /api/report/status/ip endpoint has returned headerless plaintext CSV in observed responses, not JSON. Each observed row has four comma-separated fields: a primary IP value, a second IP value, a boolean-like status flag, and a human-readable reason string.
Observed response shape with documentation IP addressestext
203.0.113.10,203.0.113.10,True,Blocked due to user complaints or other evidence of spamming 198.51.100.25,198.51.100.25,True,Blocked due to user complaints or other evidence of spamming
Treat this endpoint as a report export rather than a typical JSON resource. Read a successful response as text first. A 404 can mean that no rows are available, but it can also mean the route, method, automated link, or access context is wrong. Verify those conditions before recording the poll as a healthy empty result.

Observed response format

The important detail is the observed body shape, not the REST-style path. The payload has appeared as plain CSV text without a header row. A JSON parser will fail on valid data, and a CSV parser that requires column names needs names supplied by the client. Log the Content-Type header, but validate the body instead of trusting that header alone.

Position

Observed value

Practical meaning

1
Primary IP value
First IP-shaped field in the SNDS status row.
2
Second IP value
Second IP-shaped field. Preserve it separately until Microsoft documents its name.
3
True or False
Boolean-like status flag. Parse it case-insensitively and interpret it with the reason, rather than assuming True always means blocked.
4
Reason
Free-text status reason, including complaint or spam-evidence wording.
Observed columns in /api/report/status/ip
Do not infer a formal schema
The endpoint has no header row, so these names are operational labels rather than confirmed API contract names. Store both IP fields, the boolean-like value, the reason, and the raw row. Normalize the fields only after comparing multiple responses and checking for format changes. Use a neutral internal name such as statusFlag until the flag meaning is confirmed for each status reason.
Microsoft SNDS IP status report with address, flag, and reason columns.
Microsoft SNDS IP status report with address, flag, and reason columns.

IP Status coverage and refresh timing

Microsoft's SNDS FAQ describes IP Status as abnormal Outlook.com conditions, including blocking or junk-folder placement. The view covers the last 24 hours, is not updated in real time, and has no historical IP Status view.
Treat this endpoint as a status snapshot. Store successful polls to build your own history, and retain the last successful snapshot when a later request fails. A missing row does not prove inbox delivery. Keep the separate IP Data report's traffic metrics and red/yellow/green filter results distinct from these status rows.

How to parse the endpoint safely

Use a defensive flow: inspect the HTTP status, preserve diagnostic details, then parse only a successful, non-empty body. Keeping response classification separate from CSV parsing prevents an empty report, an outdated URL, and malformed CSV from collapsing into the same result.
SNDS API flow for checking HTTP status before parsing CSV rows.
SNDS API flow for checking HTTP status before parsing CSV rows.
Supply a CSV parser through the parseCsv adapter shown below. Configure it for headerless records and preserve each raw record. RFC 4180 describes quoted fields containing commas or line breaks and doubled quotation marks. Splitting on commas or newlines loses that structure.
Parser outline for observed rowsjavascript
async function fetchSndsIpStatus(fetcher, url, token, parseCsv) { // Supply a CSV parser adapter: parseCsv(text) returns // [{ fields: string[], raw: string }], without consuming a header row. // It must handle quoted commas, escaped quotes, embedded newlines, // and CRLF/LF endings, skip only empty records, and reject malformed CSV. const res = await fetcher(url, { headers: { Authorization: "Bearer " + token } }); const contentType = res.headers.get("content-type") || ""; const fetchedAt = new Date().toISOString(); const metadata = { httpStatus: res.status, contentType, fetchedAt }; const body = await res.text(); if (res.status === 404) { return { status: "not_found", rows: [], ...metadata, body }; } if (res.status === 429) { const retryAfter = res.headers.get("retry-after"); throw new Error("SNDS rate limit; retry after " + (retryAfter || "backoff")); } if (!res.ok) { throw new Error("SNDS request failed with " + res.status); } const csv = body.replace(/^\uFEFF/, ""); if (!csv.trim()) { return { status: "empty", rows: [], ...metadata, body }; } if (/^\s*</.test(csv)) { throw new Error("Unexpected HTML or XML response; check sign-in and URL"); } const records = parseCsv(csv); if (!records.length) { throw new Error("Non-empty SNDS body produced no CSV records"); } const rows = records.map(({ fields, raw }, index) => { if (fields.length !== 4) { throw new Error("Unexpected SNDS column count at record " + (index + 1)); } const [ip1, ip2, rawFlag, reason] = fields; const flag = rawFlag.trim().toLowerCase(); if (!ip1.trim() || !ip2.trim()) { throw new Error("Missing SNDS IP field at record " + (index + 1)); } if (flag !== "true" && flag !== "false") { throw new Error("Unexpected SNDS flag at record " + (index + 1)); } return { ip1: ip1.trim(), ip2: ip2.trim(), statusFlag: flag === "true", reason: reason.trim(), rawLine: raw }; }); return { status: "ok", rows, ...metadata, body }; }
  1. Status first: Preserve a 404 as not_found until a separate check confirms that it means no current data.
  2. Text first: Read a successful body as text. Do not send this observed payload to a JSON parser.
  3. Validate rows: Require exactly four parsed fields and a recognized boolean value. Reject missing IP values and unexpected columns instead of silently merging a changed schema into the reason.
  4. Handle CSV changes: Use a CSV parser for quoted commas, escaped quotes, and embedded newlines. Remove a leading UTF-8 byte order mark before parsing, and reject HTML sign-in pages even when the HTTP status is 200.
  5. Keep evidence: Store raw rows, status, Content-Type, and fetch time so a response change can be diagnosed.

How to interpret a 404

A 404 has been observed when the authenticated account has no current status rows, but the status code alone does not prove an empty report. It can also indicate an outdated or expired automated link, a wrong path or method, missing IP access, or an account mismatch. Preserve the body, run a control request for the same IP ranges, and compare the portal's IP Status view before choosing the no-data classification.
Response handling model
A practical classification model for the observed SNDS IP status endpoint.
200
Data
Validate and parse a non-empty CSV body; classify an empty successful body separately.
404
Check
Verify the URL, method and IP access, then compare a control request and the portal IP Status view.
401
Authenticate
Refresh an expired access token once, then require sign-in if authentication still fails.
403
Access
Review permissions, consent and authorized IP ranges before retrying.
429
Backoff
Honor Retry-After when present and reduce the polling rate.
5xx
Retry
Retry with bounded backoff and preserve request metadata for logs.
Under HTTP semantics in RFC 9110, 404 means the server found no current resource or is unwilling to disclose that one exists. The SNDS no-data interpretation is an observed endpoint behavior, so verify it against the portal rather than treating every 404 as an empty report.
Verified empty state
  1. Current link: The request uses the current REST API URL or a valid automated export link for the chosen access method.
  2. Access works: A control request succeeds for the same requested IP ranges and account context.
  3. Portal agrees: The portal IP Status view has no abnormal entries for the same authorized ranges, corroborating the observed no-data response.
  4. Job result: Record a successful poll with zero rows and retain the diagnostic response.
Unresolved failure
  1. Link is stale: The request still uses an automated URL created for the retired SNDS site.
  2. Access fails: The same credential or account fails against a known-good report path.
  3. Path differs: Known-good accounts fail because the URL or HTTP method does not match the current request.
  4. Job result: Raise an operational error and keep the last successful snapshot.

Authentication notes for scheduled polling

Authentication failures and response-format errors often surface during the same integration test. If this endpoint returns 404 while a known-good report path works for the same account and IP ranges, investigate data availability and the exact URL. For 401, check token expiry and refresh once. For 403, check consent and SNDS IP authorization before retrying.
Refresh token scope
For scheduled polling through the Microsoft identity platform's authorization code flow, request offline_access so the token response can include a refresh token. Request the SNDS resource scope required by the integration. The openid and profile scopes concern sign-in identity data and are not substitutes for offline_access. Microsoft documents this requirement for its v2.0 endpoints in its scope documentation. Confirm refresh-token issuance for the actual client and flow; requesting a scope alone does not guarantee unattended access.
Illustrative authorization-code token responsejson
{ "token_type": "Bearer", "scope": "RESOURCE_SCOPE_RETURNED_BY_MICROSOFT", "expires_in": 3599, "access_token": "REDACTED", "refresh_token": "REDACTED" }
Do not make the CSV parser depend on a refresh token being present. Token acquisition belongs in a separate client layer, so refresh failures, HTTP retries, and missing report data remain distinct. Store tokens securely and replace a cached refresh token when the identity platform returns a new one. The scope and expiry above are illustrative, not SNDS client configuration.
  1. Grant type: Use a supported authorization flow, verify refresh-token issuance, and handle a renewed interactive sign-in when required.
  2. Consent scope: Request offline_access with the required resource scope when a refresh token is needed.
  3. Token cache: Store expiry and replacement metadata securely, separate from report results.
  4. Retry logic: Retry 5xx with bounded backoff, honor Retry-After for 429, refresh once for 401, and investigate permissions for 403.

Check SNDS URLs and network access

Microsoft replaced the old SNDS portal, and the June 22, 2026 deadline for retiring legacy automated access URLs has passed. Verify the request URL for the access method you use before diagnosing a 404 as an empty report. The authenticated REST API and generated automated export links are separate access methods; a generated-link problem does not establish that this REST route has no data.
  1. Verify the request URL: For automated exports, check the link and its validity in Automated Data Access. For bearer-token REST calls, verify the current API host and exact route.
  2. Test account access: Confirm that the signed-in Microsoft account still has access to the requested IP ranges, including any required network reattestation.
  3. Run a control request: Compare this status path with another known-good SNDS report path using the same account context.
  4. Separate report changes: Trap-hit counts were removed from the Data Report on July 22, 2026. That change does not define the four fields observed on this IP status endpoint.
Network access expires 10 months after approval or migration. Microsoft's current SNDS announcement warns that the first reattestation reminder contained an inaccurate deadline. Check the expiration shown in Access Control and complete renewal before access expires. A valid access token does not renew network authorization.
Treat the row shape as version-sensitive
Microsoft's public SNDS documentation does not establish field names for this headerless response. Log HTTP status, the response host and path without credentials or query values, Content-Type, body length, and a short redacted sample. Keep bearer tokens and automated-access keys out of logs.

How SNDS status fits with blocklist monitoring

SNDS status data is a Microsoft-specific reputation signal for sending IPs. It does not replace broader blocklist monitoring (blacklist monitoring) or DMARC reporting.
When a row contains True with a complaint or spam-evidence reason, investigate that Microsoft status and check broader blocklist (blacklist) results separately. An IP can be blocked by Microsoft without appearing on a public list. Compare sender activity and authentication results around the first observed status change.
Suped's blocklist checker can check a specific IP that appears in the SNDS feed. Suped's domain health checker can check the sending domain's published email-authentication DNS records. These checks do not establish why Microsoft applied a status.
Blocklist checker
Check your domain or IP against 144 blocklists.
www.spamhaus.org logoSpamhaus0spam.org logo0Spam
Blocklist icon
Abusix
Blocklist icon
Barracuda Networks
www.spamcop.net logoCisco
Blocklist icon
Mailspike
www.nosolicitado.org logoNoSolicitado
Blocklist icon
SURBL
Blocklist icon
UCEPROTECT
uribl.com logoURIBL
Blocklist icon
8086 Consultancy
abuse.ro logoabuse.rowiki.alphanet.ch logoALPHANETanonmails.de logoAnonmailsascams.com logoAscamswww.blockedservers.com logoBLOCKEDSERVERS
Blocklist icon
Brukalai.lt
dnsbl.calivent.com.pe logoCalivent Networks
Blocklist icon
dan.me.uk
Blocklist icon
DrMx
Blocklist icon
DroneBL
rbl.efnetrbl.org logoEFnet
Blocklist icon
Fabel
Blocklist icon
GBUdb
Blocklist icon
ImproWare
Blocklist icon
JIPPG Technologies
Blocklist icon
Junk Email Filter
www.justspam.org logoJustSpamwww.kempt.net logoKempt.net
Blocklist icon
Mail Baby
www.nordspam.com logoNordSpam
Blocklist icon
nsZones
Blocklist icon
Polspam
rv-soft.info logoRV-SOFT Technology
Blocklist icon
Schulte
www.scientificspam.net logoScientific Spam
Blocklist icon
Spam Eating Monkey
psbl.org logoSpamikazewww.spamrats.com logoSpamRATSspfbl.net logoSPFBLsuomispam.net logoSuomispamwww.usenix.org.uk logoSystem 5 Hosting
Blocklist icon
Taughannock Networks
www.team-cymru.com logoTeam Cymru
Blocklist icon
Tornevall Networks
senderscore.org logoValiditywww.blocklist.de logowww.blocklist.de Fail2Ban-Reporting Servicezapbl.net logoZapBL2stepback.dk logo2stepback.dkfaynticrbl.org logoFayntic Servicesorbz.gst-group.co.uk logoORB UK
Blocklist icon
RedHawk
dnsbl.technoirc.org logotechnoirc.orgwww.techtheft.info logoTechTheftwww.spamhaus.org logoSpamhaus0spam.org logo0Spam
Blocklist icon
Abusix
Blocklist icon
Barracuda Networks
www.spamcop.net logoCisco
Blocklist icon
Mailspike
www.nosolicitado.org logoNoSolicitado
Blocklist icon
SURBL
Blocklist icon
UCEPROTECT
uribl.com logoURIBL
Blocklist icon
8086 Consultancy
abuse.ro logoabuse.rowiki.alphanet.ch logoALPHANETanonmails.de logoAnonmailsascams.com logoAscamswww.blockedservers.com logoBLOCKEDSERVERS
Blocklist icon
Brukalai.lt
dnsbl.calivent.com.pe logoCalivent Networks
Blocklist icon
dan.me.uk
Blocklist icon
DrMx
Blocklist icon
DroneBL
rbl.efnetrbl.org logoEFnet
Blocklist icon
Fabel
Blocklist icon
GBUdb
Blocklist icon
ImproWare
Blocklist icon
JIPPG Technologies
Blocklist icon
Junk Email Filter
www.justspam.org logoJustSpamwww.kempt.net logoKempt.net
Blocklist icon
Mail Baby
www.nordspam.com logoNordSpam
Blocklist icon
nsZones
Blocklist icon
Polspam
rv-soft.info logoRV-SOFT Technology
Blocklist icon
Schulte
www.scientificspam.net logoScientific Spam
Blocklist icon
Spam Eating Monkey
psbl.org logoSpamikazewww.spamrats.com logoSpamRATSspfbl.net logoSPFBLsuomispam.net logoSuomispamwww.usenix.org.uk logoSystem 5 Hosting
Blocklist icon
Taughannock Networks
www.team-cymru.com logoTeam Cymru
Blocklist icon
Tornevall Networks
senderscore.org logoValiditywww.blocklist.de logowww.blocklist.de Fail2Ban-Reporting Servicezapbl.net logoZapBL2stepback.dk logo2stepback.dkfaynticrbl.org logoFayntic Servicesorbz.gst-group.co.uk logoORB UK
Blocklist icon
RedHawk
dnsbl.technoirc.org logotechnoirc.orgwww.techtheft.info logoTechTheftwww.spamhaus.org logoSpamhaus0spam.org logo0Spam
Blocklist icon
Abusix
Blocklist icon
Barracuda Networks
www.spamcop.net logoCisco
Blocklist icon
Mailspike
www.nosolicitado.org logoNoSolicitado
Blocklist icon
SURBL
Blocklist icon
UCEPROTECT
uribl.com logoURIBL
Blocklist icon
8086 Consultancy
abuse.ro logoabuse.rowiki.alphanet.ch logoALPHANETanonmails.de logoAnonmailsascams.com logoAscamswww.blockedservers.com logoBLOCKEDSERVERS
Blocklist icon
Brukalai.lt
dnsbl.calivent.com.pe logoCalivent Networks
Blocklist icon
dan.me.uk
Blocklist icon
DrMx
Blocklist icon
DroneBL
rbl.efnetrbl.org logoEFnet
Blocklist icon
Fabel
Blocklist icon
GBUdb
Blocklist icon
ImproWare
Blocklist icon
JIPPG Technologies
Blocklist icon
Junk Email Filter
www.justspam.org logoJustSpamwww.kempt.net logoKempt.net
Blocklist icon
Mail Baby
www.nordspam.com logoNordSpam
Blocklist icon
nsZones
Blocklist icon
Polspam
rv-soft.info logoRV-SOFT Technology
Blocklist icon
Schulte
www.scientificspam.net logoScientific Spam
Blocklist icon
Spam Eating Monkey
psbl.org logoSpamikazewww.spamrats.com logoSpamRATSspfbl.net logoSPFBLsuomispam.net logoSuomispamwww.usenix.org.uk logoSystem 5 Hosting
Blocklist icon
Taughannock Networks
www.team-cymru.com logoTeam Cymru
Blocklist icon
Tornevall Networks
senderscore.org logoValiditywww.blocklist.de logowww.blocklist.de Fail2Ban-Reporting Servicezapbl.net logoZapBL2stepback.dk logo2stepback.dkfaynticrbl.org logoFayntic Servicesorbz.gst-group.co.uk logoORB UK
Blocklist icon
RedHawk
dnsbl.technoirc.org logotechnoirc.orgwww.techtheft.info logoTechTheftwww.spamhaus.org logoSpamhaus0spam.org logo0Spam
Blocklist icon
Abusix
Blocklist icon
Barracuda Networks
www.spamcop.net logoCisco
Blocklist icon
Mailspike
www.nosolicitado.org logoNoSolicitado
Blocklist icon
SURBL
Blocklist icon
UCEPROTECT
uribl.com logoURIBL
Blocklist icon
8086 Consultancy
abuse.ro logoabuse.rowiki.alphanet.ch logoALPHANETanonmails.de logoAnonmailsascams.com logoAscamswww.blockedservers.com logoBLOCKEDSERVERS
Blocklist icon
Brukalai.lt
dnsbl.calivent.com.pe logoCalivent Networks
Blocklist icon
dan.me.uk
Blocklist icon
DrMx
Blocklist icon
DroneBL
rbl.efnetrbl.org logoEFnet
Blocklist icon
Fabel
Blocklist icon
GBUdb
Blocklist icon
ImproWare
Blocklist icon
JIPPG Technologies
Blocklist icon
Junk Email Filter
www.justspam.org logoJustSpamwww.kempt.net logoKempt.net
Blocklist icon
Mail Baby
www.nordspam.com logoNordSpam
Blocklist icon
nsZones
Blocklist icon
Polspam
rv-soft.info logoRV-SOFT Technology
Blocklist icon
Schulte
www.scientificspam.net logoScientific Spam
Blocklist icon
Spam Eating Monkey
psbl.org logoSpamikazewww.spamrats.com logoSpamRATSspfbl.net logoSPFBLsuomispam.net logoSuomispamwww.usenix.org.uk logoSystem 5 Hosting
Blocklist icon
Taughannock Networks
www.team-cymru.com logoTeam Cymru
Blocklist icon
Tornevall Networks
senderscore.org logoValiditywww.blocklist.de logowww.blocklist.de Fail2Ban-Reporting Servicezapbl.net logoZapBL2stepback.dk logo2stepback.dkfaynticrbl.org logoFayntic Servicesorbz.gst-group.co.uk logoORB UK
Blocklist icon
RedHawk
dnsbl.technoirc.org logotechnoirc.orgwww.techtheft.info logoTechTheftwww.spamhaus.org logoSpamhaus0spam.org logo0Spam
Blocklist icon
Abusix
Blocklist icon
Barracuda Networks
www.spamcop.net logoCisco
Blocklist icon
Mailspike
www.nosolicitado.org logoNoSolicitado
Blocklist icon
SURBL
Blocklist icon
UCEPROTECT
uribl.com logoURIBL
Blocklist icon
8086 Consultancy
abuse.ro logoabuse.rowiki.alphanet.ch logoALPHANETanonmails.de logoAnonmailsascams.com logoAscamswww.blockedservers.com logoBLOCKEDSERVERS
Blocklist icon
Brukalai.lt
dnsbl.calivent.com.pe logoCalivent Networks
Blocklist icon
dan.me.uk
Blocklist icon
DrMx
Blocklist icon
DroneBL
rbl.efnetrbl.org logoEFnet
Blocklist icon
Fabel
Blocklist icon
GBUdb
Blocklist icon
ImproWare
Blocklist icon
JIPPG Technologies
Blocklist icon
Junk Email Filter
www.justspam.org logoJustSpamwww.kempt.net logoKempt.net
Blocklist icon
Mail Baby
www.nordspam.com logoNordSpam
Blocklist icon
nsZones
Blocklist icon
Polspam
rv-soft.info logoRV-SOFT Technology
Blocklist icon
Schulte
www.scientificspam.net logoScientific Spam
Blocklist icon
Spam Eating Monkey
psbl.org logoSpamikazewww.spamrats.com logoSpamRATSspfbl.net logoSPFBLsuomispam.net logoSuomispamwww.usenix.org.uk logoSystem 5 Hosting
Blocklist icon
Taughannock Networks
www.team-cymru.com logoTeam Cymru
Blocklist icon
Tornevall Networks
senderscore.org logoValiditywww.blocklist.de logowww.blocklist.de Fail2Ban-Reporting Servicezapbl.net logoZapBL2stepback.dk logo2stepback.dkfaynticrbl.org logoFayntic Servicesorbz.gst-group.co.uk logoORB UK
Blocklist icon
RedHawk
dnsbl.technoirc.org logotechnoirc.orgwww.techtheft.info logoTechTheft
Suped is our DMARC and email authentication platform. Use its blocklist monitoring and DMARC reports to investigate the affected sender, then compare those results with SNDS rows retained by your own polling job.
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Keep the original SNDS row and fetch time in the incident record so the operator can compare timing before changing DNS or sender configuration.

Implementation checklist

Build the integration around observed behavior without assuming that the headerless row has a published schema. Retain enough evidence to detect a changed response.
  1. Poll the endpoint: Use the current REST API URL with a valid bearer token and read the response body as text.
  2. Classify the status: Parse non-empty successful bodies, classify empty bodies separately, verify 404 against access and portal checks, distinguish 401 from 403, honor 429, and retry 5xx.
  3. Validate and parse rows: Require exactly four CSV fields, preserve both IP fields, validate the boolean, and retain the decoded reason and raw record.
  4. Store evidence: Keep the raw row, fetch time, account identifier, HTTP status, Content-Type, and parsed fields.
  5. Alert on change: Trigger alerts for a new abnormal-status row, a changed flag or reason, repeated parse failures, or an unverified 404.
Recommended storage model
Illustrative internal normalized rowjson
{ "source": "snds_status_ip", "fetched_at": "2026-09-07T12:00:00Z", "ip_primary": "203.0.113.10", "ip_secondary": "203.0.113.10", "status_flag": true, "reason": "Blocked due to user complaints or other evidence of spamming", "http_status": 200, "content_type": "RESPONSE_HEADER_VALUE", "raw_line": "203.0.113.10,203.0.113.10,True,Blocked due to user complaints or other evidence of spamming" }
Related notes cover the current Microsoft SNDS URL and common SNDS issues.

Views from the trenches

Best practices
Read each response as text, then use a CSV parser that preserves quoted fields and raw records.
Verify a 404 against account access and the portal before recording a successful empty poll.
Log raw rows and redacted response metadata so format or message changes are easy to trace.
Common pitfalls
Sending this observed payload to a JSON parser causes failures on otherwise valid CSV rows.
Treating every 404 as no data can hide a stale URL, expired network access, or account error.
Requesting offline_access alone does not guarantee refresh tokens for every client and flow.
Expert tips
Keep both IP fields separate until Microsoft publishes names for the response columns.
Validate exactly four CSV fields and a boolean flag so changed rows fail visibly during polling.
Alert on changed rows and parser failures, then compare sender activity before fixes.

Marketer view

Marketer from Email Geeks says the endpoint returned headerless plaintext CSV rows with two IP fields, a boolean value, and a human-readable status reason.
2026-06-24 - Email Geeks

Marketer view

Marketer from Email Geeks says a 404 response can mean the requested SNDS data is absent, especially when the same token works against other report paths.
2026-06-24 - Email Geeks

Frequently asked questions

Observed responses are headerless plaintext CSV rather than JSON. Read the body as text, then use a CSV parser configured without a header row.

The observed row has four positions: a primary IP value, a second IP value, a boolean-like flag, and a reason string. These are operational labels, not confirmed Microsoft API field names.

A 404 can mean that no current status rows exist, but it also warrants checks for an incorrect URL, an expired export link, or lost IP access. Confirm the requested ranges, a control request, and the portal IP Status view before recording no data.

Log the header, but validate the body shape. Reject an HTML sign-in page or changed CSV column count, even when the HTTP status is 200.

Read True with its reason and the portal status before labeling an IP blocked. Alert on a new row or changed flag or reason, and suppress repeated alerts for an unchanged row.

Suped is our DMARC and email authentication platform. Use its DMARC reports and blocklist monitoring alongside the SNDS rows stored by your polling job to investigate a sender status change.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing