`brazington.tech`

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`
		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`
		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	`brazington-tech.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c946::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch0pr04cu00603.inbound.protection.outlook.com`
		A	2a01:111:f403:f901::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00601.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm5pr02cu00203.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn8pr05cu00102.inbound.protection.outlook.com`
		A	52.101.8.42^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm6pr03cu00402.inbound.protection.outlook.com`
		A	52.101.11.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr0501cu00301.inbound.protection.outlook.com`
		A	52.101.40.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr05cu00100.inbound.protection.outlook.com`
		A	52.101.41.180^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr04cu00204.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`mscid=k/aYUKFCc4nhY01A6A8YKCvRcnRCKrs3Y1DH99KrooX2KeMIK3LyMT2X4ySp0ShDUHPSzie...`
TXT	`brazingtontemp.azurewebsites.net`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=1

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1776104353

Same first word

brazington.tech

DNS History

13 records (5 active, 8 former)

○NScont603385.earth.orderbox-dns.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○NScont603385.mars.orderbox-dns.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○NScont603385.mercury.orderbox-dns.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○NScont603385.venus.orderbox-dns.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

●NSns1.bdm.microsoftonline.com2026-03-26 → 2026-04-13 · 3 obs

○ 2017-11-28 09:13:46
● 2026-03-26 06:16:28
● 2026-04-13 18:28:42

●NSns2.bdm.microsoftonline.com2026-03-26 → 2026-04-13 · 3 obs

○ 2017-11-28 09:13:46
● 2026-03-26 06:16:28
● 2026-04-13 18:28:42

●NSns3.bdm.microsoftonline.com2026-03-26 → 2026-04-13 · 3 obs

○ 2017-11-28 09:13:46
● 2026-03-26 06:16:28
● 2026-04-13 18:28:42

●NSns4.bdm.microsoftonline.com2026-03-26 → 2026-04-13 · 3 obs

○ 2017-11-28 09:13:46
● 2026-03-26 06:16:28
● 2026-04-13 18:28:42

●MXbrazington-tech.mail.protection.outlook.com2026-03-26 → 2026-04-13 · 3 obs

○ 2017-11-28 09:13:46
● 2026-03-26 06:16:28
● 2026-04-13 18:28:42

○MXus2.mx1.mailhostbox.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○MXus2.mx2.mailhostbox.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○MXus2.mx3.mailhostbox.com2016-12-13 → 2017-11-28 · 4 obs

● 2016-12-13 01:36:04
● 2017-11-28 09:13:46
○ 2026-03-26 06:16:28
○ 2026-04-13 18:28:42

○A40.83.182.2062016-12-13 → 2016-12-13 · 3 obs

● 2016-12-13 01:36:04
○ 2017-11-28 09:13:46
○ 2026-04-13 18:28:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
brazington.tech	ns4.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com	-

✅ Authoritative Response

Server:208.84.5.208

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for brazington.tech (unsigned zone)

⏱️ Timing

Total: 242ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`brazington-tech.mail.protection.outlook.`
TXT	3	`v=spf1 include:spf.protection.outlook.co, mscid=k/aYUKFCc4nhY01A6A8YKCvRcnRCKrs3Y1...`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

Analysis

Name Servers

brazington.tech 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 brazington.tech are shared with other domains, for instance mikati.us, birsen.com.tr, shcmoks.com, shasta-llc.com and inovix.net.