Mail domain report: jamf.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:71.13.172.133 ip4:67.225.195.119 ip4:52.38.191.241 ip4:198.21.2.94 ip4:167.89.80.72 ip4:198.2.187.217 ip4:159.183.197.119 ip4:167.89.75.111 ip4:167.89.84.155 include:spf.protection.outlook.com include:mktomail.com include:_spf.salesforce.com include:spf.mandrillapp.com include:spf_c.oraclecloud.com include:amazonses.com include:mail.intercom.io ~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

warn

p=reject (_dmarc.jamf.com)

Found

Record: v=DMARC1; p=reject; rua=mailto:njg23lzil6@rua.powerdmarc.com; ruf=mailto:njg23lzil6@ruf.powerdmarc.com; sp=none;
Found at: _dmarc.jamf.com
External report address: mailto:njg23lzil6@rua.powerdmarc.com (authorized)
External report address: mailto:njg23lzil6@ruf.powerdmarc.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	none	Subdomain policy
rua	mailto:njg23lzil6@rua.powerdmarc.com	Aggregate report addresses
ruf	mailto:njg23lzil6@ruf.powerdmarc.com	Failure 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:njg23lzil6@rua.powerdmarc.com
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors: selector1, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: selector1, s1, s2 #7

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

1024-bit DKIM key

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

Signed, DS published at parent

Found

DNSKEY records: Yes (3)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 37768, 11226, 37044
Signatures valid until: 22 October 2026, 18:00 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
!

Signatures expire in 9h0m0s

DNSKEY signatures expire at 2026-10-22T18:00:00Z (in 9h0m0s). Check that re-signing works.

#21

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	jamf-com.mail.protection.outlook.com	A 52.101.40.56 A 52.101.9.93 A 52.101.41.26 A 52.101.50.4 AAAA 2a01:111:f403:f804::2 AAAA 2a01:111:f403:f801:: AAAA 2a01:111:f403:f90a:: AAAA 2a01:111:f403:c902::7	mail-cy7pr05cu00100.inbound.protection.outlook.com ✓ mail-blapr04cu00105.inbound.protection.outlook.com ✓ mail-sj0pr03cu01702.inbound.protection.outlook.com ✓ mail-co1pr03cu00404.inbound.protection.outlook.com ✓ mail-co1pr05cu00402.inbound.protection.outlook.com ✓ mail-byapr05cu00700.inbound.protection.outlook.com ✓ mail-bn6pr02cu00300.inbound.protection.outlook.com ✓ mail-sj0pr02cu00107.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
jamf-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