`kellerluxury.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@kellerluxury.com 2026-03-13 #2

`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=1774975112

Same first word

kellerluxury.com

DNS History

17 records (3 active, 14 former)

○NSns.123-reg.co.uk2015-10-23 → 2016-11-19 · 5 obs

○ 2008-03-11 10:06:04
● 2015-10-23 09:26:30
● 2016-11-19 14:23:00
○ 2017-10-30 05:02:54
○ 2026-03-31 16:52:32

○NSns1.domainha(0x736578)pired.com2017-10-30 → 2017-10-30 · 4 obs

○ 2016-11-19 14:23:00
● 2017-10-30 05:02:54
○ 2026-03-05 18:35:38
○ 2026-03-31 16:52:32

●NSns1.dyna-ns.net2026-03-05 → 2026-03-31 · 3 obs

○ 2017-10-30 05:02:54
● 2026-03-05 18:35:38
● 2026-03-31 16:52:32

○NSns2.123-reg.co.uk2015-10-23 → 2016-11-19 · 5 obs

○ 2008-03-11 10:06:04
● 2015-10-23 09:26:30
● 2016-11-19 14:23:00
○ 2017-10-30 05:02:54
○ 2026-03-31 16:52:32

○NSns2.domainha(0x736578)pired.com2017-10-30 → 2017-10-30 · 4 obs

○ 2016-11-19 14:23:00
● 2017-10-30 05:02:54
○ 2026-03-05 18:35:38
○ 2026-03-31 16:52:32

●NSns2.dyna-ns.net2026-03-05 → 2026-03-31 · 3 obs

○ 2017-10-30 05:02:54
● 2026-03-05 18:35:38
● 2026-03-31 16:52:32

○NSns31.domaincontrol.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 10:06:04
○ 2015-10-23 09:26:30
○ 2026-03-31 16:52:32

○NSns32.domaincontrol.com2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 10:06:04
○ 2015-10-23 09:26:30
○ 2026-03-31 16:52:32

○MXmail.b-io.co2017-10-30 → 2017-10-30 · 4 obs

○ 2016-11-19 14:23:00
● 2017-10-30 05:02:54
○ 2026-03-05 18:35:38
○ 2026-03-31 16:52:32

○MXmailstore1.secureserver.net2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 10:06:04
○ 2015-10-23 09:26:30
○ 2026-03-31 16:52:32

○MXmx0.123-reg.co.uk2015-10-23 → 2016-11-19 · 5 obs

○ 2008-03-11 10:06:04
● 2015-10-23 09:26:30
● 2016-11-19 14:23:00
○ 2017-10-30 05:02:54
○ 2026-03-31 16:52:32

○MXmx1.123-reg.co.uk2015-10-23 → 2016-11-19 · 5 obs

○ 2008-03-11 10:06:04
● 2015-10-23 09:26:30
● 2016-11-19 14:23:00
○ 2017-10-30 05:02:54
○ 2026-03-31 16:52:32

○MXsmtp.secureserver.net2008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 10:06:04
○ 2015-10-23 09:26:30
○ 2026-03-31 16:52:32

○A109.68.33.642017-10-30 → 2017-10-30 · 4 obs

○ 2016-11-19 14:23:00
● 2017-10-30 05:02:54
○ 2026-03-05 18:35:38
○ 2026-03-31 16:52:32

●A54.215.31.1132026-03-05 → 2026-03-31 · 3 obs

○ 2017-10-30 05:02:54
● 2026-03-05 18:35:38
● 2026-03-31 16:52:32

○A68.178.232.1002008-03-11 → 2008-03-11 · 3 obs

● 2008-03-11 10:06:04
○ 2015-10-23 09:26:30
○ 2026-03-31 16:52:32

○A81.21.76.622015-10-23 → 2016-11-19 · 5 obs

○ 2008-03-11 10:06:04
● 2015-10-23 09:26:30
● 2016-11-19 14:23:00
○ 2026-03-05 18:35:38
○ 2026-03-31 16:52:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
kellerluxury.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.25.5

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for kellerluxury.com (unsigned zone)

⏱️ Timing

Total: 241ms | Queries: -

📄 Records

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

Analysis

IP Addresses

kellerluxury.com resolves to one IP number: 54.215.31.113.

Other host names, for instance kha.in, stents.co, 2cal.com, lasix24.top and s-b.in share IP numbers with kellerluxury.com.

Name Servers

kellerluxury.com's delegation uses two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

kellerluxury.com uses the same name server setup as other domains, such as slotgroup954.de, gentiles.org, delectableoccasions.com, ceomedia.net and bau-software.com.

Host names with four IP numbers:

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

kellerluxury.com - robtex.com