`projectquivia.app`

DNSSEC	⚠️ Not signed
NS	`ns1-04.azure-dns.com` ⭐
		A	2603:1061:0:700::4^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
		A	13.107.236.4^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-04.azure-dns.com`
NS	`ns2-04.azure-dns.net`
		A	2620:1ec:8ec:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
		A	150.171.21.4^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-04.azure-dns.net`
NS	`ns3-04.azure-dns.org`
		A	2a01:111:4000:700::4^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-04.azure-dns.org`
		A	204.14.183.4^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-04.azure-dns.org`
NS	`ns4-04.azure-dns.info`
		A	2620:1ec:bda:700::4^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
		A	208.84.5.4^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-04.azure-dns.info`
SOA	`ns1-04.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`app`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=101427

🔒 HSTS Preload (+subdomains)

Same first word

projectquivia.net

projectquivia.com

projectquivia.dev

projectquivia.app

DNS History

4 records (4 active, 0 former)

●NSns1-04.azure-dns.com2026-02-28 → 2026-05-09 · 2 obs

● 2026-02-28 13:01:32
● 2026-05-09 18:16:14

●NSns2-04.azure-dns.net2026-02-28 → 2026-05-09 · 2 obs

● 2026-02-28 13:01:32
● 2026-05-09 18:16:14

●NSns3-04.azure-dns.org2026-02-28 → 2026-05-09 · 2 obs

● 2026-02-28 13:01:32
● 2026-05-09 18:16:14

●NSns4-04.azure-dns.info2026-02-28 → 2026-05-09 · 2 obs

● 2026-02-28 13:01:32
● 2026-05-09 18:16:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
projectquivia.app	ns1-04.azure-dns.com, ns3-04.azure-dns.org, ns4-04.azure-dns.info, ns2-04.azure-dns.net	-

✅ Authoritative Response

Server:208.84.5.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for projectquivia.app (unsigned zone)

⏱️ Timing

Total: 298ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-04.azure-dns.com, ns2-04.azure-dns.net...`
SOA	1	`ns1-04.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...)

Analysis

Name Servers

projectquivia.app is delegated to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

At least part of the name servers for projectquivia.app are shared with other domains, for instance pineconeresearch.com, currentdigital.net, ict.kyoiku.metro.tokyo.jp, halo5.com and febrezetradeup.com.

Host names with two IP numbers:

ns1-04.azure-dns.com points to: 2603:1061:0:700::4 and 13.107.236.4

ns4-04.azure-dns.info points to: 2620:1ec:bda:700::4 and 208.84.5.4

ns2-04.azure-dns.net points to: 2620:1ec:8ec:700::4 and 150.171.21.4

ns3-04.azure-dns.org points to: 2a01:111:4000:700::4 and 204.14.183.4

projectquivia.app - robtex.com