Mail domain report: splunk.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:104.143.85.100 ip4:104.193.137.209 ip4:104.193.137.4 ip4:104.193.137.41 ip4:192.41.71.17 ip4:199.119.121.165 ip4:204.107.141.23 ip4:204.107.141.240 ip4:216.24.147.140 ip4:68.232.128.201 ip4:68.232.147.33 ip4:68.232.149.37 ip4:97.107.118.214 ip4:50.57.196.251 ip4:162.242.190.82 ip4:72.3.137.171 ip4:92.52.102.162 ip4:63.236.27.141 ip4:67.202.198.229 ip4:63.241.4.85 ip4:67.202.198.237 ip4:5.61.117.0/24 ip4:174.143.181.180 include:sendgrid.net include:mktomail.com include:_spf.salesforce.com include:amazonses.com include:us.khoros-mail.com include:eu.khoros-mail.com include:_spf.qualtrics.com include:_netblocks.xactlycorp.com ~all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 10 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

pass

p=reject (_dmarc.splunk.com)

Found

Record: v=DMARC1; p=reject; sp=reject; rua=mailto:ssg-collab-valimail@splunk.com
Found at: _dmarc.splunk.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
rua	mailto:ssg-collab-valimail@splunk.com	Aggregate report addresses

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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:ssg-collab-valimail@splunk.com
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: s1, s2

Found

Selectors: s1, s2
_domainkey: NOERROR

Selector	Key	Flags
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: s1, s2 #7

DKIM keys found for this domain with selectors: s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: s2 (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

pass

3 mail servers

Found

Priority	Host	Records	Reverse DNS
10	alln-mx-01.cisco.com	A 173.37.147.230 AAAA 2001:420:1201:6::ad25:93e6	alln-mx-01.cisco.com ✓ alln-mx-01.cisco.com ✓
20	rcdn-mx-01.cisco.com	A 72.163.7.166 AAAA 2001:420:1101:7::48a3:166	rcdn-mx-01.cisco.com ✓ rcdn-mx-01.cisco.com ✓
30	aer-mx-01.cisco.com	A 173.38.212.150 AAAA 2001:420:4621::ad26:d496	aer-mx-01.cisco.com ✓ aer-mx-01.cisco.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.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
✓ 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.
✓ No CNAME targets #22

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

All 6 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
alln-mx-01.cisco.com	none	-
rcdn-mx-01.cisco.com	none	-
aer-mx-01.cisco.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