dragonware.com - dns.ninja
dragonware.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 | adaf1352-fe7f-4dd7-8680-044394b38257 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783692107 | ||||||
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=1785497422 | ||||||
Same first word
dragonware.fr |
dragonware.com |
dragonware.ch |
dragonware.eu |
Similar names
DNS History
20 records (4 active, 16 former)
○NSdns010.d.register.com2015-08-22 → 2017-02-16 · 4 obs
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○NSdns020.a.register.com2015-08-22 → 2017-02-16 · 4 obs
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○NSdns036.c.register.com2015-08-22 → 2017-02-16 · 4 obs
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○NSdns086.b.register.com2015-08-22 → 2017-02-16 · 4 obs
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
●NSlaunch1.spaceship.net2026-03-23 → 2026-07-31 · 5 obs
● 2026-03-23 11:48:56
● 2026-04-08 09:11:20
○ 2026-07-01 09:16:04
● 2026-07-31 11:45:30
●NSlaunch2.spaceship.net2026-03-23 → 2026-07-31 · 5 obs
● 2026-03-23 11:48:56
● 2026-04-08 09:11:20
○ 2026-07-01 09:16:04
● 2026-07-31 11:45:30
○NSns1.atom.com2026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:16:04
○ 2026-07-31 11:45:30
○NSns2.atom.com2026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:16:04
○ 2026-07-31 11:45:30
○NSsk.s5.ans1.ns121.ztomy.com2020-02-12 → 2020-02-12 · 4 obs
● 2020-02-12 15:50:52
○ 2026-03-23 11:48:56
○ 2026-07-31 11:45:30
○NSsk.s5.ans2.ns121.ztomy.com2020-02-12 → 2020-02-12 · 4 obs
● 2020-02-12 15:50:52
○ 2026-03-23 11:48:56
○ 2026-07-31 11:45:30
○MXmailserver.dragonware.com2015-08-22 → 2015-08-22 · 3 obs
○ 2015-12-10 15:06:42
○ 2026-07-31 11:45:30
○MXmailstore1.secureserver.net2015-12-10 → 2017-02-16 · 5 obs
● 2015-12-10 15:06:42
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○MXsmtp.secureserver.net2015-12-10 → 2017-02-16 · 5 obs
● 2015-12-10 15:06:42
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○A107.180.36.1022015-12-10 → 2017-02-16 · 5 obs
● 2015-12-10 15:06:42
● 2017-02-16 04:01:18
○ 2020-02-12 15:50:52
○ 2026-07-31 11:45:30
○A208.91.197.392020-02-12 → 2020-02-12 · 4 obs
● 2020-02-12 15:50:52
○ 2026-03-23 11:48:56
○ 2026-07-31 11:45:30
○A24.199.229.1702015-08-22 → 2015-08-22 · 3 obs
○ 2015-12-10 15:06:42
○ 2026-07-31 11:45:30
●A44.232.173.2492026-03-23 → 2026-07-31 · 5 obs
● 2026-03-23 11:48:56
● 2026-04-08 09:11:20
○ 2026-07-01 09:16:04
● 2026-07-31 11:45:30
○A52.20.84.622026-07-01 → 2026-07-01 · 3 obs
● 2026-07-01 09:16:04
○ 2026-07-31 11:45:30
●A52.40.42.1132026-03-23 → 2026-07-31 · 5 obs
● 2026-03-23 11:48:56
● 2026-04-08 09:11:20
○ 2026-07-01 09:16:04
● 2026-07-31 11:45:30
○PTRsk.s5.ans1.ns121.ztomy.com2020-02-12 → 2020-02-12 · 3 obs
○ 2026-03-23 11:48:56
○ 2026-07-31 11:45:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| dragonware.com | 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 dragonware.com (unsigned zone)
⏱️ Timing
Total: 396ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 44.232.173.249, 52.40.42.113 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | adaf1352-fe7f-4dd7-8680-044394b38257 |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
dragonware.com has two IP addresses: 44.232.173.249 and 52.40.42.113
Additional host names — provenz.com, linkwall.com, shifty.xyz and two others — share IP numbers with dragonware.com.
Name Servers
dragonware.com is served by two delegated name servers, launch1.spaceship.net and launch2.spaceship.net.
dragonware.com shares its name server setup with other domains, including minasofie.com, eoyuncu.com, kentuckyev.com and two others.
The name servers for dragonware.com overlap at least in part with those of other domains, including vaylora.com and rilati.com.
Each of the two host names carries two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.