Mail domain report: thredup.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:spf.mandrillapp.com include:servers.mcsv.net include:_spf.google.com include:shops.shopify.com include:19569156.spf07.hubspotemail.net ~all
DNS lookups: 5 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

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

Found

Record: v=DMARC1;p=reject;pct=100;rua=mailto:it_dmarc@thredup.com
Found at: _dmarc.thredup.com

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:it_dmarc@thredup.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:it_dmarc@thredup.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: k1, google, s1, s2

Found

Selectors: k1, google, s1, s2
_domainkey: NOERROR

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

Checks

✓ Keys found: k1, google, s1, s2 #7

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

1024-bit DKIM key

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

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

1 mail server

Found

Priority	Host	Records	Reverse DNS
1	smtp.google.com	A 142.251.127.27 A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓

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

fail

MTA-STS enforce · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record: v=STSv1;id=1749424374088;
Policy URL: https://mta-sts.thredup.com/.well-known/mta-sts.txt
Mode: enforce
Allowed MX: alt1.aspmx.l.google.com, aspmx2.googlemail.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx3.googlemail.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1;rua=mailto:smtp-tls-reports@thredup.com;

DANE (TLSA records)

MX host	TLSA	DNSSEC
smtp.google.com	none	-

Checks

✗

Invalid MTA-STS record

Senders ignore the MTA-STS record because of: 2 v=STSv1 records published; there must be exactly one.

#32
✓ Policy enforced #33

The MTA-STS policy is enforced and cached for 168h0m0s.
✗

MX hosts missing from policy

These MX hosts are not listed in the MTA-STS policy (mx: alt1.aspmx.l.google.com, aspmx2.googlemail.com, alt2.aspmx.l.google.com, aspmx.l.google.com, aspmx3.googlemail.com): smtp.google.com. Senders that enforce MTA-STS will refuse to deliver to them.

#34
✓ Reports enabled #35

TLS reports are sent to: mailto:smtp-tls-reports@thredup.com
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/7b797950-8d2c-49ca-acbc-5a842e0cc803.svg

Found

Record: v=BIMI1;l=https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.svg;a=https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.pem
Found at: default._bimi.thredup.com
Logo: https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.svg
Certificate: https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.svg; certificate: https://vmc.digicert.com/7b797950-8d2c-49ca-acbc-5a842e0cc803.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.