SPFStrict
No server may send as this domain (-all).
- -all
- Everyone else: refused
0 of the 10 allowed DNS lookups used. Full SPF check
8: a1-67.akam.net, a11-67.akam.net, a12-67.akam.net, a18-67.akam.net, a22-67.akam.net, a28-67.akam.net, a4-67.akam.net and a6-67.akam.net. They are run by Akamai Edge 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.
All 8 nameservers are run by Akamai Edge DNS.
;; opcode: QUERY, status: NOERROR, id: 57554 ;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;akam.net. IN NS ;; ANSWER SECTION: akam.net. 90000 IN NS a22-67.akam.net. akam.net. 90000 IN NS a6-67.akam.net. akam.net. 90000 IN NS a18-67.akam.net. akam.net. 90000 IN NS a28-67.akam.net. akam.net. 90000 IN NS a4-67.akam.net. akam.net. 90000 IN NS a12-67.akam.net. akam.net. 90000 IN NS a11-67.akam.net. akam.net. 90000 IN NS a1-67.akam.net.
-allFailEvery other server. Receivers should reject their mail.;; opcode: QUERY, status: NOERROR, id: 19887 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;akam.net. IN TXT ;; ANSWER SECTION: akam.net. 90000 IN TXT "This" "is" "not" "the" "nameserver" "you" "are" "looking" "for." akam.net. 90000 IN TXT "v=spf1 -all"
;; opcode: QUERY, status: NOERROR, id: 14173 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version 0; flags:; udp: 1232 ;; QUESTION SECTION: ;akam.net. IN SOA ;; ANSWER SECTION: akam.net. 90000 IN SOA internal.akam.net. hostmaster.akamai.com. 1712081400 90000 90000 90000 180
Possibly. There is no DMARC policy, so each receiver decides on its own what to do with mail that fails SPF.
No server may send as this domain (-all).
0 of the 10 allowed DNS lookups used. Full SPF check
No DMARC record. Receivers decide on their own what to do with mail that fails SPF and DKIM, and the domain gets no reports. Start with v=DMARC1; p=none; rua=mailto:you@your-domain.
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.