`daytonablogger.com`

DNSSEC	⚠️ Not signed
A	54.167.160.107^{🇺🇸 Amazon54.166.0.0/15 EC2 IAD prefix}
		PTR	`ec2-54-167-160-107.compute-1.amazonaws.com`
NS	`ns1.hover.com` ⭐
		A	2604:4000:0:d:216:40:47:26^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`ns1.hover.com`
		A	216.40.47.26^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`ns1.hover.com`
NS	`ns2.hover.com`
		A	2604:4000:2800:d:64:99:148:13^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`ns2.hover.com`
		A	64.98.148.13^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`ns2.hover.com`
SOA	`ns1.hover.com`dnsmaster@hover.com serial=1745772221

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

Same first word

daytonablogger.com

DNS History

10 records (3 active, 7 former)

○NSdns1.name-services.com2015-07-19 → 2017-04-02 · 3 obs

● 2015-07-19 00:51:28
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

○NSdns2.name-services.com2015-07-19 → 2017-04-02 · 3 obs

● 2015-07-19 00:51:28
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

○NSdns3.name-services.com2015-07-19 → 2017-04-02 · 3 obs

● 2015-07-19 00:51:28
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

○NSdns4.name-services.com2015-07-19 → 2017-04-02 · 3 obs

● 2015-07-19 00:51:28
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

○NSdns5.name-services.com2015-07-19 → 2017-04-02 · 3 obs

● 2015-07-19 00:51:28
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

●NSns1.hover.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-04-02 08:07:54
● 2026-03-26 04:25:50

●NSns2.hover.com2026-03-26 → 2026-03-26 · 2 obs

○ 2017-04-02 08:07:54
● 2026-03-26 04:25:50

○A169.44.64.2342016-06-20 → 2017-04-02 · 4 obs

○ 2016-02-22 18:39:56
● 2016-06-20 22:58:20
● 2017-04-02 08:07:54
○ 2026-03-26 04:25:50

○A174.133.247.1462015-07-19 → 2016-02-22 · 4 obs

● 2015-07-19 00:51:28
● 2016-02-22 18:39:56
○ 2016-06-20 22:58:20
○ 2026-03-26 04:25:50

●A54.167.160.1072026-03-26 → 2026-03-26 · 2 obs

○ 2017-04-02 08:07:54
● 2026-03-26 04:25:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
daytonablogger.com	ns1.hover.com, ns2.hover.com	4 records

✅ Authoritative Response

Server:216.40.47.26

NS records: ns1.hover.com, ns2.hover.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for daytonablogger.com (unsigned zone)

⏱️ Timing

Total: 183ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.167.160.107`
NS	2	`ns1.hover.com, ns2.hover.com`
SOA	1	`ns1.hover.com dnsmaster.hover.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.hover.com, ns1.hover.com, ns2.hover.com...)

Analysis

IP Addresses

daytonablogger.com points to a single IP: 54.167.160.107.

Other host names, for instance rangersblog.com, idml.org, eatthepress.com, ccxml.net and honeygrove.net share IP numbers with daytonablogger.com.

Name Servers

daytonablogger.com's delegation is to two name servers ns1.hover.com and ns2.hover.com.

daytonablogger.com shares the same name server configuration as other domains, such as chaosiq.com, agirlsgems.com, designinventprint.co.uk, caroandjose.com and brickwhale.com.

daytonablogger.com at least partially shares its name servers with other domains, for instance salesspider.com, riesd.com, daniellaskitchen.com, maresh.org and spectacle.group.

these name servers are commonly used together with ns3.hover.com, ns1.domaindirect.com, ns2.domaindirect.com and ns3.domaindirect.com.

Host names with two IP numbers: ns1.hover.com points to 2604:4000:0:d:216:40:47:26 and 216.40.47.26; ns2.hover.com points to 2604:4000:2800:d:64:99:148:13 and 64.98.148.13

daytonablogger.com - robtex.com