`bridon-bekaert.com`

DNSSEC	⚠️ Not signed
A	20.76.227.109^{🇳🇱 Microsoft20.64.0.0/10}
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	`bridonbekaert-com01e.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:ca04::2^{🇮🇪 Microsoft2a01:111:f000::/36}
			PTR	`mail-du2pr03cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:ca04::7^{🇮🇪 Microsoft2a01:111:f000::/36}
			PTR	`mail-db4pr02cu00307.inbound.protection.outlook.com`
		A	2a01:111:f403:ca04::d^{🇮🇪 Microsoft2a01:111:f000::/36}
			PTR	`mail-db6pr03cu00105.inbound.protection.outlook.com`
		A	2a01:111:f403:ca09::d^{🇳🇱 Microsoft2a01:111:f000::/36}
			PTR	`mail-as9pr05cu01305.inbound.protection.outlook.com`
		A	52.101.68.3^{🇮🇪 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-db7pr03cu00403.inbound.protection.outlook.com`
		A	52.101.73.4^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-am0pr83cu00404.inbound.protection.outlook.com`
		A	52.101.73.24^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-as8pr05cu00300.inbound.protection.outlook.com`
		A	52.101.73.153^{🇳🇱 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-as8pr05cu00401.inbound.protection.outlook.com`
TXT	`MS=ms65380278`
TXT	`MS=ms62873117`
TXT	`google-site-verification=XdrHaLAwjDVvq81xMWHGRSeeIICpY2BkEqEaE7jemSk`
TXT	`v=spf1 exists:%{l}.%{ir}.%{d}.spf.prodmarc.com ~all`
TXT	`THeEpLEEDrqhfel6`
TXT	`_uxzjf2xgpi29bdl1m7zmypq10u9qv53`
SOA	`ns1-05.azure-dns.com`vinod@kumar.bekaert.com 2023-01-19 #0

`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=1778310776

Same first word

bridon-bekaert.com

bridon-bekaert.group

DNS History

8 records (6 active, 2 former)

○NSa3.uberns.com2017-01-05 → 2018-07-07 · 4 obs

● 2017-01-05 01:02:14
● 2018-07-07 21:40:32
○ 2026-03-30 11:49:48
○ 2026-05-09 07:32:58

○NSb3.uberns.com2017-01-05 → 2018-07-07 · 4 obs

● 2017-01-05 01:02:14
● 2018-07-07 21:40:32
○ 2026-03-30 11:49:48
○ 2026-05-09 07:32:58

●NSns1-05.azure-dns.com2026-03-30 → 2026-05-09 · 3 obs

○ 2018-07-07 21:40:32
● 2026-03-30 11:49:48
● 2026-05-09 07:32:58

●NSns2-05.azure-dns.net2026-03-30 → 2026-05-09 · 3 obs

○ 2018-07-07 21:40:32
● 2026-03-30 11:49:48
● 2026-05-09 07:32:58

●NSns3-05.azure-dns.org2026-03-30 → 2026-05-09 · 3 obs

○ 2018-07-07 21:40:32
● 2026-03-30 11:49:48
● 2026-05-09 07:32:58

●NSns4-05.azure-dns.info2026-03-30 → 2026-05-09 · 3 obs

○ 2018-07-07 21:40:32
● 2026-03-30 11:49:48
● 2026-05-09 07:32:58

●MXbridonbekaert-com01e.mail.protection.outlook.com2017-01-05 → 2026-05-09 · 2 obs

● 2017-01-05 01:02:14
● 2026-05-09 07:32:58

●A20.76.227.1092026-03-30 → 2026-05-09 · 2 obs

● 2026-03-30 11:49:48
● 2026-05-09 07:32:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, e.gtld-servers.net, c.gtld-servers.net, b.gtld-servers.net...	-
bridon-bekaert.com	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 bridon-bekaert.com (unsigned zone)

⏱️ Timing

Total: 164ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.76.227.109`
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
MX	1	`bridonbekaert-com01e.mail.protection.out`
TXT	6	`MS=ms65380278, MS=ms62873117...`
SOA	1	`ns1-05.azure-dns.com vinod.kumar.bekaert`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-05.azure-dns.com, ns1-05.azure-dns.com)

Analysis

IP Addresses

bridon-bekaert.com points to a single IP: 20.76.227.109.

Other host names such as bekaert.com and bekaert.tv share IP numbers with bridon-bekaert.com.

Name Servers

bridon-bekaert.com's delegation is handled by four name servers: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

bridon-bekaert.com partially shares name servers with other domains; examples include nssales.com, pfister-rechtsanwaelte.ch, bingads.com.pt, setup-msn.us and insurechem.com.

Host names with two IPs:

ns1-05.azure-dns.com points to 2603:1061:0:700::5 and 13.107.236.5

ns4-05.azure-dns.info points to 2620:1ec:bda:700::5 and 208.84.5.5

ns2-05.azure-dns.net points to 2620:1ec:8ec:700::5 and 150.171.21.5

ns3-05.azure-dns.org points to 2a01:111:4000:700::5 and 204.14.183.5

Mail Servers

bridon-bekaert.com is handled by a single mail server, bridonbekaert-com01e.mail.protection.outlook.com.

Hostname bridonbekaert-com01e.mail.protection.outlook.com points to eight IP numbers: 2a01:111:f403:ca04::2, 2a01:111:f403:ca04::7, 2a01:111:f403:ca04::d, 2a01:111:f403:ca09::d, 52.101.68.3, 52.101.73.4, 52.101.73.24 and 52.101.73.153.

bridon-bekaert.com - robtex.com