`metrowatch.app`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
A	216.150.1.193^{🇨🇦 Amazon216.150.1.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`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1749671601

`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

metrowatch.co.uk

metrowatch.app

metrowatch.com.pk

DNS History

9 records (4 active, 5 former)

●NSns1.vercel-dns.com2026-07-16 → 2026-07-17 · 2 obs

● 2026-07-16 07:56:04
● 2026-07-17 17:30:34

●NSns2.vercel-dns.com2026-07-16 → 2026-07-17 · 2 obs

● 2026-07-16 07:56:04
● 2026-07-17 17:30:34

●A216.150.1.12026-07-17 → 2026-07-17 · 3 obs

○ 2026-07-17 00:04:18
● 2026-07-17 06:02:26
● 2026-07-17 17:30:34

○A216.150.1.1292026-07-16 → 2026-07-16 · 6 obs

○ 2026-07-16 13:42:40
● 2026-07-16 14:45:36
○ 2026-07-16 15:36:24
● 2026-07-16 20:38:10
○ 2026-07-16 22:44:38
○ 2026-07-17 17:30:34

●A216.150.1.1932026-07-16 → 2026-07-17 · 5 obs

○ 2026-07-16 07:56:04
● 2026-07-16 13:42:40
○ 2026-07-16 14:45:36
● 2026-07-16 23:24:32
● 2026-07-17 17:30:34

○A216.150.1.652026-07-16 → 2026-07-16 · 6 obs

○ 2026-07-16 14:45:36
● 2026-07-16 15:36:24
○ 2026-07-16 20:38:10
● 2026-07-16 21:32:14
○ 2026-07-16 23:24:32
○ 2026-07-17 17:30:34

○A216.150.16.12026-07-16 → 2026-07-16 · 7 obs

● 2026-07-16 07:56:04
○ 2026-07-16 13:42:40
● 2026-07-16 14:45:36
○ 2026-07-16 21:32:14
● 2026-07-16 22:44:38
○ 2026-07-16 23:24:32
○ 2026-07-17 17:30:34

○A216.150.16.1292026-07-16 → 2026-07-17 · 5 obs

● 2026-07-16 07:56:04
○ 2026-07-16 13:42:40
● 2026-07-17 00:04:18
○ 2026-07-17 06:02:26
○ 2026-07-17 17:30:34

○A216.150.16.652026-07-16 → 2026-07-16 · 6 obs

○ 2026-07-16 07:56:04
● 2026-07-16 13:42:40
○ 2026-07-16 14:45:36
● 2026-07-16 23:24:32
○ 2026-07-17 00:04:18
○ 2026-07-17 17:30:34

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:198.51.45.13

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for metrowatch.app (unsigned zone)

⏱️ Timing

Total: 312ms | Queries: -

📄 Records

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

Analysis

IP Addresses

metrowatch.app points to the IP addresses 216.150.1.1 and 216.150.1.193

competencefrancaise.com, robinhumphreys.nl, quotalavoro.it and two other host names share IP numbers with metrowatch.app.

Name Servers

metrowatch.app is delegated to two name servers: ns1.vercel-dns.com and ns2.vercel-dns.com.

metrowatch.app uses the same name servers as several other domains — among them ck.uk, pingpro.net, joyashin.com and two more.

There is at least partial name server overlap between metrowatch.app and other domains — donnavitan.com, ibrahimmizi.com, instant.im and two more among them.

ns1.vercel-dns.com and ns2.vercel-dns.com each resolve to two IP addresses: ns1.vercel-dns.com points to 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1, while ns2.vercel-dns.com points to 198.51.45.13 and 2a00:edc0:6259:7:13::2.

metrowatch.app - robtex.com

metrowatch.app

app