dataplay.io - dns.ninja

`dataplay.io`

DNSSEC	⚠️ Not signed
NS	`ns-1276.awsdns-31.org` ⭐
		A	2600:9000:5304:fc00::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1276.awsdns-31.org`
		A	205.251.196.252^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1276.awsdns-31.org`
NS	`ns-1635.awsdns-12.co.uk`
		A	2600:9000:5306:6300::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1635.awsdns-12.co.uk`
		A	205.251.198.99^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1635.awsdns-12.co.uk`
NS	`ns-290.awsdns-36.com`
		A	2600:9000:5301:2200::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-290.awsdns-36.com`
		A	205.251.193.34^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-290.awsdns-36.com`
NS	`ns-624.awsdns-14.net`
		A	2600:9000:5302:7000::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-624.awsdns-14.net`
		A	205.251.194.112^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-624.awsdns-14.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.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:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-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.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`8wSDqGtXYFmnjNHmdyaHiSbfuD9vXiZJ7lBFjKy4rSM=`
TXT	`v=spf1 include:_spf.google.com include:amazonses.com -all`
SOA	`ns-1276.awsdns-31.org`awsdns-hostmaster@amazon.com serial=1

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

Subdomains

auth.dataplay.io

Same first word

dataplay.ca

dataplay.ru

dataplay.io

dataplay.com

dataplay.de

dataplay.space

dataplay.co

dataplay.net

dataplay.cn

dataplay.co.uk

dataplay.it

dataplay.us

Similar names

playdata.io

playdata.com

playdata.ru

playdata.cn

DNS History

26 records (9 active, 17 former)

○NShosting1.cdns.net2016-04-05 → 2016-09-14 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2016-09-14 02:14:06
○ 2017-04-20 11:41:22
○ 2026-08-09 17:38:30

○NShosting2.cdns.net2016-04-05 → 2016-09-14 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2016-09-14 02:14:06
○ 2017-04-20 11:41:22
○ 2026-08-09 17:38:30

○NShosting3.cdns.net2016-04-05 → 2016-09-14 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2016-09-14 02:14:06
○ 2017-04-20 11:41:22
○ 2026-08-09 17:38:30

○NShosting4.cdns.net2016-04-05 → 2016-09-14 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2016-09-14 02:14:06
○ 2017-04-20 11:41:22
○ 2026-08-09 17:38:30

●NSns-1276.awsdns-31.org2026-04-02 → 2026-08-09 · 3 obs

○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

●NSns-1635.awsdns-12.co.uk2026-04-02 → 2026-08-09 · 3 obs

○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

●NSns-290.awsdns-36.com2026-04-02 → 2026-08-09 · 3 obs

○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

●NSns-624.awsdns-14.net2026-04-02 → 2026-08-09 · 3 obs

○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

○NSns-cloud-e1.googledomains.com2017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-14 02:14:06
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

○NSns-cloud-e2.googledomains.com2017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-14 02:14:06
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

○NSns-cloud-e3.googledomains.com2017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-14 02:14:06
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

○NSns-cloud-e4.googledomains.com2017-04-20 → 2017-04-20 · 4 obs

○ 2016-09-14 02:14:06
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

○NSns1-1.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

○NSns1-2.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

○NSns1-3.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

○NSns1-4.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

○NSns1-5.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

○NSns1-6.hpclouddns.net2015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

●MXalt1.aspmx.l.google.com2015-06-14 → 2026-08-09 · 2 obs

● 2015-06-14 19:14:46
● 2026-08-09 17:38:30

●MXalt2.aspmx.l.google.com2015-06-14 → 2026-08-09 · 2 obs

● 2015-06-14 19:14:46
● 2026-08-09 17:38:30

○MXalt3.aspmx.l.google.com2016-04-05 → 2017-04-20 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

○MXalt4.aspmx.l.google.com2016-04-05 → 2017-04-20 · 5 obs

○ 2016-01-21 22:09:00
● 2016-04-05 16:03:08
● 2017-04-20 11:41:22
○ 2026-04-02 23:25:06
○ 2026-08-09 17:38:30

●MXaspmx.l.google.com2015-06-14 → 2026-08-09 · 2 obs

● 2015-06-14 19:14:46
● 2026-08-09 17:38:30

●MXaspmx2.googlemail.com2015-06-14 → 2026-08-09 · 6 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

●MXaspmx3.googlemail.com2015-06-14 → 2026-08-09 · 6 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2017-04-20 11:41:22
● 2026-04-02 23:25:06
● 2026-08-09 17:38:30

○A15.126.241.732015-06-14 → 2016-01-21 · 4 obs

● 2015-06-14 19:14:46
● 2016-01-21 22:09:00
○ 2016-04-05 16:03:08
○ 2026-08-09 17:38:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
io	c0.nic.io, a2.nic.io, a0.nic.io, b0.nic.io	-
dataplay.io	ns-290.awsdns-36.com, ns-624.awsdns-14.net, ns-1276.awsdns-31.org, ns-1635.awsdns-12.co.uk	-

✅ Authoritative Response

Server:205.251.193.34

NS records: ns-290.awsdns-36.com, ns-624.awsdns-14.net, ns-1276.awsdns-31.org, ns-1635.awsdns-12.co.uk

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dataplay.io (unsigned zone)

⏱️ Timing

Total: 496ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-1276.awsdns-31.org, ns-1635.awsdns-12.co.uk...`
MX	5	`aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)...`
TXT	2	`8wSDqGtXYFmnjNHmdyaHiSbfuD9vXiZJ7lBFjKy4, v=spf1 include:_spf.google.com include:a`
SOA	1	`ns-1276.awsdns-31.org awsdns-hostmaster.`

Analysis

Hierarchy

dataplay.io is a parent domain of auth.dataplay.io.

Name Servers

The authoritative name servers for dataplay.io are ns-290.awsdns-36.com, ns-624.awsdns-14.net, ns-1276.awsdns-31.org and ns-1635.awsdns-12.co.uk.

dataplay.io shares at least some of its name servers with other domains, including hypertraffic.net, seaworldcarnivale.com, anamo.native-api.blob.core-azure.betsafe.lv and two others.

These name servers are frequently seen alongside the name servers ns-354.awsdns-44.com, ns-536.awsdns-03.net, ns-1300.awsdns-34.org and ns1.getnetset.com.

The host names ns-290.awsdns-36.com, ns-624.awsdns-14.net, ns-1276.awsdns-31.org and ns-1635.awsdns-12.co.uk each resolve to two IP addresses: ns-290.awsdns-36.com resolves to 205.251.193.34 and 2600:9000:5301:2200::1; ns-624.awsdns-14.net resolves to 205.251.194.112 and 2600:9000:5302:7000::1; ns-1276.awsdns-31.org resolves to 205.251.196.252 and 2600:9000:5304:fc00::1; ns-1635.awsdns-12.co.uk resolves to 205.251.198.99 and 2600:9000:5306:6300::1.

Mail Servers

Mail for dataplay.io is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

dataplay.io has at least partial mail server overlap with other domains such as ns500758.ns500759.ns500758.ns500698.ns500698.ns500735.ns500735.ns500698.ns500698.ns500576.ns500576.ns500652.ns500619.trackreceptor.com, ns500698.ns500759.ns500698.ns500736.ns500735.ns500698.ns500736.ns500736.ns500736.ns500576.ns500708.ns500698.ns500698.ns500619.ns500619.ns500619.trackreceptor.com, ns500699.ns500693.ns500734.ns500693.ns500693.ns500693.ns500699.ns500699.ns500699.ns500588.ns500699.ns500699.ns500588.ns500588.ns500632.ns500112.dtrkdll.com and two more.

These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx2.googlemail.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com directs traffic to 142.251.111.27 and 2607:f8b0:4004:c1b::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

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