Mail domain report: origin.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:spf.protection.outlook.com ~all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 2 DNS lookups (limit is 10).
✓ Ends with ~all #3

SPF record properly uses ~all to restrict unauthorized senders.
✓ Record published #6

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

Exactly one SPF record is published.
✓ Valid syntax #25

All SPF mechanisms and modifiers are valid.
✓ No void lookups #26

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

All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.origin.com)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc_agg@vali.email,mailto:it-messaging-dmarc-alerts@ea.com; ruf=mailto:it-messaging-dmarc-alerts@ea.com; fo=1
Found at: _dmarc.origin.com
External report address: mailto:dmarc_agg@vali.email (authorized)
External report address: mailto:it-messaging-dmarc-alerts@ea.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc_agg@vali.email,mailto:it-messaging-dmarc-alerts@ea.com	Aggregate report addresses
ruf	mailto:it-messaging-dmarc-alerts@ea.com	Failure report addresses
fo	1	Failure reporting options

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Applies to 100% of mail #18

DMARC policy applies to all failing mail.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc_agg@vali.email, mailto:it-messaging-dmarc-alerts@ea.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

fail

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NXDOMAIN

Checks

✗

No DKIM keys published

_domainkey.origin.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

3 mail servers

Found

Priority	Host	Records	Reverse DNS
0	origin-ea-com.mail.protection.outlook.com	A 52.101.60.182 A 52.101.50.1 A 52.101.42.165 A 52.101.8.38	mail-bn3pr0301cu00206.inbound.protection.outlook.com ✓ mail-co1pr05cu00401.inbound.protection.outlook.com ✓ mail-co2pr03cu00305.inbound.protection.outlook.com ✓ mail-dm3pr04cu00106.inbound.protection.outlook.com ✓
10	origin.com.pri-mx.na0107.smtproutes.com	CNAME mx1.mtaroutes.com A 149.13.75.27 AAAA 2001:978:2:2c::137:100	fe1-r3-in.fra02.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
90	origin.com.bak-mx.na0107.smtpbak.com	CNAME mx2.mtaroutes.com A 149.13.75.27 AAAA 2001:978:2:7::162:100	fe1-r3-in.fra02.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓

Checks

✓ 3 MX records #9

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

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: origin-ea-com.mail.protection.outlook.com

#11
✓ Redundant MX hosts #12

Found 3 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

Found 3 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.
!

Hosts are CNAMEs

MX records must point to a host name with A/AAAA records, not to a CNAME: origin.com.pri-mx.na0107.smtproutes.com -> mx1.mtaroutes.com, origin.com.bak-mx.na0107.smtpbak.com -> mx2.mtaroutes.com

#22
✓ 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 3 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
origin-ea-com.mail.protection.outlook.com	none	-
origin.com.pri-mx.na0107.smtproutes.com	none	-
origin.com.bak-mx.na0107.smtpbak.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