hypercurrent.com - dns.ninja
hypercurrent.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=1790256720 | ||||||
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=1790673809 | ||||||
Same first word
hypercurrent.io |
hypercurrent.com |
hypercurrent.xyz |
hypercurrent.live |
Similar names
Previous names
Next names
DNS History
5 records (4 active, 1 former)
●NSlaunch1.spaceship.net2026-09-14 → 2026-09-29 · 2 obs
● 2026-09-29 09:40:36
●NSlaunch2.spaceship.net2026-09-14 → 2026-09-29 · 2 obs
● 2026-09-29 09:40:36
●A44.232.173.2492026-09-14 → 2026-09-29 · 3 obs
● 2026-09-14 20:06:38
● 2026-09-29 09:40:36
●A52.40.42.1132026-09-14 → 2026-09-29 · 3 obs
● 2026-09-14 20:06:38
● 2026-09-29 09:40:36
○A54.183.99.632016-12-19 → 2018-01-25 · 4 obs
● 2018-01-25 11:56:40
○ 2026-09-14 20:06:38
○ 2026-09-29 09:40:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, m.gtld-servers.net... | - |
| hypercurrent.com | launch2.spaceship.net, launch1.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch2.spaceship.net, launch1.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1592ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
hypercurrent.com points to the IP addresses 44.232.173.249 and 52.40.42.113
Two other host names, along with mindshare.ai, studio2go.com and assame.com, also share IP numbers with hypercurrent.com.
Name Servers
hypercurrent.com is delegated to two name servers: launch1.spaceship.net and launch2.spaceship.net.
hypercurrent.com shares its NS records with other domains, for example concretehemet.com, fspbbe.top, personalgivingidentity.com and two others.
hypercurrent.com shares at least some of its name servers with other domains, such as yamadakun.com.
launch1.spaceship.net and launch2.spaceship.net each resolve to two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, while launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.