sumocode.be - dns.ninja

`sumocode.be`

DNSSEC	⚠️ Not signed
NS	`ns.nscluster.es` ⚠️ Not in zone NS records
		A	2001:41d0:304:200::ac2b^{🇫🇷 OVH2001:41d0::/32 IPv6}
			PTR	`vps-ba4dea60.vps.ovh.net`
		A	217.182.119.186^{🇫🇷 OVH217.182.0.0/16}
			PTR	`ns.nscluster.fr`
NS	`ns.nscluster.eu` ⚠️ Not in zone NS records
		A	2a03:b0c0:2:d0::79d:4001^{🇳🇱 DIGITALOCEAN2a03:b0c0:2::/48 DigitalOcean}
			PTR	`d1.bn.md`
		A	188.166.70.123^{🇳🇱 DIGITALOCEAN188.166.64.0/18 DigitalOcean}
			PTR	`d1.bn.md`
NS	`ns.nscluster.no` ⚠️ Not in zone NS records
		A	2607:5300:205:200::7f7d^{🇨🇦 OVH2607:5300::/32 Hosting route}
			PTR	`vps-ca2cd8d6.vps.ovh.ca`
		A	192.99.83.158^{🇨🇦 OVH192.99.0.0/16 Hosting route}
			PTR	`ns.nscluster.sk`
NS	`ns.nscluster.uk` ⚠️ Not in zone NS records
		A	2600:9000:a51d:1c55:a63e:443d:ec03:df01^{🇺🇸 Amazon2600:9000:a500::/43}
			PTR	`abe11aa245084d8f0.dualstack.awsglobalaccelerator.com`
		A	13.248.156.209^{🇺🇸 Amazon13.248.144.0/20}
			PTR	`abe11aa245084d8f0.awsglobalaccelerator.com`
NS	`ns.nscluster.us` ⚠️ Not in zone NS records
		A	2605:6400:10:5c1:84ee:85fb:b2b:8b37^{🇺🇸 FRANTECH2605:6400:10::/48}
			PTR	`ns.nscluster.us`
		A	198.251.86.156^{🇺🇸 FRANTECH198.251.86.0/24 More specific route.}
			PTR	`ns.anycastcluster.com`

`be`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.nsset.be` ⭐
	NS	`b.nsset.be`
	NS	`c.nsset.be`
	NS	`d.nsset.be`
	NS	`y.nsset.be`
	NS	`z.nsset.be`
	SOA	`a.nsset.be`be-hostmaster@dnsbelgium.be serial=1028251920

Same first word

sumocode.be

sumocode.com

Similar names

DNS History

19 records (5 active, 14 former)

●NSns.nscluster.es2020-02-22 → 2026-07-03 · 3 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
● 2026-07-03 18:37:58

●NSns.nscluster.eu2020-02-22 → 2026-07-03 · 3 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
● 2026-07-03 18:37:58

●NSns.nscluster.no2020-02-22 → 2026-07-03 · 3 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
● 2026-07-03 18:37:58

●NSns.nscluster.uk2020-02-22 → 2026-07-03 · 3 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
● 2026-07-03 18:37:58

●NSns.nscluster.us2020-02-22 → 2026-07-03 · 3 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
● 2026-07-03 18:37:58

○NSns1.crsolutions.be2015-07-15 → 2016-12-02 · 4 obs

● 2015-07-15 01:10:22
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

○NSns1.hostbots.be2015-07-15 → 2016-12-02 · 4 obs

● 2015-07-15 01:10:22
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

○NSns2.crsolutions.be2015-07-15 → 2016-12-02 · 4 obs

● 2015-07-15 01:10:22
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

○MXmail.crsolutions.be2015-07-15 → 2016-04-22 · 4 obs

● 2015-07-15 01:10:22
● 2016-04-22 17:26:46
○ 2016-12-02 11:30:48
○ 2026-07-03 18:37:58

○MXmail02.crsolutions.be2015-07-15 → 2016-04-22 · 4 obs

● 2015-07-15 01:10:22
● 2016-04-22 17:26:46
○ 2016-12-02 11:30:48
○ 2026-07-03 18:37:58

○MXmx.fallback.hostbots.be2016-12-02 → 2016-12-02 · 4 obs

○ 2016-04-22 17:26:46
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

○MXmx.hostbots.be2016-12-02 → 2016-12-02 · 4 obs

○ 2016-04-22 17:26:46
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

○MXmx.nameweb.biz2026-02-22 → 2026-07-03 · 9 obs

○ 2020-02-22 11:21:46
● 2026-02-22 16:30:28
● 2026-05-31 12:48:52
○ 2026-06-10 14:37:26
● 2026-06-22 07:10:58
○ 2026-06-22 08:52:54
● 2026-07-03 00:53:30
○ 2026-07-03 14:49:02
○ 2026-07-03 18:37:58

○MXsmtp.nameweb.biz2020-02-22 → 2020-02-22 · 4 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
○ 2026-02-22 16:30:28
○ 2026-07-03 18:37:58

○A2001:41d0:305:2100::27062020-02-22 → 2020-02-22 · 4 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
○ 2026-02-22 16:30:28
○ 2026-07-03 18:37:58

○A2600:9000:a412:ebed:3a5d:d6ff:4310:3f0f2026-02-22 → 2026-07-03 · 9 obs

○A51.38.231.822020-02-22 → 2020-02-22 · 4 obs

○ 2016-12-02 11:30:48
● 2020-02-22 11:21:46
○ 2026-02-22 16:30:28
○ 2026-07-03 18:37:58

○A76.223.25.502026-02-22 → 2026-07-03 · 9 obs

○A88.151.246.232015-07-15 → 2016-12-02 · 4 obs

● 2015-07-15 01:10:22
● 2016-12-02 11:30:48
○ 2020-02-22 11:21:46
○ 2026-07-03 18:37:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
be	y.nsset.be, d.nsset.be, a.nsset.be, c.nsset.be...	-
sumocode.be	ns.nscluster.eu, ns.nscluster.es, ns.nscluster.no, ns.nscluster.uk...	-

✅ Authoritative Response

Server:217.182.119.186

NS records: ns.nscluster.eu, ns.nscluster.es, ns.nscluster.no, ns.nscluster.uk, ns.nscluster.us

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sumocode.be (unsigned zone)

⏱️ Timing

Total: 2479ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`76.223.25.50`
AAAA	1	`2600:9000:a412:ebed:3a5d:d6ff:4310:3f0f`
NS	5	`ns.nscluster.es, ns.nscluster.us...`
MX	1	`mx.nameweb.biz (pri: 10)`
TXT	1	`v=spf1 include:_spf.nameweb.biz -all`
SOA	1	`ns.nscluster.eu hostmaster.nscluster.eu`

Analysis

Name Servers

sumocode.be has five name servers, which are ns.nscluster.es, ns.nscluster.eu, ns.nscluster.no and two others.

sumocode.be shares at least some of its name servers with other domains, including huisartsenpraktijkgerrits.nl, codic.es, blind.be and two others.

These name servers are frequently seen alongside ns.nscluster.us, ns.nscluster.uk, ns.bnamed.us and 7 other name servers.

Hostnames that resolve to two IP addresses:

ns.nscluster.es directs traffic to 217.182.119.186 and 2001:41d0:304:200::ac2b.

ns.nscluster.eu directs traffic to 188.166.70.123 and 2a03:b0c0:2:d0::79d:4001.

ns.nscluster.no directs traffic to 192.99.83.158 and 2607:5300:205:200::7f7d.

ns.nscluster.uk directs traffic to 13.248.156.209 and 2600:9000:a51d:1c55:a63e:443d:ec03:df01.

ns.nscluster.us directs traffic to 198.251.86.156 and 2605:6400:10:5c1:84ee:85fb:b2b:8b37.