hyperrail.com - dns.ninja
hyperrail.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 | ab287b56-cc6a-4670-9f21-a6dfcba3ef4f | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783984327 | ||||||
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=1785486847 | ||||||
Same first word
hyperrail.com |
DNS History
10 records (4 active, 6 former)
○NSbuy.internettraffic.com2015-07-08 → 2016-05-09 · 4 obs
● 2016-05-09 03:06:42
○ 2017-02-13 23:39:42
○ 2026-07-31 08:38:54
●NSlaunch1.spaceship.net2026-04-04 → 2026-07-31 · 3 obs
● 2026-04-04 16:17:58
● 2026-07-31 08:38:54
●NSlaunch2.spaceship.net2026-04-04 → 2026-07-31 · 3 obs
● 2026-04-04 16:17:58
● 2026-07-31 08:38:54
○NSns1.uniregistrymarket.link2017-02-13 → 2017-02-13 · 4 obs
● 2017-02-13 23:39:42
○ 2026-04-04 16:17:58
○ 2026-07-31 08:38:54
○NSns2.uniregistrymarket.link2017-02-13 → 2017-02-13 · 4 obs
● 2017-02-13 23:39:42
○ 2026-04-04 16:17:58
○ 2026-07-31 08:38:54
○NSsell.internettraffic.com2015-07-08 → 2016-05-09 · 4 obs
● 2016-05-09 03:06:42
○ 2017-02-13 23:39:42
○ 2026-07-31 08:38:54
●A44.232.173.2492026-04-04 → 2026-07-31 · 3 obs
● 2026-04-04 16:17:58
● 2026-07-31 08:38:54
●A52.40.42.1132026-04-04 → 2026-07-31 · 3 obs
● 2026-04-04 16:17:58
● 2026-07-31 08:38:54
○A69.172.201.1532016-05-09 → 2017-02-13 · 5 obs
● 2016-05-09 03:06:42
● 2017-02-13 23:39:42
○ 2026-04-04 16:17:58
○ 2026-07-31 08:38:54
○A69.172.201.2082015-07-08 → 2016-02-12 · 4 obs
● 2016-02-12 12:45:34
○ 2016-05-09 03:06:42
○ 2026-07-31 08:38:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| hyperrail.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 hyperrail.com (unsigned zone)
⏱️ Timing
Total: 241ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | ab287b56-cc6a-4670-9f21-a6dfcba3ef4f |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
hyperrail.com points to the IP addresses 44.232.173.249 and 52.40.42.113
Additional host names — status.digital, coozone.com, bycut.com and two others — share IP numbers with hyperrail.com.
Name Servers
hyperrail.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
hyperrail.com shares its name server setup with other domains, including glitterin.com, nanoniche.com, byscan.com and two others.
The name servers for hyperrail.com overlap at least partially with those of other domains — for example turtlepondfarm.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.