mediatek.com

Checked 22 October 2026, 09:44 UTC · via 8.8.8.8
✗Problems found
23 passed 4 warnings 1 failed 3 info

Registration

info

.com generic · Network Solutions, LLC · expires 2027-09-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
3 September 2001
Last changed
21 April 2026
Expires
3 September 2027
Status
client transfer prohibited
Registry nameservers
hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-09-03 #3
    The registration is valid until 2027-09-03 (316 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com
NS in the zone
hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com
NameserverAddressesNetwork (AS)Glue
hfdns1.mediatek.com36.7.68.171AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN36.7.68.171
hfdns2.mediatek.com36.7.144.143AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN36.7.144.143
sjdns1.mediatek.com66.171.122.170AS33717 CHT-GLOBAL - Chunghwa Telecom Global, INC, US66.171.122.170
sjdns2.mediatek.com216.200.240.180AS6461 ZAYO-6461 - Zayo Bandwidth, US216.200.240.180
twdns1.mediatek.com210.61.82.125AS3462 HINET - Data Communication Business Group, TW210.61.82.125
twdns2.mediatek.com219.87.28.2AS9924 TFN-TW - Taiwan Fixed Network, Telco and Network Service Provider., TW219.87.28.2

Checks

  • ✓ 6 nameservers #6
    Delegated to hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: hfdns1.mediatek.com, hfdns2.mediatek.com, sjdns1.mediatek.com, sjdns2.mediatek.com, twdns1.mediatek.com, twdns2.mediatek.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 6 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 5 autonomous systems #11
    The nameservers are spread over: AS33717 (CHT-GLOBAL - Chunghwa Telecom Global, INC, US): 1 address; AS3462 (HINET - Data Communication Business Group, TW): 1 address; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 2 addresses; AS6461 (ZAYO-6461 - Zayo Bandwidth, US): 1 address; AS9924 (TFN-TW - Taiwan Fixed Network, Telco and Network Service Provider., TW): 1 address.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
hfdns1.mediatek.com 36.7.68.171NOERROR, 219 ms, authoritativenono / yesrefused9.18.37
hfdns2.mediatek.com 36.7.144.143NOERROR, 196 ms, authoritativenono / yesrefused9.18.37
sjdns1.mediatek.com 66.171.122.170NOERROR, 173 ms, authoritativenono / yesrefused9.18.37
sjdns2.mediatek.com 216.200.240.180NOERROR, 146 ms, authoritativenono / yesrefused9.18.37
twdns1.mediatek.com 210.61.82.125NOERROR, 227 ms, authoritativenono / yesrefused9.18.37
twdns2.mediatek.com 219.87.28.2NOERROR, 249 ms, authoritativenono / yesrefused9.18.37

Checks

  • ✓ All respond #14
    All 6 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    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
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026101901 · primary twdns1.mediatek.com

Found

Primary (MNAME)
twdns1.mediatek.com
Contact (RNAME)
admin.mtk.com.tw
Serial
2026101901
Refresh / retry
10800 s / 3600 s
Expire
3600000 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
hfdns1.mediatek.com (36.7.68.171)2026101901
hfdns2.mediatek.com (36.7.144.143)2026101901
sjdns1.mediatek.com (66.171.122.170)2026101901
sjdns2.mediatek.com (216.200.240.180)2026101901
twdns1.mediatek.com (210.61.82.125)2026101901
twdns2.mediatek.com (219.87.28.2)2026101901

Checks

  • ✓ Serial 2026101901 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 1000h, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver twdns1.mediatek.com is one of the listed nameservers.
  • ✓ Contact admin@mtk.com.tw #25
    The SOA RNAME admin.mtk.com.tw means admin@mtk.com.tw.
  • ✓ Date-based serial #26
    The serial 2026101901 follows the YYYYMMDDnn convention (2026-10-19).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

warn

17 records at the apex

Found

Read from
36.7.68.171:53
TypeValueTTL
SOAtwdns1.mediatek.com. admin.mtk.com.tw. 2026101901 10800 3600 3600000 86400300
NShfdns1.mediatek.com.300
NSsjdns2.mediatek.com.300
NSsjdns1.mediatek.com.300
NStwdns1.mediatek.com.300
NStwdns2.mediatek.com.300
NShfdns2.mediatek.com.300
A60.250.184.10130
MX10 mailgw01.mediatek.com.86400
MX10 mailgw02.mediatek.com.86400
TXT"zeE++HY1HDpYIArRGkTj8VKRpIhpNaXinQpQB0czThYwXqxadC2iF0zgfUsxMtv61g7Y7fpEZNGxa5PKIQ+g0A=="300
TXT"DEOUnkuiriVz/t7kGlLtL3luCLDr2AkEfRiY6l2wC3iaNed/NHE600ndvbFt3K4bM05XQCxQ0YhTiB9rYRmILw=="300
TXT"apple-domain-verification=aoExaIJncTfUoGR6"300
TXT"v=spf1 include:spf.mediatek.com include:bmsend.com include:spf.protection.outlook.com include:_spf.qualtrics.com include:_spf.google.com -all"300
TXT"google-site-verification=0EJmrJwt-JV9g2wy9NClju8ynZcIbaSWKsrdBqAXSHM"300
TXT"ca3-e1b9af3377dc42858ef959628b33b359"300
TXT"facebook-domain-verification=aev8borqu0mtb43scdgioqksjrvb4u"300

Checks

  • !
    Very low TTLs
    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
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35