canpools.com - dns.ninja

`canpools.com`

DNSSEC	⚠️ Not signed
A	107.180.114.220^{🇺🇸 AS398101107.180.112.0/22}
		PTR	`220.114.180.107.host.secureserver.net`
NS	`ns65.domaincontrol.com` ⭐
		A	2603:5:2164::2b^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns65.domaincontrol.com`
		A	97.74.102.43^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns65.domaincontrol.com`
NS	`ns66.domaincontrol.com`
		A	2603:5:2264::2b^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns66.domaincontrol.com`
		A	173.201.70.43^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns66.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.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.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.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.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`D4678241`
SOA	`ns65.domaincontrol.com`dns@jomax.net 2024-05-28 #1

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

Same first word

canpools.com

Similar names

DNS History

16 records (8 active, 8 former)

○NSns47.domaincontrol.com2017-04-08 → 2017-04-08 · 4 obs

○ 2016-09-09 05:13:28
● 2017-04-08 11:48:14
○ 2026-02-15 17:44:08
○ 2026-07-12 07:27:52

○NSns48.domaincontrol.com2017-04-08 → 2017-04-08 · 4 obs

○ 2016-09-09 05:13:28
● 2017-04-08 11:48:14
○ 2026-02-15 17:44:08
○ 2026-07-12 07:27:52

○NSns51.domaincontrol.com2015-08-13 → 2016-09-09 · 4 obs

● 2015-08-13 23:03:10
● 2016-09-09 05:13:28
○ 2017-04-08 11:48:14
○ 2026-07-12 07:27:52

○NSns52.domaincontrol.com2015-08-13 → 2016-09-09 · 4 obs

● 2015-08-13 23:03:10
● 2016-09-09 05:13:28
○ 2017-04-08 11:48:14
○ 2026-07-12 07:27:52

●NSns65.domaincontrol.com2026-02-15 → 2026-07-12 · 3 obs

○ 2017-04-08 11:48:14
● 2026-02-15 17:44:08
● 2026-07-12 07:27:52

●NSns66.domaincontrol.com2026-02-15 → 2026-07-12 · 3 obs

○ 2017-04-08 11:48:14
● 2026-02-15 17:44:08
● 2026-07-12 07:27:52

●MXalt1.aspmx.l.google.com2015-08-13 → 2026-07-12 · 2 obs

● 2015-08-13 23:03:10
● 2026-07-12 07:27:52

●MXalt2.aspmx.l.google.com2015-08-13 → 2026-07-12 · 2 obs

● 2015-08-13 23:03:10
● 2026-07-12 07:27:52

●MXalt3.aspmx.l.google.com2017-04-08 → 2026-07-12 · 3 obs

○ 2016-09-09 05:13:28
● 2017-04-08 11:48:14
● 2026-07-12 07:27:52

●MXalt4.aspmx.l.google.com2026-02-15 → 2026-07-12 · 3 obs

○ 2017-04-08 11:48:14
● 2026-02-15 17:44:08
● 2026-07-12 07:27:52

●MXaspmx.l.google.com2015-08-13 → 2026-07-12 · 2 obs

● 2015-08-13 23:03:10
● 2026-07-12 07:27:52

○MXaspmx2.googlemail.com2015-08-13 → 2016-09-09 · 4 obs

● 2015-08-13 23:03:10
● 2016-09-09 05:13:28
○ 2017-04-08 11:48:14
○ 2026-07-12 07:27:52

○MXaspmx3.googlemail.com2015-08-13 → 2016-09-09 · 4 obs

● 2015-08-13 23:03:10
● 2016-09-09 05:13:28
○ 2017-04-08 11:48:14
○ 2026-07-12 07:27:52

●A107.180.114.2202026-02-15 → 2026-07-12 · 3 obs

○ 2017-04-08 11:48:14
● 2026-02-15 17:44:08
● 2026-07-12 07:27:52

○A184.168.47.2252015-08-13 → 2016-09-09 · 4 obs

● 2015-08-13 23:03:10
● 2016-09-09 05:13:28
○ 2017-04-08 11:48:14
○ 2026-07-12 07:27:52

○A50.62.174.1322017-04-08 → 2017-04-08 · 4 obs

○ 2016-09-09 05:13:28
● 2017-04-08 11:48:14
○ 2026-02-15 17:44:08
○ 2026-07-12 07:27:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
canpools.com	ns66.domaincontrol.com, ns65.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.102.43

NS records: ns66.domaincontrol.com, ns65.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for canpools.com (unsigned zone)

⏱️ Timing

Total: 121ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.180.114.220`
NS	2	`ns65.domaincontrol.com, ns66.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 0), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`D4678241`
SOA	1	`ns65.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns66.domaincontrol.com, ns66.domaincontrol.com, ns65.domaincontrol.com...)

Analysis

IP Addresses

canpools.com directs to one IP number, which is 107.180.114.220.

Among the host names that share IP numbers with canpools.com are thepresentperfect.org, theleafempire.com, mail.e3motion.com and two others.

Name Servers

canpools.com has two authoritative name servers — ns65.domaincontrol.com and ns66.domaincontrol.com.

canpools.com has the same name server delegation as a number of other domains, such as iamhere.today, talentmeritocracy.com, pretautocredit.ca and two more.

The name servers for canpools.com overlap at least partially with those of other domains — for example zerospese.org.

Both ns65.domaincontrol.com and ns66.domaincontrol.com have two IP addresses each. ns65.domaincontrol.com resolves to 97.74.102.43 and 2603:5:2164::2b; ns66.domaincontrol.com resolves to 173.201.70.43 and 2603:5:2264::2b.

Mail Servers

canpools.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

canpools.com shares at least some of its mail servers with other domains — for example ns500742.ns500671.ns500742.ns500671.ns500754.ns500671.ns500754.ns500704.ns500671.ns500678.ns500291.ns500649.ns500649.ns500291.ns500131.lustychickser.com, ns500698.ns500698.ns500759.ns500758.ns500758.ns500736.ns500698.ns500735.ns500736.ns500736.ns500735.ns500735.ns500698.ns500576.ns500686.ns500576.ns500576.trackreceptor.com, ns500759.ns500759.ns500698.ns500759.ns500735.ns500735.ns500698.ns500698.ns500708.ns500576.ns500619.ns500686.ns500619.ns500576.trackreceptor.com and two more.

It is common to find these mail servers paired with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 more.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.