yupoo.com

Checked 22 October 2026, 11:41 UTC · via 8.8.8.8
✗Problems found
20 passed 2 warnings 2 failed 7 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2027-03-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
16 March 2005
Last changed
31 August 2026
Expires
16 March 2027
Status
active
Registry nameservers
ns1.ialloc.com, ns2.ialloc.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-03-16 #3
    The registration is valid until 2027-03-16 (144 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.ialloc.com, ns2.ialloc.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.ialloc.com, ns2.ialloc.com
NS in the zone
ns1.ialloc.com, ns2.ialloc.com
NameserverAddressesNetwork (AS)Glue
ns1.ialloc.com118.24.109.1 2402:4e00:1700:7d00:0:9285:ffec:9d26AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN115.159.66.63 118.24.109.1 2402:4e00:1700:7d00:0:9285:ffec:9d26
ns2.ialloc.com115.159.66.63 2402:4e00:1409:9f00:0:991f:7f1e:1de9AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN115.159.66.63 118.24.109.1 2402:4e00:1409:9f00:0:991f:7f1e:1de9

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.ialloc.com, ns2.ialloc.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns1.ialloc.com (glue 115.159.66.63, 118.24.109.1, 2402:4e00:1700:7d00:0:9285:ffec:9d26, zone 118.24.109.1, 2402:4e00:1700:7d00:0:9285:ffec:9d26); ns2.ialloc.com (glue 115.159.66.63, 118.24.109.1, 2402:4e00:1409:9f00:0:991f:7f1e:1de9, zone 115.159.66.63, 2402:4e00:1409:9f00:0:991f:7f1e:1de9). Update the glue at your registrar.
    #8
  • ✓ 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 2 IPv4 /24s and 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

3 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ialloc.com 118.24.109.1no responsenono / no--
ns1.ialloc.com 2402:4e00:1700:7d00:0:9285:ffec:9d26NOERROR, 204 ms, authoritativenono / yesrefused-
ns2.ialloc.com 115.159.66.63NOERROR, 197 ms, authoritativenono / yesrefused-
ns2.ialloc.com 2402:4e00:1409:9f00:0:991f:7f1e:1de9NOERROR, 225 ms, authoritativenono / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.ialloc.com (118.24.109.1): read udp 46.225.38.91:54701->118.24.109.1:53: i/o timeout.
    #14
  • ✓ 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: ns1.ialloc.com (2402:4e00:1700:7d00:0:9285:ffec:9d26): dial tcp [2402:4e00:1700:7d00:0:9285:ffec:9d26]:53: connect: connection refused; ns2.ialloc.com (115.159.66.63): dial tcp 115.159.66.63:53: connect: connection refused; ns2.ialloc.com (2402:4e00:1409:9f00:0:991f:7f1e:1de9): dial tcp [2402:4e00:1409:9f00:0:991f:7f1e:1de9]:53: connect: connection refused.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2015102101 · primary ns1.ialloc.com

Found

Primary (MNAME)
ns1.ialloc.com
Contact (RNAME)
wtzhu182.163.com
Serial
2015102101
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
10800 s

Serial per nameserver

NameserverSerial
ns1.ialloc.com (2402:4e00:1700:7d00:0:9285:ffec:9d26)2015102101
ns2.ialloc.com (115.159.66.63)2015102101
ns2.ialloc.com (2402:4e00:1409:9f00:0:991f:7f1e:1de9)2015102101

Checks

  • ✓ Serial 2015102101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 3m, expire 14d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ialloc.com is one of the listed nameservers.
  • ✓ Contact wtzhu182@163.com #25
    The SOA RNAME wtzhu182.163.com means wtzhu182@163.com.
  • ✓ Date-based serial #26
    The serial 2015102101 follows the YYYYMMDDnn convention (2015-10-21).

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

info

7 records at the apex

Found

Read from
[2402:4e00:1700:7d00:0:9285:ffec:9d26]:53
TypeValueTTL
SOAns1.ialloc.com. wtzhu182.163.com. 2015102101 3600 180 1209600 10800300
NSns1.ialloc.com.600
NSns2.ialloc.com.600
A106.54.33.145300
TXT"zv35ln57w2yk19kmnhgmkzlr4m0vjhk2"600
TXT"google-site-verification=AY2ooGPxmNpHHToRCvO128kpECV8vCnHyuQf5MVmChk"300
TXT"google-site-verification=Uv5E2QKaKfOrRCFyZkqY6OmWNXM5VHepTWAYxpFMYAU"60

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, NS 10m. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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