hashcode.in - dns.ninja
hashcode.in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| 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 | 6i0dm4pzrbk8j1srvkxsk8ow84f77rur73usf6to | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1774371152 | ||||||
in
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns1.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| NS | ns2.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns3.registry.in ⚠️ Not in parent delegation | ||||||
| NS | ns4.registry.in ⚠️ Not in parent delegation | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1781112060 | ||||||
Same first word
hashcode.com.au |
hashcode.org |
hashcode.de |
hashcode.com |
hashcode.co |
hashcode.my |
hashcode.com.my |
hashcode.withgoogle.com |
hashcode.ru |
hashcode.co.kr |
hashcode.biz |
hashcode.in |
hashcode.fr |
hashcode.eu |
Similar names
codehash.net |
dashecho.co.uk |
ochedash.com |
dashecho.com |
dashohec.de |
echodash.com |
codehash.com |
shahcode.com |
sdchehao.com |
DNS History
11 records (2 active, 9 former)
●NSlaunch1.spaceship.net2026-03-25 → 2026-06-10 · 3 obs
○ 2026-02-16 16:18:20
● 2026-03-25 12:42:10
● 2026-06-10 17:56:50
● 2026-03-25 12:42:10
● 2026-06-10 17:56:50
●NSlaunch2.spaceship.net2026-03-25 → 2026-06-10 · 3 obs
○ 2026-02-16 16:18:20
● 2026-03-25 12:42:10
● 2026-06-10 17:56:50
● 2026-03-25 12:42:10
● 2026-06-10 17:56:50
○NSns1.dns-expired.com2026-02-16 → 2026-02-16 · 4 obs
○ 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○NSns11.domaincontrol.com2015-06-29 → 2026-02-16 · 4 obs
● 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○NSns12.domaincontrol.com2015-06-29 → 2026-02-16 · 4 obs
● 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○NSns2.dns-expired.com2026-02-16 → 2026-02-16 · 4 obs
○ 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○MXmailstore1.secureserver.net2015-06-29 → 2026-02-16 · 4 obs
● 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○MXsmtp.secureserver.net2015-06-29 → 2026-02-16 · 4 obs
● 2015-06-29 11:57:10
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○A34.102.136.1802021-10-21 → 2026-02-16 · 5 obs
○ 2020-03-07 11:41:16
● 2021-10-21 04:42:32
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2021-10-21 04:42:32
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
○A50.63.202.422015-06-29 → 2020-03-07 · 4 obs
● 2015-06-29 11:57:10
● 2020-03-07 11:41:16
○ 2021-10-21 04:42:32
○ 2026-06-10 17:56:50
● 2020-03-07 11:41:16
○ 2021-10-21 04:42:32
○ 2026-06-10 17:56:50
○A84.32.84.332026-02-16 → 2026-02-16 · 4 obs
○ 2021-10-21 04:42:32
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
● 2026-02-16 16:18:20
○ 2026-03-25 12:42:10
○ 2026-06-10 17:56:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| in | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| hashcode.in | launch1.spaceship.net, launch2.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch1.spaceship.net, launch2.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 871ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 6i0dm4pzrbk8j1srvkxsk8ow84f77rur73usf6to |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
Name Servers
hashcode.in uses two name servers for its delegation: launch1.spaceship.net and launch2.spaceship.net.
hashcode.in has the same name server delegation as a number of other domains, such as qmail.se, watches-store.shop, dqcf.com and two more.
At least some of hashcode.in's name servers are also used by other domains, among them ematch.org.
The two host names launch1.spaceship.net and launch2.spaceship.net each have a pair of IP addresses: launch1.spaceship.net has 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net has 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.