`primechasedata.com`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
A	216.150.16.193^{🇨🇦 Amazon216.150.16.0/24 EC2 Prefix}
NS	`ns1.vercel-dns.com` ⭐
		A	2620:4d:4000:6259:7:13:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p13.nsone.net`
		A	198.51.44.13^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p13.nsone.net`
NS	`ns2.vercel-dns.com`
		A	2a00:edc0:6259:7:13::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p13.nsone.net`
		A	198.51.45.13^{🇺🇸 NSONE198.51.45.0/24 198.51.45.0}
			PTR	`dns2.p13.nsone.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`google-site-verification=WmWAQ528ZPnBsrRUIA4ZT2uAK-j77IBgvSkiEmyEZiU`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1756096401

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

🔒 HSTS Preload (+subdomains)

Same first word

primechasedata.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
primechasedata.com	ns1.vercel-dns.com, ns2.vercel-dns.com	4 records

✅ Authoritative Response

Server:198.51.45.13

NS records: ns1.vercel-dns.com, ns2.vercel-dns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for primechasedata.com (unsigned zone)

⏱️ Timing

Total: 311ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`216.150.1.65, 216.150.16.1`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=WmWAQ528ZPnBsrR, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.vercel-dns.com, ns1.vercel-dns.com, ns2.vercel-dns.com...)

Analysis

IP Addresses

primechasedata.com has two IP numbers: 216.150.1.1 and 216.150.16.193.

Other host names, for instance route25.app, synadia.com, geoex.com, ticket.mx and politiskreklame.dk share IP numbers with primechasedata.com.

Name Servers

primechasedata.com's delegation uses two name servers: ns1.vercel-dns.com and ns2.vercel-dns.com.

primechasedata.com uses the same name server setup as other domains, such as parizeventos.com.br, mug.chat, flashapp.site, uprank.de and firstframemedia.com.

primechasedata.com at least partially shares name servers with other domains, including z61a.com, spiral.technology, malkomalko.com, atomizecode.com and palmer.chat.