← sources

13 Microsoft outbound IPs have no PTR record

source: reddit (reddit:sysadmin)published 2026-10-28 19:03ingested 2026-10-29 02:41

retained text

I analyzed 11,846 sending IPs from 494 clients’ DMARC reports against the new Spamhaus Sender Guidelines and found out that 13 Microsoft IPs fail them. In November, Spamhaus is rolling out a requirement that every sending IP must have a valid HELO, a PTR record, and a matching A record.

9 IPv4 and 4 IPv6 inside Microsoft published sending ranges (40.92.0.0/15 and 2a01:111:f403:c000::/51 in spf.protection.outlook.com) have no PTR record at all. Microsoft own DNS servers return NXDOMAIN for these:

    40.93.1.5
    40.93.1.7
    40.93.1.15
    40.93.18.1
    40.93.18.4
    40.93.19.1
    40.93.20.26
    40.93.64.30
    40.93.65.15
    2a01:111:f403:c000::1
    2a01:111:f403:c105::3
    2a01:111:f403:c202::5
    2a01:111:f403:d901::

In my data, those IPs passed 2,389 emails for 133 clients. The volume is tiny just 0.14% of the 1.75 million emails our clients sent through Microsoft in 30 days.  
  
One more IP (2a01:111:f403:c206::1) got a PTR between our two checks, so it seems like Microsoft is fixing them.  
  
M365 users can’t fix this themselves, because only Microsoft can set PTR records for its IPs. If these aren’t fixed before Spamhaus enforcement, the IPs could get listed, and the businesses sending through them can’t do anything about it.  
  
Has anyone seen M365 outbound IPs without PTR or raised this with Microsoft?

document fetched 2026-10-29 00:39 · canonical https://reddit.com/r/sysadmin/comments/1xhx9iv/13_microsoft_outbound_ips_have_no_ptr_record