SurfaceMap › t › thredup.com

thredup.com

Checked 2026-10-22 11:04 UTC · first added 2026-10-21
✗Problems found Score 65 of 100

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: matt.ns.cloudflare.com: "2026.10.2"; rose.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for thredup.com ›

Mail

fail

29 passed 3 warn 2 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC !MX ✗TLS ✓BIMI

Problems

  • ✗
    Invalid MTA-STS record
    TLS · Senders ignore the MTA-STS record because of: 2 v=STSv1 records published; there must be exactly one.
    #32
  • ✗
    MX hosts missing from policy
    TLS · 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
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 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

Recent checks

✗

Full report

Mail report for thredup.com ›