SurfaceMap › u › uptodown.com

uptodown.com

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

Domain & DNS

warn

24 passed 1 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    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 uptodown.com ›

Mail

fail

22 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✗
    Policy not reachable
    TLS · The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.uptodown.com/.well-known/mta-sts.txt returned HTTP 404.
    #33
  • !
    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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

✗

Full report

Mail report for uptodown.com ›