paraquery.com - dns.ninja

`paraquery.com`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
A	216.150.1.129^{🇨🇦 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 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`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c17::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f26.1e100.net`
		A	2607:f8b0:4004:c17::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bl-in-f27.1e100.net`
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
		A	142.251.16.27^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f27.1e100.net`
		A	142.251.111.27^{🇺🇸 Google142.251.111.0/24}
			PTR	`bk-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.1e100.net`
MX	`ly3pe7cvf3hv6ublza2b7eewi3gi4d7wbt36g3a5qcvuafh2yu3q.mx-verification.google.com`⁽¹⁵⁾
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns1.vercel-dns.com`hostmaster@nsone.net serial=1717286042

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

Same first word

paraquery.com

DNS History

20 records (6 active, 14 former)

○NSdns1.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

○NSdns2.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

●NSns1.vercel-dns.com2026-06-01 → 2026-08-06 · 3 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
● 2026-08-06 22:34:46

●NSns2.vercel-dns.com2026-06-01 → 2026-08-06 · 3 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
● 2026-08-06 22:34:46

○MXeforward1.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

○MXeforward2.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

○MXeforward3.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

○MXeforward4.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

○MXeforward5.registrar-servers.com2017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

●MXly3pe7cvf3hv6ublza2b7eewi3gi4d7wbt36g3a5qcvuafh2yu3q.mx-verification.google.com2026-06-01 → 2026-08-06 · 3 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
● 2026-08-06 22:34:46

●MXsmtp.google.com2026-06-01 → 2026-08-06 · 3 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
● 2026-08-06 22:34:46

○A162.255.119.532017-05-09 → 2017-05-09 · 3 obs

● 2017-05-09 18:26:46
○ 2026-06-01 22:34:24
○ 2026-08-06 22:34:46

●A216.150.1.12026-06-01 → 2026-08-06 · 8 obs

○ 2026-06-01 22:34:24
● 2026-06-01 23:21:18
○ 2026-06-19 12:54:36
● 2026-06-24 09:55:16
○ 2026-07-08 10:25:28
● 2026-07-24 22:12:38
○ 2026-07-30 04:16:50
● 2026-08-06 22:34:46

●A216.150.1.1292026-06-19 → 2026-08-06 · 10 obs

○ 2026-06-01 23:21:18
● 2026-06-19 12:54:36
○ 2026-06-19 13:32:36
● 2026-06-19 14:51:58
○ 2026-06-19 15:31:16
● 2026-07-08 10:25:28
○ 2026-07-10 20:00:28
● 2026-07-13 11:14:58
○ 2026-08-05 02:07:26
● 2026-08-06 22:34:46

○A216.150.1.1932026-06-01 → 2026-07-30 · 11 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
○ 2026-06-01 23:21:18
● 2026-06-19 13:32:36
○ 2026-06-19 14:16:22
● 2026-06-19 15:31:16
○ 2026-07-08 10:25:28
● 2026-07-10 20:00:28
○ 2026-07-13 11:14:58
● 2026-07-30 04:16:50
○ 2026-08-06 22:34:46

○A216.150.1.652026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-19 13:32:36
● 2026-06-19 14:16:22
○ 2026-06-19 14:51:58
○ 2026-08-06 22:34:46

○A216.150.16.12026-07-13 → 2026-08-05 · 5 obs

○ 2026-07-10 20:00:28
● 2026-07-13 11:14:58
○ 2026-07-24 22:12:38
● 2026-08-05 02:07:26
○ 2026-08-06 22:34:46

○A216.150.16.1292026-06-01 → 2026-07-08 · 8 obs

○ 2026-06-01 22:34:24
● 2026-06-01 23:21:18
○ 2026-06-19 12:54:36
● 2026-06-19 15:31:16
○ 2026-06-24 09:55:16
● 2026-07-08 10:25:28
○ 2026-07-13 11:14:58
○ 2026-08-06 22:34:46

○A216.150.16.1932026-06-01 → 2026-06-19 · 8 obs

○ 2017-05-09 18:26:46
● 2026-06-01 22:34:24
○ 2026-06-01 23:21:18
● 2026-06-19 12:54:36
○ 2026-06-19 14:16:22
● 2026-06-19 14:51:58
○ 2026-06-19 15:31:16
○ 2026-08-06 22:34:46

○A216.150.16.652026-06-19 → 2026-06-19 · 4 obs

○ 2026-06-19 13:32:36
● 2026-06-19 14:16:22
○ 2026-06-19 14:51:58
○ 2026-08-06 22:34:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net...	-
paraquery.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 paraquery.com (unsigned zone)

⏱️ Timing

Total: 220ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`216.150.16.193, 216.150.1.1`
NS	2	`ns1.vercel-dns.com, ns2.vercel-dns.com`
MX	2	`smtp.google.com (pri: 1), ly3pe7cvf3hv6ublza2b7eewi3gi4d7wbt36g3a5`
TXT	1	`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

paraquery.com has two IP addresses: 216.150.1.1 and 216.150.1.129

Two other host names, along with ledgersso.created.app, reactnexus.com and birdfact.com, also share IP numbers with paraquery.com.

Name Servers

Two name servers handle the delegation for paraquery.com: ns1.vercel-dns.com and ns2.vercel-dns.com.

paraquery.com shares its NS records with other domains, for example keyboardkeytest.com, referly.so, eowisata.com and two others.

The name servers of paraquery.com overlap at least partially with those of other domains — among them actsofism.com, tgo-atx.com, jes.st and two more.

These name servers commonly co-occur with the name servers d.zeit-world.com, a.zeit-world.net, e.zeit-world.org and b.zeit-world.co.uk.

ns1.vercel-dns.com and ns2.vercel-dns.com both carry two IP addresses. The A records for ns1.vercel-dns.com are 198.51.44.13 and 2620:4d:4000:6259:7:13:0:1; the A records for ns2.vercel-dns.com are 198.51.45.13 and 2a00:edc0:6259:7:13::2.

Mail Servers

paraquery.com is served by two mail servers, smtp.google.com and ly3pe7cvf3hv6ublza2b7eewi3gi4d7wbt36g3a5qcvuafh2yu3q.mx-verification.google.com.

There is at least a partial MX overlap between paraquery.com and other domains, including urbanseed.info, agencjaflo.pl, ranora.com and two others.

The mail servers aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com are commonly used alongside these mail servers.

DNS names with 9 IP addresses:

smtp.google.com resolves to 142.251.16.26, 142.251.16.27 and 142.251.111.27 among others, with 6 other IP addresses in total.