cmslauncher.cloud - dns.ninja
cmslauncher.cloud
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1782902728 | ||||||
Same first word
cmslauncher.cloud |
cmslauncher.com |
Similar names
DNS History
30 records (12 active, 18 former)
●NShehua.ns.giantpanda.com2026-05-16 → 2026-07-01 · 3 obs
● 2026-05-16 19:10:46
● 2026-07-01 10:54:54
○NSns1.cmslauncher.com2018-01-30 → 2018-01-30 · 3 obs
○ 2026-05-16 19:10:46
○ 2026-07-01 10:54:54
○NSns2.cmslauncher.com2018-01-30 → 2018-01-30 · 3 obs
○ 2026-05-16 19:10:46
○ 2026-07-01 10:54:54
●NSqizai.ns.giantpanda.com2026-05-16 → 2026-07-01 · 3 obs
● 2026-05-16 19:10:46
● 2026-07-01 10:54:54
○MXmail.cmslauncher.cloud2018-01-30 → 2018-01-30 · 3 obs
○ 2026-05-16 19:10:46
○ 2026-07-01 10:54:54
●A139.162.174.2092026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A139.162.181.762026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A172.104.149.862026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A172.104.203.1862026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A172.104.251.1982026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
○A192.155.84.2362026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A23.239.4.932026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A2600:3c01::2000:3aff:feb3:2e942026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A2600:3c01::f03c:95ff:fe91:5de52026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A2600:3c01::f03c:95ff:feeb:5ed62026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A2600:3c03::f03c:95ff:fe00:29ca2026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A2600:3c03::f03c:95ff:fe91:5d522026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A2600:3c03::f03c:95ff:feed:4d4f2026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A2600:3c03::f03c:95ff:feed:cf2a2026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
●A2a01:7e01::2000:dff:fec1:5cdb2026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A2a01:7e01::f03c:95ff:fe00:26922026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A2a01:7e01::f03c:95ff:fe91:5d912026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A2a01:7e01::f03c:95ff:feeb:9d4b2026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
●A2a01:7e01::f03c:95ff:feed:783e2026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:59:32
● 2026-07-01 10:54:54
○A45.33.83.1002026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A45.79.167.1802026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A66.175.209.1792026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
○A68.65.120.2112018-01-30 → 2018-01-30 · 3 obs
○ 2026-05-16 19:10:46
○ 2026-07-01 10:54:54
○A74.207.241.2452026-05-16 → 2026-05-16 · 4 obs
● 2026-05-16 19:10:46
○ 2026-07-01 00:27:04
○ 2026-07-01 10:54:54
○A96.126.111.1652026-07-01 → 2026-07-01 · 4 obs
● 2026-07-01 00:27:04
○ 2026-07-01 09:59:32
○ 2026-07-01 10:54:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| cmslauncher.cloud | hehua.ns.giantpanda.com, qizai.ns.giantpanda.com | - |
✅ Authoritative Response
Server:3.33.232.36
NS records: hehua.ns.giantpanda.com, qizai.ns.giantpanda.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cmslauncher.cloud (unsigned zone)
⏱️ Timing
Total: 421ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 66.175.209.179, 96.126.111.165... |
| AAAA | 4 | 2600:3c03::f03c:95ff:fe00:29ca, 2600:3c03::f03c:95ff:feed:4d4f... |
| NS | 2 | hehua.ns.giantpanda.com, qizai.ns.giantpanda.com |
| SOA | 1 | hehua.ns.giantpanda.com admin.giantpanda |
Analysis
IP Addresses
cmslauncher.cloud has 10 IP addresses — 139.162.174.209, 139.162.181.76, 172.104.149.86 and 7 more.
mytechno.com, thewood.com.au, samika.com and two other host names share IP numbers with cmslauncher.cloud.
Name Servers
cmslauncher.cloud uses two name servers for its delegation: hehua.ns.giantpanda.com and qizai.ns.giantpanda.com.
cmslauncher.cloud uses the same name servers as several other domains — among them bodyshapefashionadvice.com, go-partner.biz, uxobx.xyz and two more.
cmslauncher.cloud has at least partial name server overlap with other domains, such as kia.com.in, www.gtor.online, louisefstokes.kafechew.info and two others.
It is common to see these name servers used together with name servers zhenzhen.ns.giantpanda.com and panpan.ns.giantpanda.com.
hehua.ns.giantpanda.com directs to 3.33.232.36 and qizai.ns.giantpanda.com directs to 75.2.45.63; each host name points to exactly one IP number.