Mail domain report: trustwave.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:63.210.234.0/24 ip4:64.194.204.0/24 ip4:38.106.143.0/24 ip4:204.13.200.0/22 ip4:208.90.236.0/22 include:spf.protection.outlook.com include:_spf-a.trustwave.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

warn

p=quarantine (_dmarc.trustwave.com)

Found

Record: v=DMARC1; p=quarantine; sp=quarantine; ri=3600; rua=mailto:bu3v5nic@ag.dmarcian.com; ruf=mailto:bu3v5nic@fr.dmarcian.com;
Found at: _dmarc.trustwave.com
External report address: mailto:bu3v5nic@ag.dmarcian.com (authorized)
External report address: mailto:bu3v5nic@fr.dmarcian.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	quarantine	Subdomain policy
rua	mailto:bu3v5nic@ag.dmarcian.com	Aggregate report addresses
ruf	mailto:bu3v5nic@fr.dmarcian.com	Failure report addresses
ri	3600	Report interval (seconds)

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:bu3v5nic@ag.dmarcian.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

Found

Selectors: selector1, selector2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2 #7

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

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
✓ 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: 10045, 35896, 48877
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 7h0m0s

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

#21

MX

warn

1 mail server

Found

Priority	Host	Records	Reverse DNS
10	mx.us.mailmarshal.cloud	A 20.81.234.0 A 52.165.80.64 AAAA 2602:f8d5:a1:8001:: AAAA 2602:f8d5:a1:1::	mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓ mx.us.mailmarshal.cloud ✓

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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · no TLS-RPT · DANE on 1 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=20241215080000Z;
Policy URL: https://mta-sts.trustwave.com/.well-known/mta-sts.txt
Mode: testing
Allowed MX: *.us.mailmarshal.cloud
Max age: 86400 seconds

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx.us.mailmarshal.cloud	3 1 1 06e7ab1436ce4270…	Yes

Checks

✓ Record published #32

MTA-STS record found with id 20241215080000Z.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
✓ All MX hosts covered #34

Every MX host matches an mx: line of the MTA-STS policy.
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 1 MX host publish DNSSEC-validated TLSA records.

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