code-play.com - dns.ninja
code-play.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| 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 | ||||||
| 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 | dc816f3a-d35a-42d7-8391-353a84af8ccb | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1785767225 | ||||||
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=1787515336 | ||||||
Same first word
code-play.com |
code-play.fr |
code-play.de |
code-play.net |
Similar names
Previous names
Next names
DNS History
21 records (2 active, 19 former)
●NSlaunch1.spaceship.net2026-08-20 → 2026-08-23 · 3 obs
● 2026-08-20 17:02:52
● 2026-08-23 20:14:36
●NSlaunch2.spaceship.net2026-08-20 → 2026-08-23 · 3 obs
● 2026-08-20 17:02:52
● 2026-08-23 20:14:36
○NSns1.namebrightdns.com2015-06-07 → 2017-09-10 · 7 obs
● 2015-11-06 04:27:02
○ 2016-01-28 21:26:50
○ 2016-12-06 17:09:04
● 2017-09-10 08:35:32
○ 2026-08-20 17:02:52
○ 2026-08-23 20:14:36
○NSns2.namebrightdns.com2015-06-07 → 2017-09-10 · 7 obs
● 2015-11-06 04:27:02
○ 2016-01-28 21:26:50
○ 2016-12-06 17:09:04
● 2017-09-10 08:35:32
○ 2026-08-20 17:02:52
○ 2026-08-23 20:14:36
○NSnsg1.namebrightdns.com2015-06-07 → 2016-04-23 · 6 obs
○ 2015-11-06 04:27:02
● 2016-01-28 21:26:50
● 2016-04-23 00:35:12
○ 2016-12-06 17:09:04
○ 2026-08-23 20:14:36
○NSnsg2.namebrightdns.com2016-01-28 → 2016-04-23 · 5 obs
● 2016-01-28 21:26:50
● 2016-04-23 00:35:12
○ 2016-12-06 17:09:04
○ 2026-08-23 20:14:36
○NSnst1.namebrightdns.com2016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 17:09:04
○ 2017-09-10 08:35:32
○ 2026-08-23 20:14:36
○NSnst2.namebrightdns.com2016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 17:09:04
○ 2017-09-10 08:35:32
○ 2026-08-23 20:14:36
○MXanmail.namebrightmail.com2015-06-07 → 2015-06-07 · 3 obs
○ 2015-11-06 04:27:02
○ 2026-08-23 20:14:36
○A44.232.173.2492026-08-20 → 2026-08-20 · 4 obs
● 2026-08-20 17:02:52
○ 2026-08-23 18:52:44
○ 2026-08-23 20:14:36
○A52.200.243.1232016-04-23 → 2016-04-23 · 4 obs
● 2016-04-23 00:35:12
○ 2016-12-06 17:09:04
○ 2026-08-23 20:14:36
○A52.40.42.1132026-08-20 → 2026-08-20 · 4 obs
● 2026-08-20 17:02:52
○ 2026-08-23 18:52:44
○ 2026-08-23 20:14:36
○A54.152.144.2432016-04-23 → 2016-04-23 · 4 obs
● 2016-04-23 00:35:12
○ 2016-12-06 17:09:04
○ 2026-08-23 20:14:36
○A54.174.31.2542015-06-07 → 2015-11-06 · 4 obs
● 2015-11-06 04:27:02
○ 2016-01-28 21:26:50
○ 2026-08-23 20:14:36
○A54.208.74.2152015-06-07 → 2015-11-06 · 4 obs
● 2015-11-06 04:27:02
○ 2016-01-28 21:26:50
○ 2026-08-23 20:14:36
○A54.209.90.812016-01-28 → 2016-01-28 · 4 obs
● 2016-01-28 21:26:50
○ 2016-04-23 00:35:12
○ 2026-08-23 20:14:36
○A54.84.80.1732016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 17:09:04
○ 2017-09-10 08:35:32
○ 2026-08-23 20:14:36
○A54.85.54.292016-01-28 → 2016-01-28 · 4 obs
● 2016-01-28 21:26:50
○ 2016-04-23 00:35:12
○ 2026-08-23 20:14:36
○A54.88.107.1402016-12-06 → 2016-12-06 · 4 obs
● 2016-12-06 17:09:04
○ 2017-09-10 08:35:32
○ 2026-08-23 20:14:36
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-06-07 → 2016-04-23 · 4 obs
● 2016-04-23 00:35:12
○ 2016-12-06 17:09:04
○ 2026-08-23 20:14:36
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2016-12-06 → 2017-09-10 · 5 obs
● 2016-12-06 17:09:04
● 2017-09-10 08:35:32
○ 2026-08-20 17:02:52
○ 2026-08-23 20:14:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net... | - |
| code-play.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for code-play.com (unsigned zone)
⏱️ Timing
Total: 636ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| TXT | 1 | dc816f3a-d35a-42d7-8391-353a84af8ccb |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
Name Servers
code-play.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
code-play.com has the same name server delegation as a number of other domains, such as openaiga.com, gwcbm2hz.top, globalpower.co and two more.
At least some of code-play.com's name servers are shared with other domains, for example tachingon.com and licasso.com.
Both launch1.spaceship.net and launch2.spaceship.net have two IP addresses each. launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26; launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.