insign.cloud - dns.ninja
insign.cloud
| 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 | 2f34d0e2-eb3c-4f02-9ee3-b5bb965855ad | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783831562 | ||||||
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1785170729 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSlaunch1.spaceship.net2026-05-24 → 2026-07-27 · 2 obs
● 2026-07-27 17:32:42
●NSlaunch2.spaceship.net2026-05-24 → 2026-07-27 · 2 obs
● 2026-07-27 17:32:42
●A44.232.173.2492026-05-24 → 2026-07-27 · 2 obs
● 2026-07-27 17:32:42
●A52.40.42.1132026-05-24 → 2026-07-27 · 2 obs
● 2026-07-27 17:32:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| insign.cloud | 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 insign.cloud (unsigned zone)
⏱️ Timing
Total: 460ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch1.spaceship.net, launch2.spaceship.net |
| TXT | 1 | 2f34d0e2-eb3c-4f02-9ee3-b5bb965855ad |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
insign.cloud has two IP addresses: 44.232.173.249 and 52.40.42.113
wnetc.com, dexcel.net, trainmart.com and two other host names share IP numbers with insign.cloud.
Name Servers
insign.cloud has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
insign.cloud uses the same name servers as several other domains — among them caveduck.com, waxiu.vip, hzchem.com and two more.
The name servers for insign.cloud are partially shared with other domains like oidelivers.com, dxsheng.com and 7auctions.com
These name servers are routinely deployed together with the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.
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.