close.team - robtex.com
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=1775147363 | ||||||
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=1778803352 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSlaunch1.spaceship.net2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 00:07:38
●NSlaunch2.spaceship.net2026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 00:07:38
●A44.232.173.2492026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 00:07:38
●A52.40.42.1132026-05-13 → 2026-05-15 · 2 obs
● 2026-05-15 00:07:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| team | v0n0.nic.team, v0n1.nic.team, v0n2.nic.team, v0n3.nic.team... | 12 records |
| close.team | 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 close.team (unsigned zone)
⏱️ Timing
Total: 1388ms | 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 | 24c862bc-661f-404a-b529-c8ea36608067 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v0n0.nic.team, v0n0.nic.team, v0n1.nic.team...)
Analysis
IP Addresses
close.team resolves to two IP numbers: 44.232.173.249 and 52.40.42.113.
other host names including hsbcsec.com, kvk.co, hostcontrols.com, getmobile.co.uk and robomate.net share IP numbers with close.team.
Name Servers
close.team is delegated to two name servers launch1.spaceship.net and launch2.spaceship.net.
close.team shares the same name server setup as other domains, for instance 1stlondonescorts.com, travelaos.com, servicemarketing.co.uk, ayiq.com and gmgb.com.
Host names with two IP numbers:
The host name launch1.spaceship.net points to 2400:cb00:2049:1::a29f:1a26 and 162.159.26.38; the host name launch2.spaceship.net points to 2400:cb00:2049:1::a29f:1b20 and 162.159.27.32.