Mail domain report: marketo.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:96.43.144.64/31 ip4:96.43.148.64/31 ip4:199.15.212.0/22 ip4:94.236.119.0/26 ip4:185.28.196.0/22 ip4:192.28.128.0/18 ip4:103.237.104.0/22 ip4:52.38.191.241 ip4:52.207.191.216 ip4:52.34.3.26 ip4:35.166.89.76 ip4:35.164.204.88 ip4:35.164.166.33 ip4:204.93.64.116 ip4:204.93.64.117 ip4:192.250.208.112 ip4:192.250.208.113 ip4:130.248.172.0/24 ip4:130.248.173.0/24 ip4:130.248.131.152 include:_spf.salesforce.com include:spf.protection.outlook.com include:_netblocks.xactlycorp.com include:stspg-customer.com include:sendgrid.net include:mktomail.com ~all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 8 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.marketo.com)

Found

Record: v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:adobe@rua.agari.com,mailto:dmarc_agg@dmarc.250ok.net; ruf=mailto:adobe@ruf.agari.com,mailto:dmarc_fr@dmarc.250ok.net; fo=1; rf=afrf
Found at: _dmarc.marketo.com
External report address: mailto:adobe@rua.agari.com (authorized)
External report address: mailto:dmarc_agg@dmarc.250ok.net (authorized)
External report address: mailto:adobe@ruf.agari.com (authorized)
External report address: mailto:dmarc_fr@dmarc.250ok.net (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:adobe@rua.agari.com,mailto:dmarc_agg@dmarc.250ok.net	Aggregate report addresses
ruf	mailto:adobe@ruf.agari.com,mailto:dmarc_fr@dmarc.250ok.net	Failure report addresses
fo	1	Failure reporting options
rf	afrf	Failure report format

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:adobe@rua.agari.com, mailto:dmarc_agg@dmarc.250ok.net
✓ 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

warn

Selectors: mx

Found

Selectors: mx
_domainkey: NOERROR

Selector	Key	Flags
mx	RSA 1024 bits

Checks

✓ Keys found: mx #7

DKIM keys found for this domain with selectors: mx
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mx (1024 bits). Rotate to a 2048-bit key.

#23
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	marketo-com.mail.protection.outlook.com	A 52.101.194.158 A 52.101.41.24 A 52.101.9.24 A 52.101.194.152	mail-ch3pr04cu00106.inbound.protection.outlook.com ✓ mail-sj0pr03cu01600.inbound.protection.outlook.com ✓ mail-bl2pr02cu00400.inbound.protection.outlook.com ✓ mail-ch4pr04cu00300.inbound.protection.outlook.com ✓
100	adobe.mail.protection.outlook.com	A 52.101.60.191 A 52.101.9.11 A 52.101.194.4 A 52.101.8.71	mail-bn0pr05cu00107.inbound.protection.outlook.com ✓ mail-bl1pr02cu00103.inbound.protection.outlook.com ✓ mail-ch4pr04cu00104.inbound.protection.outlook.com ✓ mail-dm2pr03cu00107.inbound.protection.outlook.com ✓

Checks

✓ 2 MX records #9

Found 2 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: marketo-com.mail.protection.outlook.com, adobe.mail.protection.outlook.com

#11
✓ Redundant MX hosts #12

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

Found 2 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 2 MX hosts

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
marketo-com.mail.protection.outlook.com	none	-
adobe.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