SurfaceMap › t › tom.com

tom.com

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

Domain & DNS

fail

23 passed 4 warn 1 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to www.tom.com.3thj0n4b8fls.e.aliyunwaf2.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; a.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.00"; b.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.00"; b.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; c.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; c.dnspod.com: "DNSPod AUTHORITY DNS 7.3.2512.00". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #23
  • !
    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 tom.com ›

Mail

fail

9 passed 5 warn 3 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.tom.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: tommx.tom.com
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: tommx.tom.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for tom.com ›