codingto.com - dns.ninja
codingto.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| 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 | e6d220b3-fedb-4522-b203-3627f07dfec2 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1781835276 | ||||||
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=1785521622 | ||||||
Same first word
codingto.com |
Similar names
DNS History
18 records (4 active, 14 former)
○NSdns1.name-services.com2017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
○NSdns2.name-services.com2017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
○NSdns3.name-services.com2017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
○NSdns4.name-services.com2017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
○NSdns5.name-services.com2017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
●NSlaunch1.spaceship.net2026-03-20 → 2026-07-31 · 7 obs
● 2026-03-20 17:56:44
● 2026-03-23 13:50:08
○ 2026-04-09 17:53:20
● 2026-05-03 07:05:14
○ 2026-06-10 04:52:58
● 2026-07-31 18:39:52
●NSlaunch2.spaceship.net2026-03-20 → 2026-07-31 · 7 obs
● 2026-03-20 17:56:44
● 2026-03-23 13:50:08
○ 2026-04-09 17:53:20
● 2026-05-03 07:05:14
○ 2026-06-10 04:52:58
● 2026-07-31 18:39:52
○NSns1.afternic.com2026-04-09 → 2026-06-10 · 5 obs
● 2026-04-09 17:53:20
○ 2026-05-03 07:05:14
● 2026-06-10 04:52:58
○ 2026-07-31 18:39:52
○NSns1.simplyms.com2016-12-17 → 2016-12-17 · 3 obs
○ 2017-10-27 18:33:28
○ 2026-07-31 18:39:52
○NSns2.afternic.com2026-04-09 → 2026-06-10 · 5 obs
● 2026-04-09 17:53:20
○ 2026-05-03 07:05:14
● 2026-06-10 04:52:58
○ 2026-07-31 18:39:52
○NSns2.simplyms.com2016-12-17 → 2016-12-17 · 3 obs
○ 2017-10-27 18:33:28
○ 2026-07-31 18:39:52
○MXmail.codingto.com2016-12-17 → 2016-12-17 · 3 obs
○ 2017-10-27 18:33:28
○ 2026-07-31 18:39:52
○A13.248.169.482026-04-09 → 2026-06-10 · 5 obs
● 2026-04-09 17:53:20
○ 2026-05-03 07:05:14
● 2026-06-10 04:52:58
○ 2026-07-31 18:39:52
●A44.232.173.2492026-03-20 → 2026-07-31 · 7 obs
● 2026-03-20 17:56:44
● 2026-03-23 13:50:08
○ 2026-04-09 17:53:20
● 2026-05-03 07:05:14
○ 2026-06-10 04:52:58
● 2026-07-31 18:39:52
●A52.40.42.1132026-03-20 → 2026-07-31 · 7 obs
● 2026-03-20 17:56:44
● 2026-03-23 13:50:08
○ 2026-04-09 17:53:20
● 2026-05-03 07:05:14
○ 2026-06-10 04:52:58
● 2026-07-31 18:39:52
○A69.64.147.372017-10-27 → 2017-10-27 · 4 obs
● 2017-10-27 18:33:28
○ 2026-03-20 17:56:44
○ 2026-07-31 18:39:52
○A76.223.54.1462026-04-09 → 2026-06-10 · 5 obs
● 2026-04-09 17:53:20
○ 2026-05-03 07:05:14
● 2026-06-10 04:52:58
○ 2026-07-31 18:39:52
○A88.151.130.742016-12-17 → 2016-12-17 · 3 obs
○ 2017-10-27 18:33:28
○ 2026-07-31 18:39:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net... | - |
| codingto.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 codingto.com (unsigned zone)
⏱️ Timing
Total: 344ms | 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 | e6d220b3-fedb-4522-b203-3627f07dfec2 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
codingto.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Among the host names that share IP numbers with codingto.com are adelco.net, 01us.com, sasca.net and two others.
Name Servers
The NS records for codingto.com delegate to launch1.spaceship.net and launch2.spaceship.net.
codingto.com has the same name server delegation as a number of other domains, such as casino-champion-slots.buzz, iii.company, rkusd.com and two more.
There is an overlap in name servers between codingto.com and other domains, for example bahisseningiris.com, thewhitepine.com and moonshiesty.com
These name servers are routinely deployed together with the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.