problemsolved.ca - dns.ninja

`problemsolved.ca`

DNSSEC	⚠️ Not signed
A	44.253.207.149^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-253-207-149.us-west-2.compute.amazonaws.com`
NS	`ns1-05.azure-dns.com` ⭐
		A	2603:1061:0:700::5^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
		A	13.107.236.5^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
NS	`ns2-05.azure-dns.net`
		A	2620:1ec:8ec:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
		A	150.171.21.5^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
NS	`ns3-05.azure-dns.org`
		A	2a01:111:4000:700::5^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-05.azure-dns.org`
		A	204.14.183.5^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-05.azure-dns.org`
NS	`ns4-05.azure-dns.info`
		A	2620:1ec:bda:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
		A	208.84.5.5^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
MX	`problemsolved-ca.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c942::2^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yt3pr01cu00602.inbound.protection.outlook.com`
		A	2a01:111:f403:c942::3^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yt6pr01cu00103.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
		A	2a01:111:f403:c944::1^{🇨🇦 Microsoft2a01:111:f000::/36}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
		A	52.101.190.0^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yt5pr01cu00100.inbound.protection.outlook.com`
		A	52.101.190.3^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yt6pr01cu00103.inbound.protection.outlook.com`
		A	52.101.192.0^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yqzpr01cu00900.inbound.protection.outlook.com`
		A	52.101.192.1^{🇨🇦 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-yqzpr01cu01001.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-05.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

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

Subdomains

www.problemsolved.ca

Same first word

DNS History

9 records (6 active, 3 former)

●NSns1-05.azure-dns.com2026-06-27 → 2026-06-27 · 3 obs

○ 2026-03-29 16:09:06
● 2026-06-27 10:33:28
● 2026-06-27 10:33:30

○NSns1.problemsolvedhosting.com2015-07-17 → 2026-03-29 · 4 obs

● 2015-07-17 06:49:12
● 2026-03-29 16:09:06
○ 2026-06-27 10:33:28
○ 2026-06-27 10:33:30

●NSns2-05.azure-dns.net2026-06-27 → 2026-06-27 · 3 obs

○ 2026-03-29 16:09:06
● 2026-06-27 10:33:28
● 2026-06-27 10:33:30

○NSns2.problemsolvedhosting.com2015-07-17 → 2026-03-29 · 4 obs

● 2015-07-17 06:49:12
● 2026-03-29 16:09:06
○ 2026-06-27 10:33:28
○ 2026-06-27 10:33:30

●NSns3-05.azure-dns.org2026-06-27 → 2026-06-27 · 3 obs

○ 2026-03-29 16:09:06
● 2026-06-27 10:33:28
● 2026-06-27 10:33:30

●NSns4-05.azure-dns.info2026-06-27 → 2026-06-27 · 3 obs

○ 2026-03-29 16:09:06
● 2026-06-27 10:33:28
● 2026-06-27 10:33:30

●MXproblemsolved-ca.mail.protection.outlook.com2015-07-17 → 2026-06-27 · 2 obs

● 2015-07-17 06:49:12
● 2026-06-27 10:33:30

○A173.199.182.1922015-07-17 → 2026-03-29 · 4 obs

● 2015-07-17 06:49:12
● 2026-03-29 16:09:06
○ 2026-06-27 10:33:28
○ 2026-06-27 10:33:30

●A44.253.207.1492026-06-27 → 2026-06-27 · 3 obs

○ 2026-03-29 16:09:06
● 2026-06-27 10:33:28
● 2026-06-27 10:33:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ca	d.ca-servers.ca, any.ca-servers.ca, c.ca-servers.ca, j.ca-servers.ca	-
problemsolved.ca	ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns4-05.azure-dns.info	-

✅ Authoritative Response

Server:208.84.5.5

NS records: ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns4-05.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for problemsolved.ca (unsigned zone)

⏱️ Timing

Total: 826ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`44.253.207.149`
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
MX	1	`problemsolved-ca.mail.protection.outlook`
TXT	1	`v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1-05.azure-dns.com azuredns-hostmaster`

Analysis

Hierarchy

problemsolved.ca serves as the parent of www.problemsolved.ca.

IP Addresses

problemsolved.ca directs to one IP number, which is 44.253.207.149.

Additional host names — including ec2-44-253-207-149.us-west-2.compute.amazonaws.com and www.problemsolved.ca.cdn.cloudflare.net — share IP numbers with problemsolved.ca.

Name Servers

The domain problemsolved.ca is delegated to these four name servers: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

problemsolved.ca has at least partial name server overlap with other domains, such as dredge.be, sper.qld.gov.au, cloudfit.tech and two others.

ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org all point to exactly two IP numbers each: ns1-05.azure-dns.com → 13.107.236.5 and 2603:1061:0:700::5; ns4-05.azure-dns.info → 208.84.5.5 and 2620:1ec:bda:700::5; ns2-05.azure-dns.net → 150.171.21.5 and 2620:1ec:8ec:700::5; ns3-05.azure-dns.org → 204.14.183.5 and 2a01:111:4000:700::5.

Mail Servers

problemsolved.ca routes its mail through a single mail server, problemsolved-ca.mail.protection.outlook.com.

problemsolved-ca.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.190.0, 52.101.190.3 and 52.101.192.0, along with 5 other.