`mid-belgium.com`

DNSSEC	⚠️ Not signed
A	2a00:17d8:200::321^{🇩🇪 ROUTING2a00:17d8::/32 routing.net}
A	213.160.71.26^{🇩🇪 ROUTING213.160.71.0/24 routing.net}
NS	`ns1.routing.net` ⭐
		A	2a03:2900:3:1::2^{🇩🇪 AS488232a03:2900::/32}
			PTR	`ns1.routing.net`
		A	134.0.30.178^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`ns1.routing.net`
NS	`ns2.routing.net`
		A	2001:4d8f:2::2^{🇩🇪 ROUTING-ANYCAST2001:4d8f::/32}
			PTR	`ns2.routing.net`
		A	194.50.113.2^{🇩🇪 ROUTING-ANYCAST194.50.113.0/24 vollmarnet-anycast-route}
			PTR	`ns2.routing.net`
NS	`ns3.routing.net`
		A	2a03:2902:3:1::2^{🇩🇪 ACCELERATED-IT2a03:2902::/32 IP-Routing by firstcolo}
			PTR	`ns3.routing.net`
		A	194.126.196.2^{🇩🇪 ACCELERATED-IT194.126.196.0/24 IP-Routing by Accelerated IT Services GmbH}
			PTR	`ns3.routing.net`
MX	`mx01.routing.net` ⭐
		A	2a03:2900:1:a::13^{🇩🇪 AS488232a03:2900::/32}
			PTR	`mx01.routing.net`
		A	2a03:2900:1:a::14^{🇩🇪 AS488232a03:2900::/32}
			PTR	`mx01.routing.net`
		A	134.0.28.13^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx01.routing.net`
		A	134.0.28.14^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx01.routing.net`
MX	`mx02.routing.net` ⭐
		A	2a03:2900:1:a::15^{🇩🇪 AS488232a03:2900::/32}
		A	2a03:2900:1:a::16^{🇩🇪 AS488232a03:2900::/32}
		A	134.0.30.163^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx02.routing.net`
		A	134.0.30.164^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx02.routing.net`
MX	`mx03.routing.net` ⭐
		A	2a03:2900:1:a::17^{🇩🇪 AS488232a03:2900::/32}
			PTR	`mx03.routing.net`
		A	2a03:2900:1:a::18^{🇩🇪 AS488232a03:2900::/32}
			PTR	`mx03.routing.net`
		A	2a03:2900:1:a::19^{🇩🇪 AS488232a03:2900::/32}
			PTR	`mx03.routing.net`
		A	134.0.30.165^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx03.routing.net`
		A	134.0.30.166^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx03.routing.net`
		A	134.0.30.167^{🇩🇪 AS48823134.0.24.0/21}
			PTR	`mx03.routing.net`
MX	`mxbackup.routing.net`⁽²⁰⁾
		A	2a03:2902:4:1::a^{🇩🇪 ACCELERATED-IT2a03:2902::/32 IP-Routing by firstcolo}
			PTR	`mxbackup1.routing.net`
		A	2a03:2902:4:1::b^{🇩🇪 ACCELERATED-IT2a03:2902::/32 IP-Routing by firstcolo}
			PTR	`mxbackup2.routing.net`
		A	194.126.196.21^{🇩🇪 ACCELERATED-IT194.126.196.0/24 IP-Routing by Accelerated IT Services GmbH}
			PTR	`mxbackup1.routing.net`
		A	194.126.196.22^{🇩🇪 ACCELERATED-IT194.126.196.0/24 IP-Routing by Accelerated IT Services GmbH}
			PTR	`mxbackup2.routing.net`
SOA	`ns1.routing.net`hostmaster@routing.net 2026-02-15 #3

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

📈 Tranco rank: #413,821

Subdomains

pro.mid-belgium.com

Same first word

mid-belgium.com

DNS History

17 records (9 active, 8 former)

○NSb.ns.netim.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○NScloud3.netim.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

●NSns1.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●NSns2.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●NSns3.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●MXmx01.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●MXmx02.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●MXmx03.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●MXmxbackup.routing.net2026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

○MXmxl1-cloud.spamora.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○MXmxp1-cloud.spamora.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○MXmxv1-cloud.spamora.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○MXmxv2-cloud.spamora.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○MXmxv3-cloud.spamora.net2015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

○A185.26.106.312015-08-15 → 2017-09-25 · 4 obs

● 2015-08-15 00:01:44
● 2017-09-25 15:20:46
○ 2026-02-26 01:26:22
○ 2026-04-14 03:52:10

●A213.160.71.262026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

●A2a00:17d8:200::3212026-02-26 → 2026-04-14 · 3 obs

○ 2017-09-25 15:20:46
● 2026-02-26 01:26:22
● 2026-04-14 03:52:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
mid-belgium.com	ns2.routing.net, ns1.routing.net, ns3.routing.net	-

✅ Authoritative Response

Server:194.126.196.2

NS records: ns2.routing.net, ns1.routing.net, ns3.routing.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mid-belgium.com (unsigned zone)

⏱️ Timing

Total: 625ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`213.160.71.26`
AAAA	1	`2a00:17d8:200::321`
NS	3	`ns2.routing.net, ns3.routing.net...`
MX	4	`mx02.routing.net (pri: 10), mx03.routing.net (pri: 10)...`
SOA	1	`ns1.routing.net hostmaster.routing.net`

Analysis

Hierarchy

mid-belgium.com is the parent of pro.mid-belgium.com.

IP Addresses

The entity mid-belgium.com points to two IP numbers: 2a00:17d8:200::321 and 213.160.71.26.

For instance, other host names englanderline.ru, www.cotcotcot-apps.com, levasseur.eu, anne-dufetel.eu and anemon.fr share IP numbers with mid-belgium.com.

Name Servers

The delegation for mid-belgium.com is handled by three name servers: ns1.routing.net, ns2.routing.net and ns3.routing.net.

mid-belgium.com shares name servers with other domains at least partially, for example pembeoyun.com, calore.de, berit-salchow.de, thobaben.de and bab-i-care.de.

These name servers are commonly used with ns1.hosting.de, ns2.hosting.de and ns3.hosting.de.

Host names with two IPs:

ns1.routing.net points to 2a03:2900:3:1::2 and 134.0.30.178

ns2.routing.net points to 2001:4d8f:2::2 and 194.50.113.2

ns3.routing.net points to 2a03:2902:3:1::2 and 194.126.196.2

Mail Servers

mid-belgium.com is handled by four mail servers: mx01.routing.net, mx02.routing.net, mx03.routing.net and mxbackup.routing.net.

mid-belgium.com shares mail servers with other domains at least partially; for instance abk.archi, lbv-landshut.de, maschinensucher.ch, colingo.eu and praxis-huang.de.

Six IP numbers: mx03.routing.net points to 2a03:2900:1:a::17, 2a03:2900:1:a::18, 2a03:2900:1:a::19, 134.0.30.165, 134.0.30.166 and 134.0.30.167.

Four IP numbers: mx01.routing.net points to 2a03:2900:1:a::13, 2a03:2900:1:a::14, 134.0.28.13 and 134.0.28.14. mx02.routing.net points to 2a03:2900:1:a::15, 2a03:2900:1:a::16, 134.0.30.163 and 134.0.30.164. mxbackup.routing.net points to 2a03:2902:4:1::a, 2a03:2902:4:1::b, 194.126.196.21 and 194.126.196.22.

mid-belgium.com - robtex.com

mid-belgium.com

com

Subdomains

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Hierarchy

IP Addresses

Name Servers

Mail Servers

`mid-belgium.com`

`com`