jaydenhess.com - dns.ninja

`jaydenhess.com`

DNSSEC	⚠️ Not signed
A	2001:19f0:5c01:1061:5400:4ff:fed4:af1^{🇺🇸 AS-VULTR2001:19f0:5c00::/38 Vultr Assigned Prefix}
A	66.42.113.147^{🇺🇸 AS-VULTR66.42.112.0/20 Vultr Assigned Prefix}
NS	`ns1.vultr.com` ⭐
		A	2001:19f0:ccc::1^{🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1}
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns1.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns2.wpdns.host`
		A	2001:19f0:ccd::2^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns2.vultr.com`
		A	173.199.96.97^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns2.vultrusercontent.com`
NS	`ns3.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
SOA	`ns1.vultr.com`dnsadm@choopa.com serial=0

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

Same first word

jaydenhess.com

DNS History

17 records (6 active, 11 former)

●NSns1.vultr.com2026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

●NSns1.wpdns.host2026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

●NSns2.wpdns.host2026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

●NSns3.wpdns.host2026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

○NSrs122.registrar-servers.com2015-07-20 → 2016-06-20 · 4 obs

● 2015-07-20 10:20:18
● 2016-06-20 11:06:42
○ 2017-05-25 00:40:00
○ 2026-07-14 00:48:42

○NSrs150.registrar-servers.com2017-05-25 → 2017-05-25 · 4 obs

○ 2016-06-20 11:06:42
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○NSrs22.registrar-servers.com2015-07-20 → 2016-06-20 · 4 obs

● 2015-07-20 10:20:18
● 2016-06-20 11:06:42
○ 2017-05-25 00:40:00
○ 2026-07-14 00:48:42

○NSrs50.registrar-servers.com2017-05-25 → 2017-05-25 · 4 obs

○ 2016-06-20 11:06:42
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○MXalt1.aspmx.l.google.com2015-07-20 → 2017-05-25 · 4 obs

● 2015-07-20 10:20:18
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○MXalt2.aspmx.l.google.com2015-07-20 → 2017-05-25 · 4 obs

● 2015-07-20 10:20:18
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○MXaspmx.l.google.com2015-07-20 → 2017-05-25 · 4 obs

● 2015-07-20 10:20:18
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○MXaspmx2.googlemail.com2015-07-20 → 2017-05-25 · 4 obs

● 2015-07-20 10:20:18
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○MXaspmx3.googlemail.com2015-07-20 → 2017-05-25 · 4 obs

● 2015-07-20 10:20:18
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

○A162.213.249.1082015-07-20 → 2016-06-20 · 4 obs

● 2015-07-20 10:20:18
● 2016-06-20 11:06:42
○ 2017-05-25 00:40:00
○ 2026-07-14 00:48:42

○A198.54.116.622017-05-25 → 2017-05-25 · 4 obs

○ 2016-06-20 11:06:42
● 2017-05-25 00:40:00
○ 2026-03-01 08:33:56
○ 2026-07-14 00:48:42

●A2001:19f0:5c01:1061:5400:4ff:fed4:af12026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

●A66.42.113.1472026-03-01 → 2026-07-14 · 3 obs

○ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-07-14 00:48:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, b.gtld-servers.net...	-
jaydenhess.com	ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host	-

✅ Authoritative Response

Server:173.199.96.96

NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jaydenhess.com (unsigned zone)

⏱️ Timing

Total: 767ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.42.113.147`
AAAA	1	`2001:19f0:5c01:1061:5400:4ff:fed4:af1`
NS	3	`ns1.wpdns.host, ns2.wpdns.host...`
SOA	1	`ns1.vultr.com dnsadm.choopa.com`

Analysis

IP Addresses

jaydenhess.com points to the IP addresses 66.42.113.147 and 2001:19f0:5c01:1061:5400:4ff:fed4:af1

Other hosts including ashleyhess.com, mysite-coach.tempurl.host and www.ashleyhess.com share IP addresses with jaydenhess.com.

Name Servers

jaydenhess.com has four authoritative name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

At least some of jaydenhess.com's name servers are shared with other domains, for example pennedcon.com, yekooche.com, johnbolton.info and two more.

These name servers tend to be used in conjunction with the name servers ns2.vultr.com.

Host names with three IP numbers:

The hostname ns1.vultr.com directs to 173.199.96.96, 2001:19f0:ccc::1 and 2001:19f0:ccd::1.

Host names with two IP numbers:

ns1.wpdns.host directs traffic to 173.199.96.96 and 2001:19f0:ccd::1.

ns2.wpdns.host directs traffic to 173.199.96.97 and 2001:19f0:ccd::2.

ns3.wpdns.host directs traffic to 173.199.96.96 and 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 173.199.96.96.