`projectquivia.dev`

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

`dev`

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

🔒 HSTS Preload (+subdomains)

Same first word

projectquivia.app

projectquivia.net

projectquivia.com

projectquivia.dev

DNS History

4 records (4 active, 0 former)

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

● 2026-02-28 13:03:06
● 2026-05-09 20:37:42

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

● 2026-02-28 13:03:06
● 2026-05-09 20:37:42

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

● 2026-02-28 13:03:06
● 2026-05-09 20:37:42

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

● 2026-02-28 13:03:06
● 2026-05-09 20:37:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
projectquivia.dev	ns2-01.azure-dns.net, ns4-01.azure-dns.info, ns1-01.azure-dns.com, ns3-01.azure-dns.org	-

✅ Authoritative Response

Server:204.14.183.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for projectquivia.dev (unsigned zone)

⏱️ Timing

Total: 343ms | Queries: -

📄 Records

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

Analysis

Name Servers

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

projectquivia.dev shares some name servers with other domains, for example oaklee.org.uk, file4.info, skydrive.com.br, ticketminds.be and dynamicsproductinsights.co.za.

Host names with two IP numbers

Two IPs per host:

ns1-01.azure-dns.com points to 2603:1061:0:700::1 and 13.107.236.1

ns4-01.azure-dns.info points to 2620:1ec:bda:700::1 and 208.84.5.1

ns2-01.azure-dns.net points to 2620:1ec:8ec:700::1 and 150.171.21.1

ns3-01.azure-dns.org points to 2a01:111:4000:700::1 and 204.14.183.1

projectquivia.dev - robtex.com