rt.cm - dns.ninja

rt.cm

DNSSEC⚠️ Not signed
A154.194.251.101🇲🇾 ANSHENG-AS-AP154.194.251.0/24 LANDUI CLOUD COMPUTING (HK) LIMITED
NSns1.netsto.net
A2a03:90c0:9990::1053🇷🇺 GCORE2a03:90c0:9990::/48 GCL-DNS-ANYCAST
A92.223.100.53🇱🇺 GCORE92.223.100.0/24 GCL-DNS-ANYCAST-92-223-100
PTRns1.gcorelabs.net
A92.223.100.153🇱🇺 GCORE92.223.100.0/24 GCL-DNS-ANYCAST-92-223-100
NSns2.netsto.net
A2a03:90c0:9990::2053🇷🇺 GCORE2a03:90c0:9990::/48 GCL-DNS-ANYCAST
A92.223.77.53🇱🇺 GCORE92.223.77.0/24 GCL-DNS-ANYCAST-92-223-77
PTRns2.gcdn.services
A92.223.77.153🇱🇺 GCORE92.223.77.0/24 GCL-DNS-ANYCAST-92-223-77
SOAns1.netsto.netsupport@netsto.com serial=1770222062

cm

DNSSEC🔒 Signed (DS record present)
A195.24.205.60🇨🇲 CAMNET-AS195.24.205.0/24
NSns1.nic.cm
NSauth02.ns.uu.net ⚠️ Not in parent delegation
NSns-cm.afrinic.net ⚠️ Not in parent delegation
NSns-cm.nic.fr ⚠️ Not in parent delegation
NSns.itu.ch ⚠️ Not in parent delegation
NSns2.nic.cm
NSphloem.uoregon.edu ⚠️ Not in parent delegation
TXTGeneration Time ISO 8601: 2026-07-12 21:05:27
TXTGeneration Time: 1783890327
SOAns1.nic.cmdotcm@antic.cm 2026-07-12 #21

Same first word

Similar names

DNS History

25 records (3 active, 22 former)

20162017201820192020202120222023202420252026NSns1.netsto.netns2.netsto.netf1g1ns1.dnspod.netf1g1ns2.dnspod.netns1.bodis.comns1.dns.comns1.myhostadmin.netns2.bodis.comns2.dns.comns2.myhostadmin.netns3.myhostadmin.netns4.myhostadmin.netns5.myhostadmin.netns6.myhostadmin.netMXmx76.m2bp.commx76.mb1p.comA154.194.251.101115.29.200.111118.99.13.129124.16.31.156199.59.242.150199.59.243.120CNAMEcdn.9peng.netparkmydomain.vhostgo.comwww.9peng.net
NSf1g1ns1.dnspod.net2015-08-31 → 2016-01-27 · 4 obs
● 2015-08-31 21:49:30
● 2016-01-27 16:10:00
○ 2016-03-06 19:16:34
○ 2026-07-12 22:30:08
NSf1g1ns2.dnspod.net2015-08-31 → 2016-01-27 · 4 obs
● 2015-08-31 21:49:30
● 2016-01-27 16:10:00
○ 2016-03-06 19:16:34
○ 2026-07-12 22:30:08
NSns1.bodis.com2016-03-15 → 2017-05-24 · 5 obs
○ 2016-03-06 19:16:34
● 2016-03-15 22:18:42
● 2017-05-24 02:53:56
○ 2018-10-20 09:24:54
○ 2026-07-12 22:30:08
NSns1.dns.com2018-10-20 → 2021-05-04 · 5 obs
○ 2017-05-24 02:53:56
● 2018-10-20 09:24:54
● 2021-05-04 20:14:12
○ 2026-02-18 13:38:42
○ 2026-07-12 22:30:08
NSns1.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
NSns1.netsto.net2026-02-18 → 2026-07-12 · 6 obs
○ 2021-05-04 20:14:12
● 2026-02-18 13:38:42
● 2026-04-08 18:49:40
○ 2026-04-09 00:47:16
● 2026-04-12 10:39:16
● 2026-07-12 22:30:08
NSns2.bodis.com2016-03-15 → 2017-05-24 · 5 obs
○ 2016-03-06 19:16:34
● 2016-03-15 22:18:42
● 2017-05-24 02:53:56
○ 2018-10-20 09:24:54
○ 2026-07-12 22:30:08
NSns2.dns.com2018-10-20 → 2021-05-04 · 5 obs
○ 2017-05-24 02:53:56
● 2018-10-20 09:24:54
● 2021-05-04 20:14:12
○ 2026-02-18 13:38:42
○ 2026-07-12 22:30:08
NSns2.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
NSns2.netsto.net2026-02-18 → 2026-07-12 · 6 obs
○ 2021-05-04 20:14:12
● 2026-02-18 13:38:42
● 2026-04-08 18:49:40
○ 2026-04-09 00:47:16
● 2026-04-12 10:39:16
● 2026-07-12 22:30:08
NSns3.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
NSns4.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
NSns5.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
NSns6.myhostadmin.net2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
MXmx76.m2bp.com2017-02-02 → 2017-05-24 · 4 obs
● 2017-02-02 10:45:00
● 2017-05-24 02:53:56
○ 2018-10-20 09:24:54
○ 2026-07-12 22:30:08
MXmx76.mb1p.com2017-02-02 → 2017-05-24 · 4 obs
● 2017-02-02 10:45:00
● 2017-05-24 02:53:56
○ 2018-10-20 09:24:54
○ 2026-07-12 22:30:08
A115.29.200.1112015-08-31 → 2016-01-27 · 4 obs
● 2015-08-31 21:49:30
● 2016-01-27 16:10:00
○ 2016-03-06 19:16:34
○ 2026-07-12 22:30:08
A118.99.13.1292018-10-20 → 2018-10-20 · 4 obs
○ 2017-05-24 02:53:56
● 2018-10-20 09:24:54
○ 2019-07-31 13:11:52
○ 2026-07-12 22:30:08
A124.16.31.1562016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
A154.194.251.1012026-02-18 → 2026-07-12 · 6 obs
○ 2019-07-31 13:11:52
● 2026-02-18 13:38:42
● 2026-04-08 18:49:40
○ 2026-04-09 00:47:16
● 2026-04-12 10:39:16
● 2026-07-12 22:30:08
A199.59.242.1502016-12-28 → 2017-01-08 · 5 obs
○ 2016-12-01 05:17:08
● 2016-12-28 11:49:18
● 2017-01-08 22:21:08
○ 2017-02-02 10:45:00
○ 2026-07-12 22:30:08
A199.59.243.1202016-03-15 → 2017-05-24 · 9 obs
○ 2016-03-06 19:16:34
● 2016-03-15 22:18:42
● 2016-12-01 05:17:08
○ 2016-12-28 11:49:18
○ 2017-01-08 22:21:08
● 2017-02-02 10:45:00
● 2017-05-24 02:53:56
○ 2018-10-20 09:24:54
○ 2026-07-12 22:30:08
CNAMEcdn.9peng.net2015-08-31 → 2016-01-27 · 4 obs
● 2015-08-31 21:49:30
● 2016-01-27 16:10:00
○ 2016-03-06 19:16:34
○ 2026-07-12 22:30:08
CNAMEparkmydomain.vhostgo.com2016-03-06 → 2016-03-06 · 4 obs
○ 2016-01-27 16:10:00
● 2016-03-06 19:16:34
○ 2016-03-15 22:18:42
○ 2026-07-12 22:30:08
CNAMEwww.9peng.net2015-09-09 → 2016-01-27 · 5 obs
○ 2015-08-31 21:49:30
● 2015-09-09 16:03:12
● 2016-01-27 16:10:00
○ 2016-03-06 19:16:34
○ 2026-07-12 22:30:08

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
cmns.itu.ch, ns1.nic.cm, ns2.nic.cm, ns-cm.nic.fr...11 records
rt.cmns1.netsto.net, ns2.netsto.net-

✅ Authoritative Response

Server:92.223.77.53

NS records: ns1.netsto.net, ns2.netsto.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rt.cm (unsigned zone)

⏱️ Timing

Total: 970ms | Queries: -

📄 Records

TypeCountSample Data
A1154.194.251.101
NS2ns2.netsto.net, ns1.netsto.net
SOA1ns1.netsto.net support.netsto.com

📌 Glue Records Collected

Total: 11

In-bailiwick: 2 (ns1.nic.cm, ns2.nic.cm)

Out-of-bailiwick: 9 (ns.itu.ch, ns.itu.ch, ns-cm.nic.fr...)

Analysis

IP Addresses

rt.cm points to a single IP number: 154.194.251.101.

Additional host names — lebanon.cw.cm, sl.cm, sswcs.en.cm and two others — share IP numbers with rt.cm.

Name Servers

The NS records for rt.cm delegate to ns1.netsto.net and ns2.netsto.net.

rt.cm shares its name server setup with other domains, including 6c87.com, 54017.cn, web3ai.ee and two others.

rt.cm and other domains like tera.ws share at least a portion of their name servers.

ns1.netsto.net and ns2.netsto.net each have three IP addresses — ns1.netsto.net directs to 92.223.100.53, 92.223.100.153 and 2a03:90c0:9990::1053; ns2.netsto.net directs to 92.223.77.53, 92.223.77.153 and 2a03:90c0:9990::2053.