mpdaigle.com - dns.ninja

`mpdaigle.com`

DNSSEC	⚠️ Not signed
A	173.209.38.35^{🇨🇦 GTCOMM-36666173.209.32.0/19 Globotech Communications}
		PTR	`laurierweb.whc.ca`
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:c27::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f26.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 ip4:68.168.124.162 include:spf.web-dns1.com ip4:173.209.39.34 +a +mx ~all`
SOA	`ns1.whc.ca`sysadmin-internal@whc.ca 2026-06-19 #2

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

Previously MX for

mpdaigle.com

Subdomains

ns1.mpdaigle.com

Same first word

mpdaigle.com

Similar names

gpdemail.com

agilepdm.com

diaglepm.cn

paligmed.services

gplmedia.com

DNS History

16 records (9 active, 7 former)

○NSns1.mpdaigle.com2015-11-18 → 2020-02-07 · 5 obs

○ 2015-06-27 20:15:44
● 2015-11-18 17:41:20
● 2020-02-07 19:42:48
○ 2026-03-28 04:49:26
○ 2026-08-09 23:00:44

○NSns1.panelboxmanager.com2015-06-27 → 2015-06-27 · 3 obs

● 2015-06-27 20:15:44
○ 2015-11-18 17:41:20
○ 2026-08-09 23:00:44

●NSns1.whc.ca2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

○NSns2.panelboxmanager.com2015-06-27 → 2015-06-27 · 3 obs

● 2015-06-27 20:15:44
○ 2015-11-18 17:41:20
○ 2026-08-09 23:00:44

●NSns2.whc.ca2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●NSns3.whc.ca2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●MXalt1.aspmx.l.google.com2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●MXalt2.aspmx.l.google.com2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●MXalt3.aspmx.l.google.com2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●MXalt4.aspmx.l.google.com2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

●MXaspmx.l.google.com2026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

○MXmpdaigle.com2015-06-27 → 2015-06-27 · 3 obs

● 2015-06-27 20:15:44
○ 2015-11-18 17:41:20
○ 2026-08-09 23:00:44

○MXmx2.espacecode.com2015-11-18 → 2020-02-07 · 5 obs

○ 2015-06-27 20:15:44
● 2015-11-18 17:41:20
● 2020-02-07 19:42:48
○ 2026-03-28 04:49:26
○ 2026-08-09 23:00:44

○A167.114.101.52015-11-18 → 2020-02-07 · 5 obs

○ 2015-06-27 20:15:44
● 2015-11-18 17:41:20
● 2020-02-07 19:42:48
○ 2026-03-28 04:49:26
○ 2026-08-09 23:00:44

●A173.209.38.352026-03-28 → 2026-08-09 · 3 obs

○ 2020-02-07 19:42:48
● 2026-03-28 04:49:26
● 2026-08-09 23:00:44

○A72.55.186.482015-06-27 → 2015-06-27 · 3 obs

● 2015-06-27 20:15:44
○ 2015-11-18 17:41:20
○ 2026-08-09 23:00:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net...	-
mpdaigle.com	ns1.whc.ca, ns2.whc.ca, ns3.whc.ca	-

✅ Authoritative Response

Server:192.99.36.227

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mpdaigle.com (unsigned zone)

⏱️ Timing

Total: 1701ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.209.38.35`
NS	3	`ns1.whc.ca, ns3.whc.ca...`
MX	5	`alt4.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 ip4:68.168.124.162 include:spf.we`
SOA	1	`ns1.whc.ca sysadmin-internal.whc.ca`

Analysis

Hierarchy

mpdaigle.com serves as the parent of ns1.mpdaigle.com.

IP Addresses

mpdaigle.com has exactly one IP address — 173.209.38.35.

designwcnet.com, juliegoulet.com, swifthawkstudios.com plus two other host names have IP numbers in common with mpdaigle.com.

Name Servers

mpdaigle.com has three name servers — ns1.whc.ca, ns2.whc.ca and ns3.whc.ca.

mpdaigle.com has at least partial name server overlap with other domains, such as anniepiche.com, miecanada.com, cloud215675.mywhc.ca and two others.

These name servers tend to appear together with the name servers cloud1.whc.ca, cloud2.whc.ca and ns1.web-dns1.com, plus two others.

Each of the three hostnames points to exactly one IP address: ns1.whc.ca points to 173.209.49.178, ns2.whc.ca points to 67.43.237.129 and ns3.whc.ca points to 192.99.36.227.

Mail Servers

mpdaigle.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by mpdaigle.com are shared with other domains: ns500671.ns500742.ns500731.ns500731.ns500671.ns500705.ns500704.ns500291.ns500666.ns500153.tenderladiesbz.com, ns500671.ns500754.ns500671.ns500731.ns500704.ns500704.ns500731.ns500704.ns500671.ns500671.ns500649.ns500649.ns500688.ns500671.ns500649.lustychickser.com, ns500731.ns500731.ns500704.ns500742.ns500678.ns500688.ns500688.ns500705.ns500671.ns500671.ns500649.ns500291.ns500131.lustychickser.com and two others among them.

These mail servers are often deployed together with alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx3.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com resolves to 173.194.45.27 and 2607:f8b0:4004:c27::1a.

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

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

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

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