capesizes.com - dns.ninja

`capesizes.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	`capesizes-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc09::^{🇸🇬 Microsoft2a01:111:f000::/36}
			PTR	`mail-sg2pr03cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::8^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tydpr03cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::4^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os8pr02cu00104.inbound.protection.outlook.com`
		A	52.101.124.117^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tydpr03cu00105.inbound.protection.outlook.com`
		A	52.101.137.0^{🇸🇬 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sg2pr03cu00500.inbound.protection.outlook.com`
		A	52.101.157.80^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os8pr02cu00100.inbound.protection.outlook.com`
TXT	`mscid=E22pyIKayu7cT2rH0QK7fwLtdWQ/ehWeuvkQ+GdNRiTLZlmQhi7youCMnNv/VVCqOEF8oNQ...`
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=1783230651

Same first word

capesizes.com

Similar names

spacesize.com

DNS History

9 records (5 active, 4 former)

●NSns1.bdm.microsoftonline.com2018-05-30 → 2026-07-05 · 3 obs

○ 2017-01-17 04:54:42
● 2018-05-30 20:14:08
● 2026-07-05 06:15:44

○NSns1.centrictelecom.com2015-06-04 → 2017-01-17 · 4 obs

● 2015-06-04 17:57:42
● 2017-01-17 04:54:42
○ 2018-05-30 20:14:08
○ 2026-07-05 06:15:44

●NSns2.bdm.microsoftonline.com2018-05-30 → 2026-07-05 · 3 obs

○ 2017-01-17 04:54:42
● 2018-05-30 20:14:08
● 2026-07-05 06:15:44

○NSns2.centrictelecom.com2015-06-04 → 2017-01-17 · 4 obs

● 2015-06-04 17:57:42
● 2017-01-17 04:54:42
○ 2018-05-30 20:14:08
○ 2026-07-05 06:15:44

●NSns3.bdm.microsoftonline.com2018-05-30 → 2026-07-05 · 3 obs

○ 2017-01-17 04:54:42
● 2018-05-30 20:14:08
● 2026-07-05 06:15:44

●NSns4.bdm.microsoftonline.com2018-05-30 → 2026-07-05 · 3 obs

○ 2017-01-17 04:54:42
● 2018-05-30 20:14:08
● 2026-07-05 06:15:44

●MXcapesizes-com.mail.protection.outlook.com2018-05-30 → 2026-07-05 · 3 obs

○ 2017-01-17 04:54:42
● 2018-05-30 20:14:08
● 2026-07-05 06:15:44

○MXcapesizes.com.bak-mx.uk0108.smtpbak.com2015-06-04 → 2017-01-17 · 4 obs

● 2015-06-04 17:57:42
● 2017-01-17 04:54:42
○ 2018-05-30 20:14:08
○ 2026-07-05 06:15:44

○MXcapesizes.com.pri-mx.uk0108.smtproutes.com2015-06-04 → 2017-01-17 · 4 obs

● 2015-06-04 17:57:42
● 2017-01-17 04:54:42
○ 2018-05-30 20:14:08
○ 2026-07-05 06:15:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net...	-
capesizes.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com	8 records

✅ Authoritative Response

Server:150.171.21.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 capesizes.com (unsigned zone)

⏱️ Timing

Total: 141ms | Queries: -

📄 Records

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

capesizes.com has four authoritative name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

capesizes.com has at least partial name server overlap with other domains, such as a4.com.au, jaegerinformatik.com, ebisz.com and two others.

ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com all point to exactly two IP numbers each: ns1.bdm.microsoftonline.com → 13.107.236.208 and 2603:1061:0:700::d0; ns2.bdm.microsoftonline.com → 150.171.21.208 and 2620:1ec:8ec:700::d0; ns3.bdm.microsoftonline.com → 204.14.183.208 and 2a01:111:4000:700::d0; ns4.bdm.microsoftonline.com → 208.84.5.208 and 2620:1ec:bda:700::d0.

Mail Servers

capesizes.com has one mail server: capesizes-com.mail.protection.outlook.com.

capesizes-com.mail.protection.outlook.com points to 6 IP numbers: 52.101.124.117, 52.101.137.0, 52.101.157.80 and 3 other.