buildfuture.com - dns.ninja

`buildfuture.com`

DNSSEC	⚠️ Not signed
A	64.98.135.80^{🇺🇸 TUCOWS-364.98.135.0/24 Tucows.com Co.}
NS	`dns1.name-services.com` ⭐
		A	2604:4000:2800:2000:64:98:148:137^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns1.name-services.com`
		A	64.98.148.137^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns1.name-services.com`
NS	`dns2.name-services.com`
		A	2604:4000:0:d:216:40:47:201^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns2.name-services.com`
		A	216.40.47.201^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns2.name-services.com`
NS	`dns3.name-services.com`
		A	2604:4000:2800:2000:64:98:148:138^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns3.name-services.com`
		A	64.98.148.138^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns3.name-services.com`
NS	`dns4.name-services.com`
		A	2604:4000:0:d:216:40:47:202^{🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000}
			PTR	`dns4.name-services.com`
		A	216.40.47.202^{🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0}
			PTR	`dns4.name-services.com`
NS	`dns5.name-services.com`
		A	2604:4000:2800:2000:64:98:148:139^{🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co.}
			PTR	`dns5.name-services.com`
		A	64.98.148.139^{🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co.}
			PTR	`dns5.name-services.com`
SOA	`dns1.name-services.com`info@name-services.com serial=1750787324

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

Same first word

buildfuture.org

buildfuture.com

buildfuture.ai

buildfuture.net

Similar names

futurebuild.co.uk

futurebuild.co.nz

buildfutuer.com

futurebuild.com

DNS History

16 records (6 active, 10 former)

●NSdns1.name-services.com2026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

●NSdns2.name-services.com2026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

●NSdns3.name-services.com2026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

●NSdns4.name-services.com2026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

●NSdns5.name-services.com2026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

○NShost.tradenames.com2008-03-18 → 2016-04-24 · 4 obs

● 2008-03-18 08:01:28
● 2016-04-24 08:06:28
○ 2016-07-01 08:23:22
○ 2026-07-10 19:21:22

○NSns.tradenames.com2008-03-18 → 2016-04-24 · 4 obs

● 2008-03-18 08:01:28
● 2016-04-24 08:06:28
○ 2016-07-01 08:23:22
○ 2026-07-10 19:21:22

○NSns1.dsredirection.com2016-07-01 → 2016-12-26 · 5 obs

○ 2016-04-24 08:06:28
● 2016-07-01 08:23:22
● 2016-12-26 08:53:40
○ 2018-05-25 00:41:22
○ 2026-07-10 19:21:22

○NSns2.dsredirection.com2016-07-01 → 2016-12-26 · 5 obs

○ 2016-04-24 08:06:28
● 2016-07-01 08:23:22
● 2016-12-26 08:53:40
○ 2018-05-25 00:41:22
○ 2026-07-10 19:21:22

○A141.8.230.202016-07-01 → 2016-12-26 · 5 obs

○ 2016-04-24 08:06:28
● 2016-07-01 08:23:22
● 2016-12-26 08:53:40
○ 2018-05-25 00:41:22
○ 2026-07-10 19:21:22

○A64.20.35.1552008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 08:01:28
○ 2015-07-18 21:56:28
○ 2026-07-10 19:21:22

●A64.98.135.802026-03-02 → 2026-07-10 · 3 obs

○ 2018-05-25 00:41:22
● 2026-03-02 10:33:40
● 2026-07-10 19:21:22

○A66.45.246.1402015-10-16 → 2016-04-24 · 5 obs

○ 2008-03-18 08:01:28
● 2015-10-16 10:50:50
● 2016-04-24 08:06:28
○ 2016-07-01 08:23:22
○ 2026-07-10 19:21:22

○CNAMEpres.serverhome.com2016-07-01 → 2018-05-25 · 4 obs

● 2016-07-01 08:23:22
● 2018-05-25 00:41:22
○ 2026-03-02 10:33:40
○ 2026-07-10 19:21:22

○CNAMEthie5ku9.dsgeneration.com2016-07-01 → 2016-12-26 · 4 obs

● 2016-07-01 08:23:22
● 2016-12-26 08:53:40
○ 2018-05-25 00:41:22
○ 2026-07-10 19:21:22

○PTRns1.dsredirection.com2016-12-26 → 2016-12-26 · 3 obs

● 2016-12-26 08:53:40
○ 2018-05-25 00:41:22
○ 2026-07-10 19:21:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, l.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
buildfuture.com	dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com...	10 records

✅ Authoritative Response

Server:64.98.148.139

NS records: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com, dns4.name-services.com, dns5.name-services.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for buildfuture.com (unsigned zone)

⏱️ Timing

Total: 275ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.98.135.80`
NS	5	`dns1.name-services.com, dns2.name-services.com...`
SOA	1	`dns1.name-services.com info.name-service`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (dns1.name-services.com, dns1.name-services.com, dns2.name-services.com...)

Analysis

IP Addresses

buildfuture.com has exactly one IP address — 64.98.135.80.

medacoustic.com, premierpayonline.com, shop(0x65726f746963)tv.org plus two other host names have IP numbers in common with buildfuture.com.

Name Servers

Five name servers handle delegation for buildfuture.com: dns1.name-services.com, dns2.name-services.com, dns3.name-services.com and two others.

There is at least partial name server overlap between buildfuture.com and other domains — pyx.be, wtmarchitect.com, buddylingo.com and two more among them.

These name servers frequently co-occur with the name servers dns4.name-services.com and dns5.name-services.com.

Host names pointing to two IP addresses:

dns1.name-services.com resolves to two addresses: 64.98.148.137 and 2604:4000:2800:2000:64:98:148:137.

dns2.name-services.com resolves to two addresses: 216.40.47.201 and 2604:4000:0:d:216:40:47:201.

dns3.name-services.com resolves to two addresses: 64.98.148.138 and 2604:4000:2800:2000:64:98:148:138.

dns4.name-services.com resolves to two addresses: 216.40.47.202 and 2604:4000:0:d:216:40:47:202.

dns5.name-services.com resolves to two addresses: 64.98.148.139 and 2604:4000:2800:2000:64:98:148:139.