Mail domain report: zacks.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:208.85.51.130 ip4:208.85.51.134 include:sendgrid.net include:spf.protection.outlook.com include:_spf_uswest2.prod.hydra.sophos.com ip4:208.65.116.58 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.8.0/21 include:et._spf.pardot.com include:49604619.spf03.hubspotemail.net include:_spf.salesforce.com include:_spf.google.com ~all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

Found

Record: v=DMARC1; p=quarantine; rua=mailto:YDaPefzO6S@dmarc.inboxmonster.com;
Found at: _dmarc.zacks.com
External report address: mailto:YDaPefzO6S@dmarc.inboxmonster.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:YDaPefzO6S@dmarc.inboxmonster.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:YDaPefzO6S@dmarc.inboxmonster.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

warn

Selectors: google, s1, s2

Found

Selectors: google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: google, s1, s2 #7

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

1024-bit DKIM key

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

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: ECDSAP256SHA256 (13)
Key tags: 4067, 8152
Signatures valid until: 29 November 2026, 04: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 valid until 2026-11-29 #21

DNSKEY signatures are valid until 2026-11-29T04:00:24Z.

MX

warn

2 mail servers

Found

Priority	Host	Records	Reverse DNS
1	mx-01-us-west-2.prod.hydra.sophos.com	A 52.27.15.38 A 44.242.39.10 A 54.71.245.22	ec2-52-27-15-38.us-west-2.compute.amazonaws.com ✓ ec2-44-242-39-10.us-west-2.compute.amazonaws.com ✓ ec2-54-71-245-22.us-west-2.compute.amazonaws.com ✓
5	mx-02-us-west-2.prod.hydra.sophos.com	A 52.27.15.38 A 54.71.245.22 A 44.242.39.10	ec2-52-27-15-38.us-west-2.compute.amazonaws.com ✓ ec2-54-71-245-22.us-west-2.compute.amazonaws.com ✓ ec2-44-242-39-10.us-west-2.compute.amazonaws.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: mx-01-us-west-2.prod.hydra.sophos.com, mx-02-us-west-2.prod.hydra.sophos.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 6 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
mx-01-us-west-2.prod.hydra.sophos.com	none	-
mx-02-us-west-2.prod.hydra.sophos.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

pass

https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.svg

Found

Record: v=BIMI1;l=https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.svg;a=https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.pem
Found at: default._bimi.zacks.com
Logo: https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.svg
Certificate: https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.svg; certificate: https://vmc.digicert.com/ab6236e4-7fa7-43a8-91d0-7fcdfd55066b.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.