`ur-solution.com`

DNSSEC	⚠️ Not signed
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com` ⚠️ Not in parent delegation
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`ursolution-com0e.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::14^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
		A	2a01:111:f403:f90c::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr03cu00100.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.11.10^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr03cu00202.inbound.protection.outlook.com`
		A	52.101.40.6^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy1pr03cu00106.inbound.protection.outlook.com`
		A	52.101.41.54^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00506.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`mscid=go6fIHavnRxUbuJ49oTu91Gyv8UfBiLwVqhMQaq060kZO+PXAKD1Epc4c/koRszVz0xtYjf...`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=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=1771291435

Same first word

ur-solution.com

DNS History

14 records (5 active, 9 former)

○NSdns4.intergroup.net2015-05-29 → 2017-08-19 · 4 obs

○ 2008-12-31 19:30:48
● 2015-05-29 03:00:06
● 2017-08-19 09:51:22
○ 2026-03-02 16:41:38

○NSdns5.intergroup.net2015-05-29 → 2017-08-19 · 4 obs

○ 2008-12-31 19:30:48
● 2015-05-29 03:00:06
● 2017-08-19 09:51:22
○ 2026-03-02 16:41:38

●NSns1.bdm.microsoftonline.com2026-03-02 → 2026-03-02 · 2 obs

○ 2017-08-19 09:51:22
● 2026-03-02 16:41:38

○NSns1.hostmonster.com2008-12-31 → 2008-12-31 · 3 obs

● 2008-12-31 19:30:48
○ 2015-05-29 03:00:06
○ 2026-03-02 16:41:38

●NSns2.bdm.microsoftonline.com2026-03-02 → 2026-03-02 · 2 obs

○ 2017-08-19 09:51:22
● 2026-03-02 16:41:38

○NSns2.hostmonster.com2008-12-31 → 2008-12-31 · 3 obs

● 2008-12-31 19:30:48
○ 2015-05-29 03:00:06
○ 2026-03-02 16:41:38

●NSns3.bdm.microsoftonline.com2026-03-02 → 2026-03-02 · 2 obs

○ 2017-08-19 09:51:22
● 2026-03-02 16:41:38

●NSns4.bdm.microsoftonline.com2026-03-02 → 2026-03-02 · 2 obs

○ 2017-08-19 09:51:22
● 2026-03-02 16:41:38

○MXaspmx.l.google.com2016-04-14 → 2017-08-19 · 4 obs

○ 2016-01-24 19:20:40
● 2016-04-14 23:12:10
● 2017-08-19 09:51:22
○ 2026-03-02 16:41:38

○MXmail.ur-solution.com2016-01-24 → 2016-01-24 · 4 obs

○ 2015-05-29 03:00:06
● 2016-01-24 19:20:40
○ 2016-04-14 23:12:10
○ 2026-03-02 16:41:38

○MXur-solution.com2008-12-31 → 2008-12-31 · 3 obs

● 2008-12-31 19:30:48
○ 2015-05-29 03:00:06
○ 2026-03-02 16:41:38

●MXursolution-com0e.mail.protection.outlook.com2026-03-02 → 2026-03-02 · 2 obs

○ 2017-08-19 09:51:22
● 2026-03-02 16:41:38

○A59.124.120.2532015-05-29 → 2017-08-19 · 4 obs

○ 2008-12-31 19:30:48
● 2015-05-29 03:00:06
● 2017-08-19 09:51:22
○ 2026-03-02 16:41:38

○A74.220.215.752008-12-31 → 2008-12-31 · 3 obs

● 2008-12-31 19:30:48
○ 2015-05-29 03:00:06
○ 2026-03-02 16:41:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, m.gtld-servers.net, e.gtld-servers.net, i.gtld-servers.net...	-
ur-solution.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com	4 records

✅ Authoritative Response

Server: 150.171.21.208

NS records: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ur-solution.com (unsigned zone)

⏱️ Timing

Total: 172ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`ursolution-com0e.mail.protection.outlook`
TXT	2	`v=spf1 include:spf.protection.outlook.co, mscid=go6fIHavnRxUbuJ49oTu91Gyv8UfBiLwVq`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns1.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...)

Analysis

Name Servers

ur-solution.com is delegated to four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

At least part of the name servers for ur-solution.com are shared with other domains, for instance nhjdobrasil.com, tradewagon.com, globallsoccer.com, microjournaler.com and newhouse.be.