supaquick.net - dns.ninja

`supaquick.net`

DNSSEC	⚠️ Not signed
A	2a01:7e00:e000:3f7::^{🇬🇧 AKAMAI-LINODE-AP2a01:7e00::/32 Akamai Technologies}
		PTR	`web.forwarder.lexsynergy.com`
A	178.79.178.218^{🇬🇧 AKAMAI-LINODE-AP178.79.128.0/18 Akamai Technologies}
NS	`ns1.lexsynergy.net` ⭐
		A	2a01:3f1:854::53^{🇸🇪 NETNOD-IX2a01:3f1:800::/38 NDS EUROPE-1 $Id: route6_2a01:3f1:0800::-38,v 1.1 2019/10/04 10:07:35 mem Exp $}
			PTR	`ns4.ac1.lexsynergy.com`
		A	194.58.196.54^{🇸🇪 NETNOD-IX194.58.196.0/24 NDS E}
			PTR	`ns4.ac1.lexsynergy.com`
NS	`ns2.lexsynergy.us`
		A	2600:3c03:e000:958::^{🇺🇸 AKAMAI-LINODE-AP2600:3c03::/32 Akamai Technologies}
		A	45.79.129.26^{🇺🇸 AKAMAI-LINODE-AP45.79.128.0/19 Akamai Technologies}
			PTR	`ns2.lexsynergy.us`
NS	`ns3.lexsynergy.info`
		A	2a00:1a48:7807:103:be76:4eff:fe08:d749^{🇬🇧 RACKSPACE-LON2a00:1a48::/32 Rackspace}
			PTR	`ns3.lexsynergy.info`
		A	162.13.177.111^{🇬🇧 RACKSPACE-LON162.13.0.0/16 Rackspace}
			PTR	`ns3.lexsynergy.info`
SOA	`ns1.lexsynergy.net`dnsmaster@lexsynergy.com serial=18

`net`

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

Same first word

supaquick.com

supaquick.net

supaquick.mobi

supaquick.com.na

supaquick.co.na

supaquick.co.za

DNS History

18 records (5 active, 13 former)

●NSns1.lexsynergy.net2026-06-12 → 2026-08-04 · 3 obs

○ 2017-03-25 13:35:08
● 2026-06-12 14:10:14
● 2026-08-04 10:12:36

●NSns2.lexsynergy.us2026-06-12 → 2026-08-04 · 3 obs

○ 2017-03-25 13:35:08
● 2026-06-12 14:10:14
● 2026-08-04 10:12:36

●NSns3.lexsynergy.info2026-06-12 → 2026-08-04 · 3 obs

○ 2017-03-25 13:35:08
● 2026-06-12 14:10:14
● 2026-08-04 10:12:36

○NSns63.domaincontrol.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○NSns64.domaincontrol.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXalt1.aspmx.l.google.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXalt2.aspmx.l.google.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXaspmx.l.google.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXaspmx2.googlemail.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXaspmx3.googlemail.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXaspmx4.googlemail.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○MXaspmx5.googlemail.com2015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

●A178.79.178.2182026-06-12 → 2026-08-04 · 3 obs

○ 2017-03-25 13:35:08
● 2026-06-12 14:10:14
● 2026-08-04 10:12:36

○A216.239.32.212015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○A216.239.34.212015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○A216.239.36.212015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

○A216.239.38.212015-05-29 → 2017-03-25 · 4 obs

● 2015-05-29 17:35:18
● 2017-03-25 13:35:08
○ 2026-06-12 14:10:14
○ 2026-08-04 10:12:36

●A2a01:7e00:e000:3f7::2026-06-12 → 2026-08-04 · 3 obs

○ 2017-03-25 13:35:08
● 2026-06-12 14:10:14
● 2026-08-04 10:12:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
supaquick.net	ns1.lexsynergy.net, ns2.lexsynergy.us, ns3.lexsynergy.info	2 records

✅ Authoritative Response

Server:185.42.137.105

NS records: ns1.lexsynergy.net, ns2.lexsynergy.us, ns3.lexsynergy.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for supaquick.net (unsigned zone)

⏱️ Timing

Total: 641ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.79.178.218`
AAAA	1	`2a01:7e00:e000:3f7::`
NS	3	`ns1.lexsynergy.net, ns2.lexsynergy.us...`
SOA	1	`ns1.lexsynergy.net dnsmaster.lexsynergy.`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.lexsynergy.net, ns1.lexsynergy.net)

Analysis

IP Addresses

supaquick.net directs to two IP numbers, 178.79.178.218 and 2a01:7e00:e000:3f7::

schindler.link, bidvest-bank.eu, xn--fiqs8sku3c1a.com plus two other host names have IP numbers in common with supaquick.net.

Name Servers

supaquick.net carries NS records delegating to ns3.lexsynergy.info, ns1.lexsynergy.net and ns2.lexsynergy.us.

supaquick.net partially shares its NS delegation with several other domains, including easternbank.financial, otterbox.com.hk, bitvestvoter.com and two others.

ns3.lexsynergy.info, ns1.lexsynergy.net and ns2.lexsynergy.us are three hostnames that each resolve to a pair of IP addresses: ns3.lexsynergy.info to 162.13.177.111 and 2a00:1a48:7807:103:be76:4eff:fe08:d749, ns1.lexsynergy.net to 194.58.196.54 and 2a01:3f1:854::53, and ns2.lexsynergy.us to 45.79.129.26 and 2600:3c03:e000:958::.