jaydenhess.com - robtex.com

jaydenhess.com

DNSSEC⚠️ Not signed
A2001:19f0:5c01:1061:5400:4ff:fed4:af1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:5c00::/38 Vultr Assigned Prefix
A66.42.113.147πŸ‡ΊπŸ‡Έ AS-VULTR66.42.112.0/20 Vultr Assigned Prefix
NSns1.vultr.com ⭐
A2001:19f0:ccc::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccc::/48 DNS1
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns1.wpdns.host
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns2.wpdns.host
A2001:19f0:ccd::2πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns2.vultr.com
A173.199.96.97πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns2.vultrusercontent.com
NSns3.wpdns.host
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
SOAns1.vultr.comdnsadm@choopa.com serial=0

com

Same first word

DNS History

17 records (6 active, 11 former)

20162017201820192020202120222023202420252026NSns1.vultr.comns1.wpdns.hostns2.wpdns.hostns3.wpdns.hostrs122.registrar-servers.comrs150.registrar-servers.comrs22.registrar-servers.comrs50.registrar-servers.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA2001:19f0:5c01:1061:5400:4ff:fed4:af166.42.113.147162.213.249.108198.54.116.62
●NSns1.vultr.com2026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28
●NSns1.wpdns.host2026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28
●NSns2.wpdns.host2026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28
●NSns3.wpdns.host2026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
β—‹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-04-24 17:15:28
●A2001:19f0:5c01:1061:5400:4ff:fed4:af12026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28
●A66.42.113.1472026-03-01 β†’ 2026-04-24 Β· 3 obs
β—‹ 2017-05-25 00:40:00
● 2026-03-01 08:33:56
● 2026-04-24 17:15:28

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
jaydenhess.comns1.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: 368ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A166.42.113.147
AAAA12001:19f0:5c01:1061:5400:4ff:fed4:af1
NS3ns1.wpdns.host, ns3.wpdns.host...
SOA1ns1.vultr.com dnsadm.choopa.com

Analysis

IP Addresses

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

Other host names, for example ashleyhess.com, mysite-coach.tempurl.host and www.ashleyhess.com share IPs with jaydenhess.com.

Name Servers

jaydenhess.com is delegated to four name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

jaydenhess.com at least partially shares name servers with other domains, for example pennedcon.com, johnbolton.info, 439932.com, sureshotbasketball.com and arteymercado.com.

these name servers are commonly used alongside ns2.vultr.com name servers.

Host names with three IP numbers:

ns1.vultr.com points to: 2001:19f0:ccc::1, 2001:19f0:ccd::1 and 173.199.96.96.

Host names with two IP numbers:

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

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

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

Host names pointing to 2001:19f0:ccd::1: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.

Host names pointing to 173.199.96.96: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.