`5crowd.com`

DNSSEC	⚠️ Not signed
NS	`ns1-06.azure-dns.com` ⚠️ Not in zone NS records
		A	2603:1061:0:700::6^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
		A	13.107.236.6^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
NS	`ns2-06.azure-dns.net` ⚠️ Not in zone NS records
		A	2620:1ec:8ec:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
		A	150.171.21.6^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
NS	`ns3-06.azure-dns.org` ⚠️ Not in zone NS records
		A	2a01:111:4000:700::6^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-06.azure-dns.org`
		A	204.14.183.6^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-06.azure-dns.org`
NS	`ns4-06.azure-dns.info` ⚠️ Not in zone NS records
		A	2620:1ec:bda:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
		A	208.84.5.6^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`

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

Same first word

5crowd.com

DNS History

19 records (4 active, 15 former)

○NSelinore.ns.cloudflare.com2016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○NSlars.ns.cloudflare.com2016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

●NSns1-06.azure-dns.com2026-04-08 → 2026-05-10 · 3 obs

○ 2017-03-28 13:21:40
● 2026-04-08 14:33:20
● 2026-05-10 22:35:22

●NSns2-06.azure-dns.net2026-04-08 → 2026-05-10 · 3 obs

○ 2017-03-28 13:21:40
● 2026-04-08 14:33:20
● 2026-05-10 22:35:22

●NSns3-06.azure-dns.org2026-04-08 → 2026-05-10 · 3 obs

○ 2017-03-28 13:21:40
● 2026-04-08 14:33:20
● 2026-05-10 22:35:22

○NSns35.domaincontrol.com2015-08-08 → 2016-03-10 · 4 obs

● 2015-08-08 14:51:14
● 2016-03-10 13:34:02
○ 2016-06-30 12:08:46
○ 2026-05-10 22:35:22

○NSns36.domaincontrol.com2015-08-08 → 2016-03-10 · 4 obs

● 2015-08-08 14:51:14
● 2016-03-10 13:34:02
○ 2016-06-30 12:08:46
○ 2026-05-10 22:35:22

●NSns4-06.azure-dns.info2026-04-08 → 2026-05-10 · 3 obs

○ 2017-03-28 13:21:40
● 2026-04-08 14:33:20
● 2026-05-10 22:35:22

○MXalt1.aspmx.l.google.com2015-08-08 → 2017-03-28 · 4 obs

● 2015-08-08 14:51:14
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○MXalt2.aspmx.l.google.com2015-08-08 → 2017-03-28 · 4 obs

● 2015-08-08 14:51:14
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○MXaspmx.l.google.com2015-08-08 → 2017-03-28 · 4 obs

● 2015-08-08 14:51:14
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○MXaspmx2.googlemail.com2015-08-08 → 2017-03-28 · 4 obs

● 2015-08-08 14:51:14
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○MXaspmx3.googlemail.com2015-08-08 → 2017-03-28 · 4 obs

● 2015-08-08 14:51:14
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○A104.27.142.212016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○A104.27.143.212016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○A184.168.221.42015-11-29 → 2016-03-10 · 5 obs

○ 2015-08-08 14:51:14
● 2015-11-29 23:08:28
● 2016-03-10 13:34:02
○ 2016-06-30 12:08:46
○ 2026-05-10 22:35:22

○A2400:cb00:2048:1::681b:8e152016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○A2400:cb00:2048:1::681b:8f152016-06-30 → 2017-03-28 · 5 obs

○ 2016-03-10 13:34:02
● 2016-06-30 12:08:46
● 2017-03-28 13:21:40
○ 2026-04-08 14:33:20
○ 2026-05-10 22:35:22

○A68.178.254.2352015-08-08 → 2015-08-08 · 3 obs

● 2015-08-08 14:51:14
○ 2015-11-29 23:08:28
○ 2026-05-10 22:35:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net, l.gtld-servers.net...	-
5crowd.com	ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.6

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 5crowd.com (unsigned zone)

⏱️ Timing

Total: 377ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-06.azure-dns.com, ns1-06.azure-dns.com)

Analysis

Name Servers

5crowd.com is delegated to four name servers: ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.

5crowd.com shares some name servers with other domains, for example arden.nsw.edu.au, hotmailreactivate.biz, loader.it, msdynmktgpe.com and 71.20.in-addr.arpa.

Host names with two IP numbers

Two IPs per host:

ns1-06.azure-dns.com points to 2603:1061:0:700::6 and 13.107.236.6

ns4-06.azure-dns.info points to 2620:1ec:bda:700::6 and 208.84.5.6

ns2-06.azure-dns.net points to 2620:1ec:8ec:700::6 and 150.171.21.6

ns3-06.azure-dns.org points to 2a01:111:4000:700::6 and 204.14.183.6

5crowd.com - robtex.com

5crowd.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

`5crowd.com`

`com`