london2012.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
!Passed with warnings
22 passed 4 warnings 0 failed 5 info

Registration

info

.com generic · Nom-iq Ltd. dba COM LAUDE · expires 2027-11-20

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Nom-iq Ltd. dba COM LAUDE
Registered
20 November 2002
Last changed
21 October 2026
Expires
20 November 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
vip7.alidns.com, vip8.alidns.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-11-20 #3
    The registration is valid until 2027-11-20 (394 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

vip7.alidns.com, vip8.alidns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
vip7.alidns.com, vip8.alidns.com
NS in the zone
vip7.alidns.com, vip8.alidns.com
NameserverAddressesNetwork (AS)Glue
vip7.alidns.com170.33.32.214 140.205.1.13 47.88.82.208 170.33.80.14 47.254.160.176 8.212.93.7 47.253.24.27 2408:4009:500::7AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN121.40.6.167 140.205.1.13 170.33.32.214 170.33.80.14 2408:4009:500::7 39.103.26.216 47.108.36.167 47.253.24.27 47.254.160.176 47.74.160.227 47.88.82.208 8.212.93.7
vip8.alidns.com170.33.32.215 170.33.80.15 47.88.82.209 8.212.93.8 47.253.24.28 140.205.1.14 47.254.160.177 2408:4009:500::8AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN121.40.6.168 140.205.1.14 170.33.32.215 170.33.80.15 2408:4009:500::8 39.103.26.217 47.108.36.168 47.253.24.28 47.254.160.177 47.74.160.228 47.88.82.209 8.212.93.8

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: vip7.alidns.com, vip8.alidns.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: vip7.alidns.com (glue 121.40.6.167, 140.205.1.13, 170.33.32.214, 170.33.80.14, 2408:4009:500::7, 39.103.26.216, 47.108.36.167, 47.253.24.27, 47.254.160.176, 47.74.160.227, 47.88.82.208, 8.212.93.7, zone 170.33.32.214, 140.205.1.13, 47.88.82.208, 170.33.80.14, 47.254.160.176, 8.212.93.7, 47.253.24.27, 2408:4009:500::7); vip8.alidns.com (glue 121.40.6.168, 140.205.1.14, 170.33.32.215, 170.33.80.15, 2408:4009:500::8, 39.103.26.217, 47.108.36.168, 47.253.24.28, 47.254.160.177, 47.74.160.228, 47.88.82.209, 8.212.93.8, zone 170.33.32.215, 170.33.80.15, 47.88.82.209, 8.212.93.8, 47.253.24.28, 140.205.1.14, 47.254.160.177, 2408:4009:500::8). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2408:4009:500::/48, while the other address family is spread over several networks.
    #10
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS134963 (ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG): 3 addresses; AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 1 address; AS45102 (ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN): 12 addresses.
  • 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

pass

16 of 16 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
vip7.alidns.com 170.33.32.214NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 140.205.1.13NOERROR, 5 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 47.88.82.208NOERROR, 160 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 170.33.80.14NOERROR, 263 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 47.254.160.176NOERROR, 5 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 8.212.93.7NOERROR, 241 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 47.253.24.27NOERROR, 103 ms, authoritativenoyes / yesrefused-
vip7.alidns.com 2408:4009:500::7NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 170.33.32.215NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 170.33.80.15NOERROR, 249 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 47.88.82.209NOERROR, 158 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 8.212.93.8NOERROR, 165 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 47.253.24.28NOERROR, 102 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 140.205.1.14NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 47.254.160.177NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip8.alidns.com 2408:4009:500::8NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 16 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.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026081810 · primary vip7.alidns.com

Found

Primary (MNAME)
vip7.alidns.com
Contact (RNAME)
hostmaster.hichina.com
Serial
2026081810
Refresh / retry
3600 s / 1200 s
Expire
86400 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
vip7.alidns.com (170.33.32.214)2026081810
vip7.alidns.com (140.205.1.13)2026081810
vip7.alidns.com (47.88.82.208)2026081710
vip7.alidns.com (170.33.80.14)2026082516
vip7.alidns.com (47.254.160.176)2026082415
vip7.alidns.com (8.212.93.7)2022061416
vip7.alidns.com (47.253.24.27)2026081812
vip7.alidns.com (2408:4009:500::7)2026082415
vip8.alidns.com (170.33.32.215)2026081716
vip8.alidns.com (170.33.80.15)2026081716
vip8.alidns.com (47.88.82.209)2026081710
vip8.alidns.com (8.212.93.8)2026081316
vip8.alidns.com (47.253.24.28)2026081810
vip8.alidns.com (140.205.1.14)2026081810
vip8.alidns.com (47.254.160.177)2026081810
vip8.alidns.com (2408:4009:500::8)2026082415

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2022061416 on vip7.alidns.com (8.212.93.7); 2026081316 on vip8.alidns.com (8.212.93.8); 2026081710 on vip7.alidns.com (47.88.82.208), vip8.alidns.com (47.88.82.209); 2026081716 on vip8.alidns.com (170.33.32.215), vip8.alidns.com (170.33.80.15); 2026081810 on vip7.alidns.com (170.33.32.214), vip7.alidns.com (140.205.1.13), vip8.alidns.com (47.253.24.28), vip8.alidns.com (140.205.1.14), vip8.alidns.com (47.254.160.177); 2026081812 on vip7.alidns.com (47.253.24.27); 2026082415 on vip7.alidns.com (47.254.160.176), vip7.alidns.com (2408:4009:500::7), vip8.alidns.com (2408:4009:500::8); 2026082516 on vip7.alidns.com (170.33.80.14). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver vip7.alidns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@hichina.com #25
    The SOA RNAME hostmaster.hichina.com means hostmaster@hichina.com.
  • ✓ Date-based serial #26
    The serial 2026081810 follows the YYYYMMDDnn convention (2026-08-18).

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

9 records at the apex

Found

Read from
170.33.32.214:53
TypeValueTTL
SOAvip7.alidns.com. hostmaster.hichina.com. 2026081716 3600 1200 86400 600600
NSvip8.alidns.com.86400
NSvip7.alidns.com.86400
A8.208.27.943600
A47.91.87.1643600
MX20 cluster4a.eu.messagelabs.com.3600
MX10 cluster4.eu.messagelabs.com.3600
TXT"google-site-verification=wywghqLFFxCHh4DN0tAk8slhLhFaBiVnaW6xKNkpmvg"3600
TXT"v=spf1ip4:213.48.118.37ip4:213.121.128.0/26ip4:89.234.20.132/28ip4:213.215.157.240ip4:213.121.129.192/26ip4:89.187.66.118ip4:62.140.221.10ip4:202.60.76.30ip4:194.116.199.82ip4:213.86.53.6ip4:217.10.139.67ip4:46.231.186.200mx"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, 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