Mail domain report: spirit.com

SPF

pass

SPF record published

Found

Record: v=spf1 a mx ip4:38.103.84.0/24 ip4:40.85.148.145 ip4:199.59.200.201 ip4:54.240.57.251 ip4:54.240.31.215 ip4:208.86.168.7 ip4:64.28.86.55 include:spf.protection.outlook.com include:mail.zendesk.com include:spf.qb-feedback.com include:mktomail.com a:c.spf.service-now.com ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

Found

Record: v=DMARC1; p=quarantine; rua=mailto:6bc74b83-9b5e-4516-9bb0-0e23dcdd757e@us1.smtp.az.brand.darktrace.com;
Found at: _dmarc.spirit.com
External report address: mailto:6bc74b83-9b5e-4516-9bb0-0e23dcdd757e@us1.smtp.az.brand.darktrace.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:6bc74b83-9b5e-4516-9bb0-0e23dcdd757e@us1.smtp.az.brand.darktrace.com	Aggregate report addresses

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:6bc74b83-9b5e-4516-9bb0-0e23dcdd757e@us1.smtp.az.brand.darktrace.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

pass

Selectors: selector1, selector2, s1

Found

Selectors: selector1, selector2, s1
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2, s1 #7

DKIM keys found for this domain with selectors: selector1, selector2, s1
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits; s1: RSA 2048 bits.
✓ 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	spirit.com.1.arsmtp.com	A 8.31.233.174	server238.appriver.com ✓
20	spirit.com.2.arsmtp.com	A 8.19.118.174	server239.appriver.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: spirit.com.1.arsmtp.com, spirit.com.2.arsmtp.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 2 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
spirit.com.1.arsmtp.com	none	-
spirit.com.2.arsmtp.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