`resolver1.win.be`

DNSSEC	⚠️ Not signed
A	2a01:5a00:3000::10^{🇧🇪 WIN2a01:5a00::/32 v6 Block}
		PTR	`resolver1.win.be`
A	212.166.2.10^{🇧🇪 WIN212.166.0.0/18 Win}

`win.be`

	DNSSEC	⚠️ Not signed
	A	212.166.9.98^{🇧🇪 WIN212.166.0.0/18 Win}
	NS	`nameserver1.win.be` ⭐
	NS	`nameserver2.win.be`
	MX	`psyche.win.be` ⭐
	MX	`mailq.win.be`⁽⁵⁰⁾
	TXT	`MS=ms61339139`
	TXT	`druide-validation-domaine=ede1b3079da045e64d5414cb1014aee0`
	TXT	`v=spf1 mx ip4:212.166.2.0/24 -all`
	TXT	`j2ofvvufgigbjoib8lbiralf3d`
	TXT	`_tf9v7scflcr3yeljljk8er17d5luv76`
	SOA	`nameserver1.win.be`postmaster@win.be 2026-04-11 #0

WOT: SAFE (60/100)
WOT: UNKNOWN (61/100)
📈 Tranco rank: #118,790

PTR for

0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.0.0.a.5.1.0.a.2.ip6.arpa

10.2.166.212.in-addr.arpa

Previously NS for

nsi-sa.be

Same first word

resolver1.fm

resolver1.net

DNS History

2 records (2 active, 0 former)

●A212.166.2.102015-07-04 → 2026-04-14 · 2 obs

● 2015-07-04 15:42:58
● 2026-04-14 22:54:10

●A2a01:5a00:3000::102015-07-04 → 2026-04-14 · 2 obs

● 2015-07-04 15:42:58
● 2026-04-14 22:54:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
be	y.nsset.be, c.nsset.be, b.nsset.be, a.nsset.be...	-
win.be	nameserver2.win.be, nameserver1.win.be	3 records

✅ Authoritative Response

Server:212.166.3.108

NS records: nameserver2.win.be, nameserver1.win.be

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for win.be (unsigned zone)

⏱️ Timing

Total: 211ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`212.166.2.10`
AAAA	1	`2a01:5a00:3000::10`

📌 Glue Records Collected

Total: 3

In-bailiwick: 3 (nameserver1.win.be, nameserver2.win.be, nameserver1.win.be)

Analysis

IP Addresses

resolver1.win.be points to two IP numbers: 2a01:5a00:3000::10 and 212.166.2.10.

Other host names, for instance ns1.win.be, share IP numbers with resolver1.win.be.

resolver1.win.be - robtex.com

resolver1.win.be

win.be