bcebos.com

Checked 22 October 2026, 07:53 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 6 info

Registration

info

.com generic · Key-Systems GmbH · expires 2027-08-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Key-Systems GmbH
Registered
28 August 2014
Last changed
27 July 2026
Expires
28 August 2027
Status
client transfer prohibited
Registry nameservers
ns1.baidubce.com, ns2.baidubce.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-08-28 #3
    The registration is valid until 2027-08-28 (310 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

info

ns1.baidubce.com, ns2.baidubce.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.baidubce.com, ns2.baidubce.com
NS in the zone
ns1.baidubce.com, ns2.baidubce.com
NameserverAddressesNetwork (AS)Glue
ns1.baidubce.com111.206.208.183AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN111.206.208.183
ns2.baidubce.com180.97.107.151 240e:bf:b801:1007:0:ff:b001:2389 240e:940:603:b:0:ff:b0cd:257dAS137702 CHINATELECOM-JIANGSU-NANJING-IDC - Nanjing, Jiangsu Province, P.R.China., CN AS134768 CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN180.97.107.151 240e:940:603:b:0:ff:b0cd:257d 240e:bf:b801:1007:0:ff:b001:2389

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.baidubce.com, ns2.baidubce.com.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS134768 (CHINANET-SHAANXI-CLOUD-BASE - CHINANET SHAANXI province Cloud Base network, CN): 1 address; AS137702 (CHINATELECOM-JIANGSU-NANJING-IDC - Nanjing, Jiangsu Province, P.R.China., CN): 1 address; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 1 address; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.baidubce.com.
    #13

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.baidubce.com 111.206.208.183NOERROR, 239 ms, authoritativenoyes / yesrefusedbaidu dns
ns2.baidubce.com 180.97.107.151NOERROR, 205 ms, authoritativenoyes / norefused-
ns2.baidubce.com 240e:bf:b801:1007:0:ff:b001:2389NOERROR, 170 ms, authoritativenoyes / yesrefusedbaidu dns
ns2.baidubce.com 240e:940:603:b:0:ff:b0cd:257dNOERROR, 160 ms, authoritativenoyes / yesrefusedbaidu dns

Checks

  • ✓ All respond #14
    All 4 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.baidubce.com: "baidu dns"; ns2.baidubce.com: "baidu dns".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns2.baidubce.com (180.97.107.151).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2015168518 · primary ns1.baidubce.com

Found

Primary (MNAME)
ns1.baidubce.com
Contact (RNAME)
sa.baidu.com
Serial
2015168518
Refresh / retry
30 s / 30 s
Expire
2592000 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns1.baidubce.com (111.206.208.183)2015168518
ns2.baidubce.com (180.97.107.151)2015168518
ns2.baidubce.com (240e:bf:b801:1007:0:ff:b001:2389)2015168518
ns2.baidubce.com (240e:940:603:b:0:ff:b0cd:257d)2015168518

Checks

  • ✓ Serial 2015168518 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 30s is outside 20m–1d; retry 30s should be shorter than refresh 30s. Current values: refresh 30s, retry 30s, expire 30d, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.baidubce.com is one of the listed nameservers.
  • ✓ Contact sa@baidu.com #25
    The SOA RNAME sa.baidu.com means sa@baidu.com.
  • ✓ Timestamp serial #26
    The serial 2015168518 is a Unix timestamp (2033-11-09 17:01 UTC).

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

6 records at the apex

Found

Read from
111.206.208.183:53
TypeValueTTL
SOAns1.baidubce.com. sa.baidu.com. 2015168518 30 30 2592000 6007200
NSns2.baidubce.com.86400
NSns1.baidubce.com.86400
MX10 mx102.dns.com.cn.600
TXT"spf1 include:spf.dns.com.cn ~all"7200
TXT"jbw55l13429zwqlm525vs0khbd1mr8hv"7200

Checks

  • ✓ TTLs within range #32
    TTLs: MX 10m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✓ 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