`dragon-capital.net`

DNSSEC	⚠️ Not signed
A	54.215.31.113^{🇺🇸 Amazon54.215.0.0/17 EC2 SFO prefix}
		PTR	`ec2-54-215-31-113.us-west-1.compute.amazonaws.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@dragon-capital.net 2026-04-08 #2

`net`

	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.net`nstld@verisign-grs.com serial=1776156687

Same first word

dragon-capital.ua

dragon-capital.net

dragon-capital.com

dragon-capital.kiev.ua

DNS History

6 records (3 active, 3 former)

●NSns1.dyna-ns.net2026-03-30 → 2026-04-14 · 3 obs

○ 2017-04-03 06:43:02
● 2026-03-30 19:18:28
● 2026-04-14 09:14:50

○NSns1.dynadot.com2015-08-01 → 2017-04-03 · 4 obs

● 2015-08-01 01:46:22
● 2017-04-03 06:43:02
○ 2026-03-30 19:18:28
○ 2026-04-14 09:14:50

●NSns2.dyna-ns.net2026-03-30 → 2026-04-14 · 3 obs

○ 2017-04-03 06:43:02
● 2026-03-30 19:18:28
● 2026-04-14 09:14:50

○NSns2.dynadot.com2015-08-01 → 2017-04-03 · 4 obs

● 2015-08-01 01:46:22
● 2017-04-03 06:43:02
○ 2026-03-30 19:18:28
○ 2026-04-14 09:14:50

○A193.239.68.132015-08-01 → 2017-04-03 · 4 obs

● 2015-08-01 01:46:22
● 2017-04-03 06:43:02
○ 2026-03-30 19:18:28
○ 2026-04-14 09:14:50

●A54.215.31.1132026-03-30 → 2026-04-14 · 3 obs

○ 2017-04-03 06:43:02
● 2026-03-30 19:18:28
● 2026-04-14 09:14:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	i.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net...	-
dragon-capital.net	ns2.dyna-ns.net, ns1.dyna-ns.net	4 records

✅ Authoritative Response

Server:162.159.26.92

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dragon-capital.net (unsigned zone)

⏱️ Timing

Total: 249ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.215.31.113`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.dragon-capita`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns2.dyna-ns.net, ns2.dyna-ns.net, ns1.dyna-ns.net...)

Analysis

IP Addresses

dragon-capital.net points to a single IP address: 54.215.31.113.

Other host names such as santarosa.info, office-coffee.com, zarent.com, certificata.pro and sabachat.com share IP numbers with dragon-capital.net.

Name Servers

dragon-capital.net is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

dragon-capital.net uses the same name server setup as other domains, including preparemos.com, aedc4ac6a5bb8dd97777ae3faa9d54ce.xyz, toptenfeed.com, wggn.tv and dmoz114.com.

Host names with four IPs

ns1.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158

ns2.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5

dragon-capital.net - robtex.com