close.team - dns.ninja
close.team
| 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 | 24c862bc-661f-404a-b529-c8ea36608067 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1785510669 | ||||||
team
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.nic.team ⭐ | ||||||
| NS | v0n1.nic.team | ||||||
| NS | v0n2.nic.team | ||||||
| NS | v0n3.nic.team | ||||||
| NS | v2n0.nic.team | ||||||
| NS | v2n1.nic.team | ||||||
| SOA | v0n0.nic.teamhostmaster@donuts.email serial=1786413724 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSlaunch1.spaceship.net2026-05-13 → 2026-08-11 · 2 obs
● 2026-08-11 03:00:42
●NSlaunch2.spaceship.net2026-05-13 → 2026-08-11 · 2 obs
● 2026-08-11 03:00:42
●A44.232.173.2492026-05-13 → 2026-08-11 · 3 obs
○ 2026-08-10 12:39:22
● 2026-08-11 03:00:42
●A52.40.42.1132026-05-13 → 2026-08-11 · 3 obs
○ 2026-08-10 12:39:22
● 2026-08-11 03:00:42
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| team | v2n1.nic.team, v2n0.nic.team, v0n3.nic.team, v0n0.nic.team... | 12 records |
| close.team | launch1.spaceship.net, launch2.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch1.spaceship.net, launch2.spaceship.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for close.team (unsigned zone)
⏱️ Timing
Total: 290ms | 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 | 24c862bc-661f-404a-b529-c8ea36608067 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v0n0.nic.team, v0n1.nic.team, v0n2.nic.team...)
Analysis
IP Addresses
close.team points to the IP addresses 44.232.173.249 and 52.40.42.113
maclasa.com, hsbcsec.com, kvk.co and two other host names share IP numbers with close.team.
Name Servers
DNS delegation for close.team points to two name servers: launch1.spaceship.net and launch2.spaceship.net.
close.team uses the same name servers as several other domains — among them cat-460.casino, mybisnesonline.com, leboncoin.xyz and two more.
close.team has partial name server overlap with other domains, including bodyfitnesscenter.com.
launch1.spaceship.net directs to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. launch2.spaceship.net directs to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20. Each host name carries two IP addresses.