biperformance.ca - dns.ninja

`biperformance.ca`

DNSSEC	⚠️ Not signed
A	158.69.168.192^{🇨🇦 OVH158.69.0.0/16 Hosting route}
NS	`ns1.whc.ca` ⭐
		A	173.209.49.178^{🇨🇦 GTCOMM-36666173.209.32.0/19 Globotech Communications}
			PTR	`ns1.web-dns1.com`
NS	`ns2.whc.ca`
		A	67.43.237.129^{🇨🇦 GTCOMM-3666667.43.237.0/24 GloboTech}
NS	`ns3.whc.ca`
		A	192.99.36.227^{🇨🇦 OVH192.99.0.0/16 Hosting route}
			PTR	`ns3.whc.ca`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.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}
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.27^{🇺🇸 Google172.253.116.0/24}
MX	`al31.aspmx.l.google.com`⁽¹⁰⁾
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.26^{🇺🇸 Google172.253.0.0/16}
TXT	`v=spf1 ip4:51.161.14.84 include:spf.web-dns1.com +mx +a +ip4:54.39.100.142 ~all`
SOA	`ns1.whc.ca`sysadmin-internal@whc.ca 2026-06-09 #0

`ca`

	DNSSEC	🔒 Signed (DS record present)
	NS	`prd-czp-05.corp.cira.ca` ⭐
	NS	`any.ca-servers.ca`
	NS	`c.ca-servers.ca`
	NS	`d.ca-servers.ca`
	NS	`j.ca-servers.ca`
	SOA	`prd-czp-05.corp.cira.ca`admin-dns@cira.ca serial=2606282100

Previously MX for

biperformance.ca

Same first word

biperformance.com

biperformance.ca

DNS History

22 records (9 active, 13 former)

○NSns-cloud-e1.googledomains.com2019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

○NSns-cloud-e2.googledomains.com2019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

○NSns-cloud-e3.googledomains.com2019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

○NSns-cloud-e4.googledomains.com2019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

○NSns1.superwebhost.com2016-03-16 → 2016-12-27 · 5 obs

○ 2015-12-02 19:40:34
● 2016-03-16 06:20:18
● 2016-12-27 08:44:22
○ 2019-12-30 12:09:04
○ 2026-06-28 21:38:24

●NSns1.whc.ca2026-03-26 → 2026-06-28 · 3 obs

○ 2019-12-30 12:09:04
● 2026-03-26 12:19:18
● 2026-06-28 21:38:24

○NSns17.van-dns.com2015-08-05 → 2015-12-02 · 4 obs

● 2015-08-05 00:57:10
● 2015-12-02 19:40:34
○ 2016-03-16 06:20:18
○ 2026-06-28 21:38:24

○NSns18.van-dns.com2015-08-05 → 2015-12-02 · 4 obs

● 2015-08-05 00:57:10
● 2015-12-02 19:40:34
○ 2016-03-16 06:20:18
○ 2026-06-28 21:38:24

○NSns2.superwebhost.com2016-03-16 → 2016-12-27 · 5 obs

○ 2015-12-02 19:40:34
● 2016-03-16 06:20:18
● 2016-12-27 08:44:22
○ 2019-12-30 12:09:04
○ 2026-06-28 21:38:24

●NSns2.whc.ca2026-03-26 → 2026-06-28 · 3 obs

○ 2019-12-30 12:09:04
● 2026-03-26 12:19:18
● 2026-06-28 21:38:24

●NSns3.whc.ca2026-03-26 → 2026-06-28 · 3 obs

○ 2019-12-30 12:09:04
● 2026-03-26 12:19:18
● 2026-06-28 21:38:24

●MXal31.aspmx.l.google.com2026-03-26 → 2026-06-28 · 3 obs

○ 2019-12-30 12:09:04
● 2026-03-26 12:19:18
● 2026-06-28 21:38:24

●MXalt1.aspmx.l.google.com2019-12-30 → 2026-06-28 · 3 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
● 2026-06-28 21:38:24

●MXalt2.aspmx.l.google.com2019-12-30 → 2026-06-28 · 3 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
● 2026-06-28 21:38:24

○MXalt3.aspmx.l.google.com2019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

●MXalt4.aspmx.l.google.com2019-12-30 → 2026-06-28 · 3 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
● 2026-06-28 21:38:24

●MXaspmx.l.google.com2019-12-30 → 2026-06-28 · 3 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
● 2026-06-28 21:38:24

○MXbiperformance.ca2015-08-05 → 2016-12-27 · 4 obs

● 2015-08-05 00:57:10
● 2016-12-27 08:44:22
○ 2019-12-30 12:09:04
○ 2026-06-28 21:38:24

●A158.69.168.1922026-03-26 → 2026-06-28 · 3 obs

○ 2019-12-30 12:09:04
● 2026-03-26 12:19:18
● 2026-06-28 21:38:24

○A208.92.161.192016-03-16 → 2016-12-27 · 5 obs

○ 2015-12-02 19:40:34
● 2016-03-16 06:20:18
● 2016-12-27 08:44:22
○ 2019-12-30 12:09:04
○ 2026-06-28 21:38:24

○A35.192.23.262019-12-30 → 2019-12-30 · 4 obs

○ 2016-12-27 08:44:22
● 2019-12-30 12:09:04
○ 2026-03-26 12:19:18
○ 2026-06-28 21:38:24

○A64.40.123.332015-08-05 → 2015-12-02 · 4 obs

● 2015-08-05 00:57:10
● 2015-12-02 19:40:34
○ 2016-03-16 06:20:18
○ 2026-06-28 21:38:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ca	c.ca-servers.ca, d.ca-servers.ca, j.ca-servers.ca, any.ca-servers.ca	-
biperformance.ca	ns1.whc.ca, ns2.whc.ca, ns3.whc.ca	3 records

✅ Authoritative Response

Server:67.43.237.129

NS records: ns1.whc.ca, ns2.whc.ca, ns3.whc.ca

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for biperformance.ca (unsigned zone)

⏱️ Timing

Total: 453ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`158.69.168.192`
NS	3	`ns3.whc.ca, ns1.whc.ca...`
MX	5	`ALT4.ASPMX.L.GOOGLE.COM (pri: 10), ALT1.ASPMX.L.GOOGLE.COM (pri: 5)...`
TXT	1	`v=spf1 ip4:51.161.14.84 include:spf.web-`
SOA	1	`ns1.whc.ca sysadmin-internal.whc.ca`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns1.whc.ca, ns2.whc.ca, ns3.whc.ca)

Analysis

IP Addresses

biperformance.ca directs to one IP number, which is 158.69.168.192.

Among the host names that share IP numbers with biperformance.ca are smid.com, calendarofevents.ca, v3m.ca and two others.

Name Servers

biperformance.ca is served by three name servers: ns1.whc.ca, ns2.whc.ca and ns3.whc.ca.

biperformance.ca shares at least some of its name servers with other domains, including haunerland.com, techni-data.com, aubergeanimour.com and two others.

These name servers are routinely co-deployed with the name servers cloud1.whc.ca, cloud2.whc.ca, ns1.web-dns1.com and two others.

ns1.whc.ca has IP address 173.209.49.178, ns2.whc.ca has IP address 67.43.237.129 and ns3.whc.ca has IP address 192.99.36.227 — one address each.

Mail Servers

Mail for biperformance.ca is handled by five mail servers, namely aspmx.l.google.com, al31.aspmx.l.google.com, alt1.aspmx.l.google.com and two others.

biperformance.ca shares at least some of its mail servers with other domains — for example ns500765.ns500693.ns500699.ns500699.ns500734.ns500699.ns500699.ns500693.ns500699.ns500588.ns500699.ns500588.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, ns500765.ns500765.ns500699.ns500699.ns500734.ns500588.ns500683.ns500588.ns500683.ns500588.ns500612.ns500588.ns500632.ns500612.ns500578.ns500110.dtrkdll.com, ns500742.ns500754.ns500731.ns500742.ns500671.ns500754.ns500704.ns500704.ns500704.ns500704.ns500291.lustychickser.com and two more.

These mail servers tend to be used in conjunction with alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.com and two additional mail servers.

The host names aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and alt4.aspmx.l.google.com each resolve to two IP addresses: aspmx.l.google.com resolves to 142.251.163.26 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.27 and 2a00:1450:400b:c02::1a; alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.