playerframework.net - dns.ninja

`playerframework.net`

DNSSEC	⚠️ Not signed
NS	`ns1-02.azure-dns.com` ⭐ ⚠️ Not in zone NS records
		A	2603:1061:0:700::2^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
		A	13.107.236.2^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-02.azure-dns.com`
NS	`ns1.markmonitor.com`
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns2-02.azure-dns.net` ⚠️ Not in zone NS records
		A	2620:1ec:8ec:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
		A	150.171.21.2^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-02.azure-dns.net`
NS	`ns2.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:10b8::1^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns2.markmonitor.com`
		A	176.97.158.1^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns2.markmonitor.com`
NS	`ns3-02.azure-dns.org` ⚠️ Not in zone NS records
		A	2a01:111:4000:700::2^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-02.azure-dns.org`
		A	204.14.183.2^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-02.azure-dns.org`
NS	`ns3.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4-02.azure-dns.info` ⚠️ Not in zone NS records
		A	2620:1ec:bda:700::2^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
		A	208.84.5.2^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-02.azure-dns.info`
NS	`ns4.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com` ⚠️ Not in parent delegation
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
NS	`ns7.markmonitor.com` ⚠️ Not in parent delegation
		A	2620:10a:80a9::2^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.2^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
SOA	`ns1-02.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1781116473

Same first word

playerframework.net

playerframework.org

playerframework.com

DNS History

21 records (11 active, 10 former)

●NSns1-02.azure-dns.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns1.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

○NSns1.msft.net2015-05-18 → 2018-11-18 · 4 obs

● 2015-05-18 23:00:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

●NSns2-02.azure-dns.net2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns2.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

○NSns2.msft.net2015-05-18 → 2018-11-18 · 4 obs

● 2015-05-18 23:00:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

●NSns3-02.azure-dns.org2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns3.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

○NSns3.msft.net2015-05-18 → 2018-11-18 · 4 obs

● 2015-05-18 23:00:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

●NSns4-02.azure-dns.info2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns4.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

○NSns4.msft.net2015-05-18 → 2018-11-18 · 4 obs

● 2015-05-18 23:00:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

●NSns5.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns6.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

●NSns7.markmonitor.com2026-02-28 → 2026-06-10 · 3 obs

○ 2018-11-18 04:52:04
● 2026-02-28 12:07:52
● 2026-06-10 19:00:38

○A104.215.95.1872018-11-18 → 2018-11-18 · 4 obs

○ 2017-02-09 16:55:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

○A40.84.199.2332017-02-09 → 2017-02-09 · 4 obs

○ 2016-07-10 06:50:38
● 2017-02-09 16:55:00
○ 2018-11-18 04:52:04
○ 2026-06-10 19:00:38

○A52.164.206.562018-11-18 → 2018-11-18 · 4 obs

○ 2017-02-09 16:55:00
● 2018-11-18 04:52:04
○ 2026-02-28 12:07:52
○ 2026-06-10 19:00:38

○A52.178.167.1092017-02-09 → 2017-02-09 · 4 obs

○ 2016-07-10 06:50:38
● 2017-02-09 16:55:00
○ 2018-11-18 04:52:04
○ 2026-06-10 19:00:38

○A64.4.6.1002015-05-18 → 2016-07-10 · 4 obs

● 2015-05-18 23:00:00
● 2016-07-10 06:50:38
○ 2017-02-09 16:55:00
○ 2026-06-10 19:00:38

○A65.55.39.102015-05-18 → 2016-07-10 · 4 obs

● 2015-05-18 23:00:00
● 2016-07-10 06:50:38
○ 2017-02-09 16:55:00
○ 2026-06-10 19:00:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	h.gtld-servers.net, a.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net...	-
playerframework.net	ns1.markmonitor.com, ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org...	2 records

✅ Authoritative Response

Server:149.112.160.1

NS records: ns1.markmonitor.com, ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for playerframework.net (unsigned zone)

⏱️ Timing

Total: 652ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-02.azure-dns.com, ns2-02.azure-dns.net...`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-02.azure-dns.net, ns2-02.azure-dns.net)

Analysis

Name Servers

playerframework.net delegates authority to 11 name servers: ns1-02.azure-dns.com, ns1.markmonitor.com, ns2.markmonitor.com plus 8 other.

The name servers of playerframework.net overlap at least partially with those of other domains — among them byrongroe.com, zenprise.org, harperteachers.com and two more.

These name servers commonly appear in delegations together with ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com and 5 other.

Hosts with two IP numbers each:

ns1-02.azure-dns.com directs traffic to 13.107.236.2 and 2603:1061:0:700::2.

ns1.markmonitor.com directs traffic to 149.112.160.1 and 2620:10a:80a8::1.

ns2.markmonitor.com directs traffic to 176.97.158.1 and 2001:67c:10b8::1.

ns3.markmonitor.com directs traffic to 149.112.161.1 and 2620:10a:80a9::1.

ns4.markmonitor.com directs traffic to 192.174.68.1 and 2001:67c:1bc::1.

ns5.markmonitor.com directs traffic to 149.112.160.2 and 2620:10a:80a8::2.

ns6.markmonitor.com directs traffic to 176.97.158.3 and 2001:67c:10b8::3.

ns7.markmonitor.com directs traffic to 149.112.161.2 and 2620:10a:80a9::2.

ns4-02.azure-dns.info directs traffic to 208.84.5.2 and 2620:1ec:bda:700::2.

ns2-02.azure-dns.net directs traffic to 150.171.21.2 and 2620:1ec:8ec:700::2.

ns3-02.azure-dns.org directs traffic to 204.14.183.2 and 2a01:111:4000:700::2.