blue-tokyo.com - robtex.com
blue-tokyo.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 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1778736314 | ||||||
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=1778764056 | ||||||
Same first word
blue-tokyo.com |
DNS History
8 records (4 active, 4 former)
●NSlaunch1.spaceship.net2026-04-09 → 2026-05-14 · 3 obs
● 2026-04-09 05:27:16
● 2026-05-14 13:17:50
●NSlaunch2.spaceship.net2026-04-09 → 2026-05-14 · 3 obs
● 2026-04-09 05:27:16
● 2026-05-14 13:17:50
○NSnt1.bluesingapore.com2007-08-22 → 2007-08-22 · 3 obs
○ 2015-10-25 10:08:04
○ 2026-05-14 13:17:50
○NSnt2.bluesingapore.com2007-08-22 → 2007-08-22 · 3 obs
○ 2015-10-25 10:08:04
○ 2026-05-14 13:17:50
○MXmail.bluesingapore.com2007-08-22 → 2007-08-22 · 3 obs
○ 2015-10-25 10:08:04
○ 2026-05-14 13:17:50
○MXsapphire.bluesingapore.com2007-08-22 → 2007-08-22 · 3 obs
○ 2015-10-25 10:08:04
○ 2026-05-14 13:17:50
●A44.232.173.2492026-04-09 → 2026-05-14 · 2 obs
● 2026-05-14 13:17:50
●A52.40.42.1132026-04-09 → 2026-05-14 · 2 obs
● 2026-05-14 13:17:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, b.gtld-servers.net, j.gtld-servers.net, c.gtld-servers.net... | - |
| blue-tokyo.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for blue-tokyo.com (unsigned zone)
⏱️ Timing
Total: 715ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | 0b6bbca5-c9e0-49d2-8366-c2349fe81d88 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
blue-tokyo.com points to two IP numbers: 44.232.173.249 and 52.40.42.113.
Other host names, for instance numfi.com, cableai.com, sanfranciscomarket.com, ecivi.com and 662.me share IP numbers with blue-tokyo.com.
Name Servers
blue-tokyo.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
blue-tokyo.com uses the same name server setup as other domains, for instance metaactors.com, vesound.com, wifi.study, uoj.se and farnuvo.store.
blue-tokyo.com partially shares name servers with other domains, for instance getitmyself.com.
Host names with two IP numbers:
The host launch1.spaceship.net points to 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38.
The host launch2.spaceship.net points to 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32.