cqtry.com - dns.ninja
cqtry.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | launch1.spaceship.net ⭐ ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | afternic-verification-FEaNfPnq4JXSYa8rsXqAT6 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1733961025 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785240417 | ||||||
Same first word
cqtry.com |
Similar names
DNS History
20 records (2 active, 18 former)
●NSlaunch1.spaceship.net2026-07-28 → 2026-07-28 · 2 obs
○ 2019-04-04 05:40:28
● 2026-07-28 12:23:28
● 2026-07-28 12:23:28
●NSlaunch2.spaceship.net2026-07-28 → 2026-07-28 · 2 obs
○ 2019-04-04 05:40:28
● 2026-07-28 12:23:28
● 2026-07-28 12:23:28
○NSns01.cashparking.com2019-04-04 → 2019-04-04 · 3 obs
○ 2017-02-20 07:33:58
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○NSns02.cashparking.com2019-04-04 → 2019-04-04 · 3 obs
○ 2017-02-20 07:33:58
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○NSns1.bluehost.com2017-02-20 → 2017-02-20 · 4 obs
○ 2016-07-06 23:51:22
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○NSns2.bluehost.com2017-02-20 → 2017-02-20 · 4 obs
○ 2016-07-06 23:51:22
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○NSns71.domaincontrol.com2015-07-22 → 2016-03-03 · 4 obs
● 2015-07-22 16:26:36
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
○NSns72.domaincontrol.com2015-07-22 → 2016-03-03 · 4 obs
● 2015-07-22 16:26:36
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
○NSns73.domaincontrol.com2016-07-06 → 2016-07-06 · 4 obs
○ 2016-03-03 21:45:30
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
○NSns74.domaincontrol.com2016-07-06 → 2016-07-06 · 4 obs
○ 2016-03-03 21:45:30
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
○MX(root)2019-04-04 → 2019-04-04 · 3 obs
○ 2017-02-20 07:33:58
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○MX102019-04-04 → 2019-04-04 · 3 obs
○ 2017-02-20 07:33:58
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○MXmail.cqtry.com2017-02-20 → 2017-02-20 · 4 obs
○ 2016-07-06 23:51:22
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○MXmailstore1.secureserver.net2015-07-22 → 2016-07-06 · 4 obs
● 2015-07-22 16:26:36
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
○MXsmtp.secureserver.net2015-07-22 → 2016-07-06 · 4 obs
● 2015-07-22 16:26:36
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
○A184.168.221.962019-04-04 → 2019-04-04 · 3 obs
○ 2017-02-20 07:33:58
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
○A198.44.253.232015-07-22 → 2015-11-21 · 4 obs
● 2015-07-22 16:26:36
● 2015-11-21 20:15:20
○ 2016-03-03 21:45:30
○ 2026-07-28 12:23:28
● 2015-11-21 20:15:20
○ 2016-03-03 21:45:30
○ 2026-07-28 12:23:28
○A50.63.202.332016-07-06 → 2016-07-06 · 4 obs
○ 2016-03-03 21:45:30
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
● 2016-07-06 23:51:22
○ 2017-02-20 07:33:58
○ 2026-07-28 12:23:28
○A50.63.202.692016-03-03 → 2016-03-03 · 4 obs
○ 2015-11-21 20:15:20
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
● 2016-03-03 21:45:30
○ 2016-07-06 23:51:22
○ 2026-07-28 12:23:28
○A66.147.244.1352017-02-20 → 2017-02-20 · 4 obs
○ 2016-07-06 23:51:22
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
● 2017-02-20 07:33:58
○ 2019-04-04 05:40:28
○ 2026-07-28 12:23:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net, g.gtld-servers.net... | - |
| cqtry.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1114ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | afternic-verification-FEaNfPnq4JXSYa8rsX |
Analysis
Name Servers
cqtry.com is served by two delegated name servers, launch1.spaceship.net and launch2.spaceship.net.
cqtry.com shares its name server setup with other domains, including nutrascale.com, k3h7.com, 0820640.xyz and two others.
The DNS delegation for cqtry.com at least partly coincides with that of other domains, codingguard.com being one example.
Each of the two host names carries two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.