`richmonddevelopment.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`
		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	`richmonddevelopment-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy4pr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr03cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch4pr21cu00105.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr05cu00402.inbound.protection.outlook.com`
		A	52.101.11.9^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr02cu00101.inbound.protection.outlook.com`
		A	52.101.41.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
		A	52.101.42.18^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr03cu00302.inbound.protection.outlook.com`
		A	52.101.194.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr21cu00107.inbound.protection.outlook.com`
TXT	`mscid=ZpB4U4c6hitJRG1R9jUGKXiLIcSWBaj5d3/DTTb3vEcnIvCW5XR1PsLcjTJGHqFL5gxcSIZ...`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
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

richmonddevelopment.com

DNS History

14 records (5 active, 9 former)

○NSdns1.ttlc.net2015-08-02 → 2015-08-02 · 3 obs

● 2015-08-02 18:14:50
○ 2015-11-12 15:59:46
○ 2026-03-23 10:03:08

○NSdns3.ttlc.net2015-08-02 → 2015-08-02 · 3 obs

● 2015-08-02 18:14:50
○ 2015-11-12 15:59:46
○ 2026-03-23 10:03:08

○NSns0.cp.link2thecloud.com2015-11-12 → 2016-12-31 · 5 obs

○ 2015-08-02 18:14:50
● 2015-11-12 15:59:46
● 2016-12-31 01:02:36
○ 2026-02-21 01:48:00
○ 2026-03-23 10:03:08

●NSns1.bdm.microsoftonline.com2026-02-21 → 2026-03-23 · 3 obs

○ 2016-12-31 01:02:36
● 2026-02-21 01:48:00
● 2026-03-23 10:03:08

○NSns1.cp.link2thecloud.com2015-11-12 → 2016-12-31 · 5 obs

○ 2015-08-02 18:14:50
● 2015-11-12 15:59:46
● 2016-12-31 01:02:36
○ 2026-02-21 01:48:00
○ 2026-03-23 10:03:08

●NSns2.bdm.microsoftonline.com2026-02-21 → 2026-03-23 · 3 obs

○ 2016-12-31 01:02:36
● 2026-02-21 01:48:00
● 2026-03-23 10:03:08

●NSns3.bdm.microsoftonline.com2026-02-21 → 2026-03-23 · 3 obs

○ 2016-12-31 01:02:36
● 2026-02-21 01:48:00
● 2026-03-23 10:03:08

●NSns4.bdm.microsoftonline.com2026-02-21 → 2026-03-23 · 3 obs

○ 2016-12-31 01:02:36
● 2026-02-21 01:48:00
● 2026-03-23 10:03:08

○MXinbound10.mxlogic.net2015-08-02 → 2015-08-02 · 3 obs

● 2015-08-02 18:14:50
○ 2015-11-12 15:59:46
○ 2026-03-23 10:03:08

○MXinbound10.mxlogicmx.net2015-08-02 → 2015-08-02 · 3 obs

● 2015-08-02 18:14:50
○ 2015-11-12 15:59:46
○ 2026-03-23 10:03:08

●MXrichmonddevelopment-com.mail.protection.outlook.com2026-02-21 → 2026-03-23 · 3 obs

○ 2016-12-31 01:02:36
● 2026-02-21 01:48:00
● 2026-03-23 10:03:08

○MXserver1.inboundmx.com2015-11-12 → 2016-12-31 · 5 obs

○ 2015-08-02 18:14:50
● 2015-11-12 15:59:46
● 2016-12-31 01:02:36
○ 2026-02-21 01:48:00
○ 2026-03-23 10:03:08

○MXserver2.inboundmx.com2015-11-12 → 2016-12-31 · 5 obs

○ 2015-08-02 18:14:50
● 2015-11-12 15:59:46
● 2016-12-31 01:02:36
○ 2026-02-21 01:48:00
○ 2026-03-23 10:03:08

○A66.94.32.62015-08-02 → 2015-08-02 · 3 obs

● 2015-08-02 18:14:50
○ 2015-11-12 15:59:46
○ 2026-03-23 10:03:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
richmonddevelopment.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com	8 records

✅ Authoritative Response

Server:13.107.236.208

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for richmonddevelopment.com (unsigned zone)

⏱️ Timing

Total: 142ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 8

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

Analysis

Name Servers

richmonddevelopment.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 richmonddevelopment.com are shared with other domains, for instance spaceart.com.ua, upicpa-hk.com, linkedis.com, lingeetmaison.fr and uetbv.com.