`futurestruct.com`

DNSSEC	⚠️ Not signed
NS	`ns1.domain.com` ⭐
		A	172.64.52.73^{🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.domain.com`
		A	172.64.53.117^{🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 ip4:66.96.128.0/18 include:websitewelcome.com ?all`
SOA	`ns1.domain.com`dnsadmin@domain.com 2024-02-13 #15

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

Same first word

futurestruct.com

DNS History

8 records (2 active, 6 former)

○NSns-cloud-d1.googledomains.com2017-11-10 → 2017-11-10 · 3 obs

● 2017-11-10 06:38:58
○ 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

○NSns-cloud-d2.googledomains.com2017-11-10 → 2017-11-10 · 3 obs

● 2017-11-10 06:38:58
○ 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

○NSns-cloud-d3.googledomains.com2017-11-10 → 2017-11-10 · 3 obs

● 2017-11-10 06:38:58
○ 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

○NSns-cloud-d4.googledomains.com2017-11-10 → 2017-11-10 · 3 obs

● 2017-11-10 06:38:58
○ 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

●NSns1.domain.com2026-02-16 → 2026-03-24 · 3 obs

○ 2017-11-10 06:38:58
● 2026-02-16 07:13:48
● 2026-03-24 22:13:54

●NSns2.domain.com2026-02-16 → 2026-03-24 · 3 obs

○ 2017-11-10 06:38:58
● 2026-02-16 07:13:48
● 2026-03-24 22:13:54

○MXmx.futurestruct.com2026-02-16 → 2026-02-16 · 2 obs

● 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

○A66.96.162.1282026-02-16 → 2026-02-16 · 2 obs

● 2026-02-16 07:13:48
○ 2026-03-24 22:13:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
futurestruct.com	ns2.domain.com, ns1.domain.com	2 records

✅ Authoritative Response

Server:172.64.53.117

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for futurestruct.com (unsigned zone)

⏱️ Timing

Total: 1735ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.96.162.128`
NS	2	`ns1.domain.com, ns2.domain.com`
TXT	1	`v=spf1 ip4:66.96.128.0/18 include:websit`
SOA	1	`ns1.domain.com dnsadmin.domain.com`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

futurestruct.com is delegated to two name servers: ns1.domain.com and ns2.domain.com.

futurestruct.com shares the same name server setup as davidfleurymusic.net, kontan-online.com, alloutnet.com, elegancelite.com and lqce.net.

futurestruct.com at least partially shares name servers with other domains, for instance dreamsworld.me, slidecar.biz, heartfeltcandles.com, lordfilm-ros.ru and food-recipe.ru.

These name servers are commonly used together with ns3.domain.com, ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.

Host names with a single IP:

ns1.domain.com points to 172.64.52.73.

ns2.domain.com points to 172.64.53.117.

futurestruct.com - robtex.com