SPFStrict
Only the listed servers may send (-all). Mail from any other server fails SPF.
- include:spf.protection.outlook.com
- Microsoft 365
- -all
- Everyone else: refused
1 of the 10 allowed DNS lookups used. Full SPF check
4: ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org and ns4-35.azure-dns.info. They are run by Azure DNS.
Resolvers keep each answer for the time in its TTL and ask again only after it runs out, so right after a change some of them still hold the old value. Public resolvers such as Cloudflare and Google answer from that cache. Choose "Its own nameservers" above to ask the domain's authoritative nameservers, which always return the current value.
To see whether a change has reached every nameserver, open the trace.
Mostly not. Receivers can tell real mail from forged mail, and forged mail lands in spam. The policy stops short of refusing it.
Only the listed servers may send (-all). Mail from any other server fails SPF.
1 of the 10 allowed DNS lookups used. Full SPF check
Mail that fails the checks goes to spam (sp=quarantine). Inherited from outlook.com.
Found at _dmarc.outlook.com. Full DMARC check
No key under 38 common selectors. That does not mean there is none: a domain does not list its selectors. Find yours in the DKIM-Signature header of a sent message (the s= value) and check it below.
google, 20230601, 20210112, 20161025, selector1, selector2, k1, k2, k3, mandrill, s1, s2, mx, smtp, mailo, krs, pm, fm1, fm2, fm3, protonmail, protonmail2, protonmail3, zoho, zmail, sig1, cm, mailjet, ctct1, ctct2, default, dkim, mail, selector, key1, key2, s1024, s2048
As seen by Cloudflare.
All 4 nameservers are run by Azure DNS.
;; opcode: QUERY, status: NOERROR, id: 22590 ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;protection.outlook.com. IN NS ;; ANSWER SECTION: protection.outlook.com. 172800 IN NS ns1-35.azure-dns.com. protection.outlook.com. 172800 IN NS ns2-35.azure-dns.net. protection.outlook.com. 172800 IN NS ns3-35.azure-dns.org. protection.outlook.com. 172800 IN NS ns4-35.azure-dns.info.
include:spf.protection.outlook.comPassSenders that pass the SPF record of spf.protection.outlook.com View record-allFailEvery other server. Receivers should reject their mail.;; opcode: QUERY, status: NOERROR, id: 61274 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;protection.outlook.com. IN TXT ;; ANSWER SECTION: protection.outlook.com. 290 IN TXT "v=spf1 include:spf.protection.outlook.com -all"
;; opcode: QUERY, status: NOERROR, id: 28621 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;protection.outlook.com. IN SOA ;; ANSWER SECTION: protection.outlook.com. 300 IN SOA ns1-35.azure-dns.com. hostmaster.o365filtering.com. 2024081305 10800 3600 604800 120