forgeverse.com - dns.ninja
forgeverse.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 | ||||||
| TXT | 48f5c545-e961-4c0f-ba99-f9e4f00d59fd | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783154838 | ||||||
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=1785096242 | ||||||
Same first word
forgeverse.com |
Similar names
DNS History
7 records (4 active, 3 former)
●NSlaunch1.spaceship.net2026-05-24 → 2026-07-26 · 3 obs
● 2026-05-24 10:58:54
● 2026-07-26 20:24:54
●NSlaunch2.spaceship.net2026-05-24 → 2026-07-26 · 3 obs
● 2026-05-24 10:58:54
● 2026-07-26 20:24:54
○NSns1.doghorn.arvixe.com2016-12-13 → 2016-12-13 · 3 obs
○ 2017-08-18 08:24:28
○ 2026-07-26 20:24:54
○NSns2.doghorn.arvixe.com2016-12-13 → 2016-12-13 · 3 obs
○ 2017-08-18 08:24:28
○ 2026-07-26 20:24:54
○A143.95.252.452016-12-13 → 2016-12-13 · 3 obs
○ 2017-08-18 08:24:28
○ 2026-07-26 20:24:54
●A44.232.173.2492026-05-24 → 2026-07-26 · 3 obs
● 2026-05-24 10:58:54
● 2026-07-26 20:24:54
●A52.40.42.1132026-05-24 → 2026-07-26 · 3 obs
● 2026-05-24 10:58:54
● 2026-07-26 20:24:54
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| forgeverse.com | 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 forgeverse.com (unsigned zone)
⏱️ Timing
Total: 647ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
forgeverse.com resolves to the IP addresses 44.232.173.249 and 52.40.42.113
worldswap.fun, rayhen.com, lwm.ca plus two other host names have IP numbers in common with forgeverse.com.
Name Servers
forgeverse.com has two authoritative name servers — launch1.spaceship.net and launch2.spaceship.net.
The name server configuration of forgeverse.com is shared with other domains, for instance braskolir.top, pinterestpay.com, schulung.co and two others.
The name servers for forgeverse.com overlap at least partially with those of other domains — for example neoextracts.com.
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.