threatpost.com

Checked 22 October 2026, 11:04 UTC · via 8.8.8.8

✗Problems found

14 passed 3 warnings 4 failed 3 info

SPF

fail

SPF record published

Found

Record: v=spf1 include:spf.protection.outlook.com -all,3600
DNS lookups: 1 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 1 of 10 DNS lookups #2

SPF record needs 1 DNS lookups (limit is 10).
✗

No 'all' mechanism

SPF record doesn't have an 'all' mechanism. Add -all or ~all at the end of your SPF record.

#3
✓ Record published #6

SPF record exists for this domain.
✓ Single record #16

Exactly one SPF record is published.
✗

Syntax errors

Receivers reject the whole SPF record (permerror) because of: unknown mechanism "-all,3600".

#25
✓ No void lookups #26

All include/redirect targets exist.
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

No DMARC record found

Checks

✗

No DMARC record

No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.

#5

DKIM

fail

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NXDOMAIN

Checks

✗

No DKIM keys published

_domainkey.threatpost.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7

DNSSEC

warn

Not signed

Found

DNSKEY records: No (0)
DS at parent: No

Checks

!

Not enabled

DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	threatpost-com.mail.protection.outlook.com	A 52.101.60.65 A 52.101.194.167 A 52.101.9.87 A 52.101.41.125 AAAA 2a01:111:f403:f913::1 AAAA 2a01:111:f403:c902::1 AAAA 2a01:111:f403:f907:: AAAA 2a01:111:f403:f909::4	mail-bn3pr02cu00101.inbound.protection.outlook.com ✓ mail-ch0pr02cu00107.inbound.protection.outlook.com ✓ mail-bl2pr02cu00507.inbound.protection.outlook.com ✓ mail-byapr05cu00605.inbound.protection.outlook.com ✓ mail-cy1pr02cu00101.inbound.protection.outlook.com ✓ mail-sj2pr05cu00401.inbound.protection.outlook.com ✓ mail-dm2pr02cu00100.inbound.protection.outlook.com ✓ mail-bn0pr03cu00304.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 MX records, which is within the recommended range (1-5).
✓ No localhost targets #14

No MX records pointing to localhost found.
✓ No private IP addresses #15

No MX records resolving to private IP addresses found.
✓ No CNAME targets #22

No MX records point to a CNAME.
✓ Reverse DNS confirmed #30

All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
threatpost-com.mail.protection.outlook.com	none	-

Checks

!

Not configured

MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32
i

Not configured

TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.

#35
i

Not used

No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.

#36

BIMI

info

No BIMI record

Checks

i

Not configured

BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.

#38