`amplifydata.io`

DNSSEC	⚠️ Not signed
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`henry.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3bb0^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`henry.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1b0^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`henry.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21b0^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`henry.ns.cloudflare.com`
		A	108.162.193.176^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`henry.ns.cloudflare.com`
		A	172.64.33.176^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`henry.ns.cloudflare.com`
		A	173.245.59.176^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`henry.ns.cloudflare.com`
NS	`sandy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3adb^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0db^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sandy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20db^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sandy.ns.cloudflare.com`
		A	108.162.192.219^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	172.64.32.219^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	173.245.58.219^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`google-site-verification=pf1YeHsDPM3l5-PeusfWoT2uWKrDWCgc3wT9VDjuAJY`
TXT	`proxy-ssl.webflow.com`
TXT	`v=spf1 include:_spf.google.com include:spf.mailjet.com include:44536248.spf05...`
SOA	`henry.ns.cloudflare.com`dns@cloudflare.com serial=2410207420

`io`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.nic.io` ⭐
	NS	`a2.nic.io`
	NS	`b0.nic.io`
	NS	`c0.nic.io`
	SOA	`a0.nic.io`hostmaster@donuts.email serial=1786100878

Same first word

amplifydata.io

DNS History

8 records (8 active, 0 former)

●NShenry.ns.cloudflare.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●NSsandy.ns.cloudflare.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●MXalt1.aspmx.l.google.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●MXalt2.aspmx.l.google.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●MXaspmx.l.google.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●MXaspmx2.googlemail.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●MXaspmx3.googlemail.com2026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

●A198.202.211.12026-05-18 → 2026-08-07 · 2 obs

● 2026-05-18 13:02:16
● 2026-08-07 11:19:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
io	a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io	-
amplifydata.io	sandy.ns.cloudflare.com, henry.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.219

NS records: sandy.ns.cloudflare.com, henry.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for amplifydata.io (unsigned zone)

⏱️ Timing

Total: 597ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	2	`henry.ns.cloudflare.com, sandy.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	3	`google-site-verification=pf1YeHsDPM3l5-P, proxy-ssl.webflow.com...`
SOA	1	`henry.ns.cloudflare.com dns.cloudflare.c`

Analysis

IP Addresses

amplifydata.io directs to one IP number, which is 198.202.211.1.

Among the host names that share IP numbers with amplifydata.io are lendocstudio.com, twise.eu, nyevinduer.dk and two others.

Name Servers

amplifydata.io has two authoritative name servers — henry.ns.cloudflare.com and sandy.ns.cloudflare.com.

amplifydata.io has the same name server delegation as a number of other domains, such as etev.org, allthingscomedy.com, classsiccards.com and two more.

The name servers of amplifydata.io overlap at least partially with those of other domains — among them srvcontrol.xyz, sommiteworks.click, penhandle.com and two more.

These name servers commonly co-occur with the name servers zainab.ns.cloudflare.com, candy.ns.cloudflare.com, jade.ns.cloudflare.com and jerry.ns.cloudflare.com.

Host names resolving to 6 IP numbers:

henry.ns.cloudflare.com points to 108.162.193.176, 172.64.33.176, 173.245.59.176 and 3 other IP addresses.

sandy.ns.cloudflare.com points to 108.162.192.219, 172.64.32.219, 173.245.58.219 and 3 other IP addresses.

Mail Servers

Five mail servers handle amplifydata.io: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

amplifydata.io shares at least some of its mail servers with other domains — for example ns500731.ns500731.ns500742.ns500671.ns500731.ns500671.ns500678.ns500678.ns500671.ns500649.ns500153.tenderladiesbz.com, ns500599.ns500599.ns500599.ns500724.ns500724.ns500724.ns500724.ns500724.ns500599.ns500724.ns500737.ns500583.ns500599.ns500669.www.yummyflingsfinder.com, ns500742.ns500754.ns500705.ns500705.ns500704.ns500705.ns500671.ns500688.ns500688.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com and two more.

It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.

Hosts with two IP numbers each:

aspmx2.googlemail.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com resolves to 142.251.179.27 and 2607:f8b0:4004:c1b::1a.

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

alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1a IP addresses.

The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 2a00:1450:400b:c02::1a IP addresses.

The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.26 IP addresses.

amplifydata.io - robtex.com

amplifydata.io

io

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`amplifydata.io`

`io`