asuscomm.com

Checked 22 October 2026, 07:50 UTC · via 8.8.8.8
✗Problems found
18 passed 7 warnings 1 failed 5 info

Registration

info

.com generic · Net-Chinese Co., Ltd. · expires 2034-01-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Net-Chinese Co., Ltd.
Registered
8 January 2007
Last changed
27 August 2026
Expires
8 January 2034
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns-nw.asuscomm.com, ns2.asuscomm.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 2034-01-08 #3
    The registration is valid until 2034-01-08 (2635 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns-nw.asuscomm.com, ns2.asuscomm.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns-nw.asuscomm.com, ns2.asuscomm.com
NS in the zone
ns-nw.asuscomm.com
NameserverAddressesNetwork (AS)Glue
ns-nw.asuscomm.com52.250.42.40AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US52.250.42.40
ns2.asuscomm.com (parent only)52.250.42.40AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US52.250.42.40

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns-nw.asuscomm.com, ns2.asuscomm.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.asuscomm.com. ns-nw.asuscomm.com, ns2.asuscomm.com report NS ns-nw.asuscomm.com.
    #7
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns-nw.asuscomm.com, ns2.asuscomm.com.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • !
    Nameservers in one network
    all IPv4 addresses are in 52.250.42.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-nw.asuscomm.com 52.250.42.40NOERROR, 160 ms, authoritativenono / norefused-
ns2.asuscomm.com 52.250.42.40NOERROR, 161 ms, authoritativenono / norefused-

Checks

  • ✓ All respond #14
    All 2 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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: ns-nw.asuscomm.com (52.250.42.40): dial tcp 52.250.42.40:53: connect: connection refused; ns2.asuscomm.com (52.250.42.40): dial tcp 52.250.42.40:53: connect: connection refused.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns-nw.asuscomm.com (52.250.42.40), ns2.asuscomm.com (52.250.42.40).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 55 · primary ns-nw.asuscomm.com

Found

Primary (MNAME)
ns-nw.asuscomm.com
Contact (RNAME)
chris1_wang.asuscomm.com
Serial
55
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
30 s

Serial per nameserver

NameserverSerial
ns-nw.asuscomm.com (52.250.42.40)55
ns2.asuscomm.com (52.250.42.40)55

Checks

  • ✓ Serial 55 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 30s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 8h, retry 2h, expire 7d, negative TTL 30s.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-nw.asuscomm.com is one of the listed nameservers.
  • ✓ Contact chris1_wang@asuscomm.com #25
    The SOA RNAME chris1_wang.asuscomm.com means chris1_wang@asuscomm.com.
  • ✓ Counter serial #26
    The serial 55 is a plain counter.

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

5 records at the apex

Found

Read from
52.250.42.40:53
TypeValueTTL
SOAns-nw.asuscomm.com. chris1_wang.asuscomm.com. 55 28800 7200 604800 3086400
NSns-nw.asuscomm.com.86400
A52.250.42.4086400
MX10 hostmaster.asuscomm.com.120
TXT"Vrn20d-nLvmiEq-FsPwCItKcYL0k4m-HgP2cIo0E47o"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; 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