`cryptochallenge.net`

DNSSEC	⚠️ Not signed
A	50.87.77.17^{🇺🇸 EIGI50.87.64.0/20}
		PTR	`50-87-77-17.unifiedlayer.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.markmonitor.com`
		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.markmonitor.com`
		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.markmonitor.com`
		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`
		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`
		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`
		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}
TXT	`v=spf1 -all`
SOA	`ns1.markmonitor.com`hostmaster@markmonitor.com 2018-10-29 #3

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

Same first word

cryptochallenge.com

cryptochallenge.net

cryptochallenge.info

cryptochallenge.biz

cryptochallenge.io

DNS History

15 records (8 active, 7 former)

○NSa4.nstld.com2007-09-23 → 2007-09-23 · 3 obs

● 2007-09-23 01:41:14
○ 2015-07-18 19:27:20
○ 2026-04-12 21:17:24

○NSf4.nstld.com2007-09-23 → 2007-09-23 · 3 obs

● 2007-09-23 01:41:14
○ 2015-07-18 19:27:20
○ 2026-04-12 21:17:24

○NSg4.nstld.com2007-09-23 → 2007-09-23 · 3 obs

● 2007-09-23 01:41:14
○ 2015-07-18 19:27:20
○ 2026-04-12 21:17:24

○NSl4.nstld.com2007-09-23 → 2007-09-23 · 3 obs

● 2007-09-23 01:41:14
○ 2015-07-18 19:27:20
○ 2026-04-12 21:17:24

●NSns1.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns2.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns3.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns4.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns5.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns6.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

●NSns7.markmonitor.com2026-04-09 → 2026-04-12 · 3 obs

○ 2017-04-01 14:19:28
● 2026-04-09 06:58:46
● 2026-04-12 21:17:24

○NSudns1.ultradns.net2015-07-18 → 2017-04-01 · 5 obs

○ 2007-09-23 01:41:14
● 2015-07-18 19:27:20
● 2017-04-01 14:19:28
○ 2026-04-09 06:58:46
○ 2026-04-12 21:17:24

○NSudns2.ultradns.net2015-07-18 → 2017-04-01 · 5 obs

○ 2007-09-23 01:41:14
● 2015-07-18 19:27:20
● 2017-04-01 14:19:28
○ 2026-04-09 06:58:46
○ 2026-04-12 21:17:24

○A198.41.1.402007-09-23 → 2007-09-23 · 3 obs

● 2007-09-23 01:41:14
○ 2015-07-18 19:27:20
○ 2026-04-12 21:17:24

●A50.87.77.172015-07-18 → 2026-04-12 · 3 obs

○ 2007-09-23 01:41:14
● 2015-07-18 19:27:20
● 2026-04-12 21:17:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	j.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, a.gtld-servers.net...	-
cryptochallenge.net	ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com...	-

✅ Authoritative Response

Server:149.112.160.2

NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cryptochallenge.net (unsigned zone)

⏱️ Timing

Total: 534ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`50.87.77.17`
NS	7	`ns1.markmonitor.com, ns2.markmonitor.com...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.markmonitor.com hostmaster.markmonit`

Analysis

IP Addresses

cryptochallenge.net resolves to one IP number: 50.87.77.17.

Other host names including cryptochallenge.com, cryptochallenge.info, cryptochallenge.biz and 50-87-77-17.unifiedlayer.com share IP numbers with cryptochallenge.net.

Name Servers

cryptochallenge.net is delegated to seven name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.

cryptochallenge.net at least partially shares name servers with other domains, including cherry.sk, netsuite.tv, bbhco.cn, exxonmobilsafety.ru and pintrest.com.mx.