`concert-tracking.app`

DNSSEC	⚠️ Not signed
A	216.150.1.193^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
A	216.150.16.129^{🇨🇦 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 PNAP-ACS nsone-1}
			PTR	`dns1.p13.nsone.net`
		A	198.51.44.13^{🇺🇸 NSONE198.51.44.0/24}
			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}
			PTR	`dns2.p13.nsone.net`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1785853476

`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

⚠️ On DNS blocklist: tif, tif.medium, tif.mini
🔒 HSTS Preload (+subdomains)

Same first word

concert-tracking.app

DNS History

7 records (4 active, 3 former)

●NSns1.vercel-dns.com2026-08-07 → 2026-08-13 · 2 obs

● 2026-08-07 20:25:12
● 2026-08-13 12:33:56

●NSns2.vercel-dns.com2026-08-07 → 2026-08-13 · 2 obs

● 2026-08-07 20:25:12
● 2026-08-13 12:33:56

●A216.150.1.1932026-08-07 → 2026-08-13 · 3 obs

○ 2026-08-07 20:25:12
● 2026-08-07 23:53:42
● 2026-08-13 12:33:56

○A216.150.1.652026-08-07 → 2026-08-07 · 3 obs

○ 2026-08-07 20:25:12
● 2026-08-07 23:53:42
○ 2026-08-13 12:33:56

○A216.150.16.12026-08-07 → 2026-08-07 · 3 obs

● 2026-08-07 20:25:12
○ 2026-08-07 23:53:42
○ 2026-08-13 12:33:56

●A216.150.16.1292026-08-13 → 2026-08-13 · 2 obs

○ 2026-08-07 23:53:42
● 2026-08-13 12:33:56

○A216.150.16.652026-08-07 → 2026-08-07 · 3 obs

● 2026-08-07 20:25:12
○ 2026-08-07 23:53:42
○ 2026-08-13 12:33:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
concert-tracking.app	ns2.vercel-dns.com, ns1.vercel-dns.com	-

✅ Authoritative Response

Server:198.51.44.13

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for concert-tracking.app (unsigned zone)

⏱️ Timing

Total: 811ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`216.150.1.193, 216.150.16.1`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
SOA	1	`ns1.vercel-dns.com hostmaster.nsone.net`

Analysis

IP Addresses

concert-tracking.app resolves to the IP addresses 216.150.1.193 and 216.150.16.129

Among the host names that share IP numbers with concert-tracking.app are name02.cssv.jp, lideresdeexito.com, gamerscout.io and two others.

Name Servers

concert-tracking.app has two authoritative name servers — ns1.vercel-dns.com and ns2.vercel-dns.com.

concert-tracking.app has the same name server delegation as a number of other domains, such as emissorgssistemas.com.br, unhaze.ai, turbocook.app and two more.

There is an overlap in name servers between concert-tracking.app and other domains, for example jameswiens.dev, msc.guide and gyan.biz

These name servers are frequently seen alongside the name servers e.zeit-world.com.

Both ns1.vercel-dns.com and ns2.vercel-dns.com have two IP addresses each. ns1.vercel-dns.com resolves to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; ns2.vercel-dns.com resolves to 198.51.45.13 and 2a00:edc0:6259:7:13::2.

concert-tracking.app - robtex.com