mediatek.com

23 passed 4 warn 1 failed

Areas

Problems

• ✗

  No DNS over TCP

  Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: hfdns1.mediatek.com (36.7.68.171): dial tcp 36.7.68.171:53: i/o timeout; hfdns2.mediatek.com (36.7.144.143): dial tcp 36.7.144.143:53: i/o timeout; sjdns1.mediatek.com (66.171.122.170): dial tcp 66.171.122.170:53: i/o timeout; sjdns2.mediatek.com (216.200.240.180): dial tcp 216.200.240.180:53: i/o timeout; twdns1.mediatek.com (210.61.82.125): dial tcp 210.61.82.125:53: i/o timeout; twdns2.mediatek.com (219.87.28.2): dial tcp 219.87.28.2:53: i/o timeout.

  #19
• !

  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: hfdns1.mediatek.com: "9.18.37"; hfdns2.mediatek.com: "9.18.37"; sjdns1.mediatek.com: "9.18.37"; sjdns2.mediatek.com: "9.18.37"; twdns1.mediatek.com: "9.18.37"; twdns2.mediatek.com: "9.18.37". 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
• !

  Very low TTLs

  Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (30s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.

  #32

Recent checks

Full report

Domain & DNS report for mediatek.com ›