`warsawnights.com`

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@warsawnights.com 2026-03-28 #4

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

Same first word

warsawnights.com

DNS History

19 records (3 active, 16 former)

○NSns1.dsredirection.com2016-06-22 → 2016-06-22 · 3 obs

● 2016-06-22 06:10:30
○ 2017-02-20 02:28:42
○ 2026-04-26 13:57:04

●NSns1.dyna-ns.net2026-03-27 → 2026-04-26 · 3 obs

○ 2019-04-12 03:08:28
● 2026-03-27 09:42:10
● 2026-04-26 13:57:04

○NSns1.namebrightdns.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-06-22 06:10:30
● 2017-02-20 02:28:42
○ 2019-04-12 03:08:28
○ 2026-04-26 13:57:04

○NSns2.dsredirection.com2016-06-22 → 2016-06-22 · 3 obs

● 2016-06-22 06:10:30
○ 2017-02-20 02:28:42
○ 2026-04-26 13:57:04

●NSns2.dyna-ns.net2026-03-27 → 2026-04-26 · 3 obs

○ 2019-04-12 03:08:28
● 2026-03-27 09:42:10
● 2026-04-26 13:57:04

○NSns2.namebrightdns.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-06-22 06:10:30
● 2017-02-20 02:28:42
○ 2019-04-12 03:08:28
○ 2026-04-26 13:57:04

○NSnsg1.namebrightdns.com2019-04-12 → 2019-04-12 · 4 obs

○ 2017-02-20 02:28:42
● 2019-04-12 03:08:28
○ 2026-03-27 09:42:10
○ 2026-04-26 13:57:04

○NSnsg2.namebrightdns.com2019-04-12 → 2019-04-12 · 4 obs

○ 2017-02-20 02:28:42
● 2019-04-12 03:08:28
○ 2026-03-27 09:42:10
○ 2026-04-26 13:57:04

○MXmxs1.fides.com2015-06-29 → 2015-11-28 · 4 obs

● 2015-06-29 18:53:14
● 2015-11-28 14:33:50
○ 2016-06-22 06:10:30
○ 2026-04-26 13:57:04

○MXmxs2.fides.com2015-06-29 → 2015-11-28 · 4 obs

● 2015-06-29 18:53:14
● 2015-11-28 14:33:50
○ 2016-06-22 06:10:30
○ 2026-04-26 13:57:04

○A141.8.230.202016-06-22 → 2016-06-22 · 4 obs

○ 2015-11-28 14:33:50
● 2016-06-22 06:10:30
○ 2017-02-20 02:28:42
○ 2026-04-26 13:57:04

○A52.1.32.252017-02-20 → 2017-02-20 · 4 obs

○ 2016-06-22 06:10:30
● 2017-02-20 02:28:42
○ 2019-04-12 03:08:28
○ 2026-04-26 13:57:04

●A54.215.31.1132026-03-27 → 2026-04-26 · 3 obs

○ 2019-04-12 03:08:28
● 2026-03-27 09:42:10
● 2026-04-26 13:57:04

○A54.85.149.1352017-02-20 → 2017-02-20 · 4 obs

○ 2016-06-22 06:10:30
● 2017-02-20 02:28:42
○ 2019-04-12 03:08:28
○ 2026-04-26 13:57:04

○A64.20.39.1342015-06-29 → 2015-11-28 · 4 obs

● 2015-06-29 18:53:14
● 2015-11-28 14:33:50
○ 2016-06-22 06:10:30
○ 2026-04-26 13:57:04

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-06-22 06:10:30
● 2017-02-20 02:28:42
○ 2019-04-12 03:08:28
○ 2026-04-26 13:57:04

○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2019-04-12 → 2019-04-12 · 4 obs

○ 2017-02-20 02:28:42
● 2019-04-12 03:08:28
○ 2026-03-27 09:42:10
○ 2026-04-26 13:57:04

○CNAMEpres.serverhome.com2016-06-22 → 2016-06-22 · 3 obs

● 2016-06-22 06:10:30
○ 2017-02-20 02:28:42
○ 2026-04-26 13:57:04

○CNAMEthie5ku9.dsgeneration.com2016-06-22 → 2016-06-22 · 3 obs

● 2016-06-22 06:10:30
○ 2017-02-20 02:28:42
○ 2026-04-26 13:57:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, e.gtld-servers.net, g.gtld-servers.net, c.gtld-servers.net...	-
warsawnights.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.27.158

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for warsawnights.com (unsigned zone)

⏱️ Timing

Total: 714ms | 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.warsawnights.`

Analysis

IP Addresses

warsawnights.com resolves to a single IP: 54.215.31.113.

Other host names, for instance pcgames.in, dragon-capital.net, usloanaid.com, youthpadel.com and huo.be share IP numbers with warsawnights.com.

Name Servers

warsawnights.com has two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

warsawnights.com shares the same name server setup as other domains, for example dragonia-casino-777.fr, kingofvalue.com, shuswapbuilder.com, coure.com and rapid.im.

Host names with four IP numbers:

ns1.dyna-ns.net has four IPs: 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 has four IPs: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5.

warsawnights.com - robtex.com