botframework.net - dns.ninja

`botframework.net`

DNSSEC	⚠️ Not signed
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	`botframework-net.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr03cu01602.inbound.protection.outlook.com`
		A	2a01:111:f403:c902::7^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr02cu00107.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy5pr05cu00101.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.8.51^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm1pr04cu00203.inbound.protection.outlook.com`
		A	52.101.11.19^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr04cu00203.inbound.protection.outlook.com`
		A	52.101.194.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch5pr02cu00401.inbound.protection.outlook.com`
TXT	`MS=ms87129475`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-05.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`net`

	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=1781415960

Same first word

botframework.us

botframework.net

botframework.com

botframework.ai

Similar names

frameworkbot.com

DNS History

9 records (5 active, 4 former)

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

○ 2020-03-11 05:30:08
● 2026-02-27 03:52:48
● 2026-06-14 05:47:24

○NSns1.msft.net2017-01-03 → 2020-03-11 · 4 obs

● 2017-01-03 11:43:34
● 2020-03-11 05:30:08
○ 2026-02-27 03:52:48
○ 2026-06-14 05:47:24

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

○ 2020-03-11 05:30:08
● 2026-02-27 03:52:48
● 2026-06-14 05:47:24

○NSns2.msft.net2017-01-03 → 2020-03-11 · 4 obs

● 2017-01-03 11:43:34
● 2020-03-11 05:30:08
○ 2026-02-27 03:52:48
○ 2026-06-14 05:47:24

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

○ 2020-03-11 05:30:08
● 2026-02-27 03:52:48
● 2026-06-14 05:47:24

○NSns3.msft.net2017-01-03 → 2020-03-11 · 4 obs

● 2017-01-03 11:43:34
● 2020-03-11 05:30:08
○ 2026-02-27 03:52:48
○ 2026-06-14 05:47:24

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

○ 2020-03-11 05:30:08
● 2026-02-27 03:52:48
● 2026-06-14 05:47:24

○NSns4.msft.net2017-01-03 → 2020-03-11 · 4 obs

● 2017-01-03 11:43:34
● 2020-03-11 05:30:08
○ 2026-02-27 03:52:48
○ 2026-06-14 05:47:24

●MXbotframework-net.mail.protection.outlook.com2017-01-03 → 2026-06-14 · 2 obs

● 2017-01-03 11:43:34
● 2026-06-14 05:47:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
botframework.net	ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.5

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for botframework.net (unsigned zone)

⏱️ Timing

Total: 407ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-05.azure-dns.net, ns2-05.azure-dns.net)

Analysis

Name Servers

botframework.net is delegated to four name servers, ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

botframework.net has at least partial name server overlap with other domains, such as unianhanguera.com.br, greenorg.net, 181.62.20.in-addr.arpa and two others.

It is common to find these name servers paired with the name servers ns1-04.azure-dns.com.

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

botframework.net has one mail server: botframework-net.mail.protection.outlook.com.

botframework-net.mail.protection.outlook.com points to 8 IP numbers: 52.101.8.42, 52.101.8.51, 52.101.11.19 and 5 other.