`futurefoodstudio.com`

DNSSEC	⚠️ Not signed
A	3.215.100.79^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-215-100-79.compute-1.amazonaws.com`
A	3.234.189.133^{🇺🇸 Amazon3.224.0.0/12 EC2 IAD prefix}
NS	`ns1.cargo.site` ⭐
		A	44.205.91.121^{🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix}
			PTR	`ns1.cargo.site`
NS	`ns2.cargo.site`
		A	100.21.27.241^{🇺🇸 Amazon100.20.0.0/14 EC2 PDX prefix}
			PTR	`ns2.cargo.site`
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4009:c19::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrp-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.27^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4025:c01::1b^{🇵🇱 Google2a00:1450:4025::/48}
			PTR	`rd-in-f27.1e100.net`
		A	142.250.147.27^{🇺🇸 Google142.250.147.0/24}
			PTR	`rd-in-f27.1e100.net`
MX	`6cqa5vgpqmoat2eotdwtua5p7vuyd2p4xcxbu4z4vcxdgrm6sxzq.mx-verification.google.com`⁽¹⁵⁾
SOA	`ns1.cargo.site`hostmaster@futurefoodstudio.com 2026-03-26 #1

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

Same first word

futurefoodstudio.com

DNS History

22 records (10 active, 12 former)

●NSns1.cargo.site2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○NSns1.whois.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●NSns2.cargo.site2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○NSns2.whois.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

○NSns3.whois.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

○NSns4.whois.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●MX6cqa5vgpqmoat2eotdwtua5p7vuyd2p4xcxbu4z4vcxdgrm6sxzq.mx-verification.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○MXalt1.aspmx.google.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●MXalt1.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○MXalt2.aspmx.google.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●MXalt2.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○MXalt3.aspmx.google.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●MXalt3.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

○MXalt4.aspmx.google.com2015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●MXalt4.aspmx.l.google.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

●MXaspmx.l.google.com2015-08-20 → 2026-03-28 · 2 obs

● 2015-08-20 13:11:02
● 2026-03-28 00:40:32

○A198.185.159.1442015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

○A198.185.159.1452015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

○A198.49.23.1442015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

○A198.49.23.1452015-08-20 → 2017-06-08 · 3 obs

● 2015-08-20 13:11:02
● 2017-06-08 14:40:50
○ 2026-03-28 00:40:32

●A3.215.100.792026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

●A3.234.189.1332026-03-28 → 2026-03-28 · 2 obs

○ 2017-06-08 14:40:50
● 2026-03-28 00:40:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
futurefoodstudio.com	ns1.cargo.site, ns2.cargo.site	-

✅ Authoritative Response

Server:100.21.27.241

NS records: ns1.cargo.site, ns2.cargo.site

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for futurefoodstudio.com (unsigned zone)

⏱️ Timing

Total: 524ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`3.234.189.133, 3.215.100.79`
NS	2	`ns1.cargo.site, ns2.cargo.site`
MX	6	`alt3.aspmx.l.google.com (pri: 10), 6cqa5vgpqmoat2eotdwtua5p7vuyd2p4xcxbu4z4...`
SOA	1	`ns1.cargo.site hostmaster.futurefoodstud`

Analysis

IP Addresses

futurefoodstudio.com resolves to two IP numbers: 3.215.100.79 and 3.234.189.133.

other host names including obstart.com, husedesign.com, happdesign.com, pepppa.com and skykawano.com share IP numbers with futurefoodstudio.com.

Name Servers

futurefoodstudio.com is delegated to two name servers ns1.cargo.site and ns2.cargo.site.

futurefoodstudio.com shares the same name server setup as other domains, for instance nekolos.com, blumestudio.com, arenacomunicacion.com, allison-eng.com and digitalcube.cn.

futurefoodstudio.com at least partially shares name servers with other domains, for instance marksavoia.ca, johnathanscane.co.uk, vertigo.jp, jonathanlawrence.net and warranty.aero.

These name servers are commonly used alongside ns1.cargocollective.com and ns2.cargocollective.com.

Host names with one IP number:

ns1.cargo.site points to 44.205.91.121

ns2.cargo.site points to 100.21.27.241

Mail Servers

futurefoodstudio.com is served by six mail servers: aspmx.l.google.com, 6cqa5vgpqmoat2eotdwtua5p7vuyd2p4xcxbu4z4vcxdgrm6sxzq.mx-verification.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

futurefoodstudio.com shares some mail servers with other domains, at least partially, for instance imminentlatency.com, ns500754.ns500742.ns500731.ns500742.ns500688.ns500688.ns500705.ns500153.tenderladiesbz.com, ns500742.ns500671.ns500754.ns500671.ns500731.ns500704.ns500671.ns500688.ns500678.ns500649.ns500666.ns500291.ns500291.ns500131.lustychickser.com, ns500699.ns500734.ns500699.ns500734.ns500734.ns500699.ns500699.ns500699.ns500693.ns500699.ns500693.ns500699.ns500693.ns500588.ns500110.dtrkdll.com and ns500742.ns500742.ns500731.ns500731.ns500731.ns500688.ns500705.ns500649.ns500649.ns500666.ns500291.ns500291.ns500131.lustychickser.com.

these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com points to 2a00:1450:4009:c19::1a and 192.178.223.27

alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.26

alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1b and 172.253.135.27

alt3.aspmx.l.google.com points to 2a00:1450:4009:c0f::1a and 192.178.223.26

alt4.aspmx.l.google.com points to 2a00:1450:4025:c01::1b and 142.250.147.27

futurefoodstudio.com - robtex.com