`billing-linkedin.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	`billinglinkedin-com01i.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::16^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr04cu00306.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr03cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01403.inbound.protection.outlook.com`
		A	2a01:111:f403:f90f::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr04cu00201.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.9.5^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mn2pr04cu00205.inbound.protection.outlook.com`
		A	52.101.41.26^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr03cu01702.inbound.protection.outlook.com`
		A	52.101.194.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00605.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`mscid=Qqr5BF3Ps4M/MzboUZneejZeNHQVgQ4XmgGMl7Z5RvQGoaxHZHjkumX0Hp6KRZOjmGgMJ0w...`
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=1774799792

Same first word

billing-linkedin.net

billing-linkedin.com

DNS History

5 records (5 active, 0 former)

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

● 2026-03-10 03:16:04
● 2026-03-29 16:07:26

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

● 2026-03-10 03:16:04
● 2026-03-29 16:07:26

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

● 2026-03-10 03:16:04
● 2026-03-29 16:07:26

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

● 2026-03-10 03:16:04
● 2026-03-29 16:07:26

●MXbillinglinkedin-com01i.mail.protection.outlook.com2026-03-10 → 2026-03-29 · 2 obs

● 2026-03-10 03:16:04
● 2026-03-29 16:07:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
billing-linkedin.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com	4 records

✅ Authoritative Response

Server:13.107.236.208

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for billing-linkedin.com (unsigned zone)

⏱️ Timing

Total: 95ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`billinglinkedin-com01i.mail.protection.o`
TXT	2	`v=spf1 include:spf.protection.outlook.co, mscid=Qqr5BF3Ps4M/MzboUZneejZeNHQVgQ4Xmg`
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

billing-linkedin.com's delegation is handled by four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

billing-linkedin.com partially shares name servers with other domains; examples include rydon.devon.sch.uk, luminoo.com, mgmarketing.ca, ofchu.com and spartagym.hr.