`digitalledger.com`

DNSSEC	⚠️ Not signed
A	13.56.33.8^{🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix}
		PTR	`ec2-13-56-33-8.us-west-1.compute.amazonaws.com`
NS	`ns1.brandbucket.com` ⭐
		A	2600:1f1c:800:8b01:2ba3:bb61:44fb:b361^{🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS}
		A	54.241.53.41^{🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix}
			PTR	`ec2-54-241-53-41.us-west-1.compute.amazonaws.com`
NS	`ns2.brandbucket.com`
		A	2600:1f16:54:8701:4012:7e34:5c5f:95a8^{🇺🇸 Amazon2600:1f16::/38 AMAZON AWS}
		A	18.221.52.246^{🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix}
			PTR	`ec2-18-221-52-246.us-east-2.compute.amazonaws.com`
TXT	`27aab5373841b85aab94982ee19ab62f96481ed6`
TXT	`v=spf1 -all`
TXT	`afternic-verification-cvgUQU8SkLxsjXcPBSk2CM`
SOA	`ns1.brandbucket.com`mail@digitalledger.com 2024-03-05 #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=1784124547

Same first word

digitalledger.com

digitalledger.dev

digitalledger.click

digitalledger.app

DNS History

7 records (3 active, 4 former)

○NSns1.bluehost.com2015-11-19 → 2017-02-11 · 4 obs

● 2015-11-19 07:31:30
● 2017-02-11 03:25:14
○ 2026-05-05 09:05:26
○ 2026-07-15 14:27:08

●NSns1.brandbucket.com2026-05-05 → 2026-07-15 · 3 obs

○ 2017-02-11 03:25:14
● 2026-05-05 09:05:26
● 2026-07-15 14:27:08

○NSns2.bluehost.com2015-11-19 → 2017-02-11 · 4 obs

● 2015-11-19 07:31:30
● 2017-02-11 03:25:14
○ 2026-05-05 09:05:26
○ 2026-07-15 14:27:08

●NSns2.brandbucket.com2026-05-05 → 2026-07-15 · 3 obs

○ 2017-02-11 03:25:14
● 2026-05-05 09:05:26
● 2026-07-15 14:27:08

○MXmail.digitalledger.com2015-11-19 → 2017-02-11 · 4 obs

● 2015-11-19 07:31:30
● 2017-02-11 03:25:14
○ 2026-05-05 09:05:26
○ 2026-07-15 14:27:08

●A13.56.33.82026-05-05 → 2026-07-15 · 3 obs

○ 2017-02-11 03:25:14
● 2026-05-05 09:05:26
● 2026-07-15 14:27:08

○A50.87.248.642015-11-19 → 2017-02-11 · 4 obs

● 2015-11-19 07:31:30
● 2017-02-11 03:25:14
○ 2026-05-05 09:05:26
○ 2026-07-15 14:27:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net, c.gtld-servers.net...	-
digitalledger.com	ns1.brandbucket.com, ns2.brandbucket.com	2 records

✅ Authoritative Response

Server:54.241.53.41

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for digitalledger.com (unsigned zone)

⏱️ Timing

Total: 253ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`13.56.33.8`
NS	2	`ns1.brandbucket.com, ns2.brandbucket.com`
TXT	3	`27aab5373841b85aab94982ee19ab62f96481ed6, v=spf1 -all...`
SOA	1	`ns1.brandbucket.com mail.digitalledger.c`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)

Analysis

IP Addresses

digitalledger.com resolves to one IP address: 13.56.33.8.

naturaldaddy.com, vopoc.com, vertacom.com and two other host names share IP numbers with digitalledger.com.

Name Servers

DNS delegation for digitalledger.com points to two name servers: ns1.brandbucket.com and ns2.brandbucket.com.

digitalledger.com uses the same name servers as several other domains — among them zurtu.com, bounceo.com, coinexo.com and two more.

ns1.brandbucket.com directs to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361. ns2.brandbucket.com directs to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8. Each host name carries two IP addresses.

digitalledger.com - robtex.com