letscom.be - dns.ninja

`letscom.be`

DNSSEC	⚠️ Not signed
A	2a00:17d8:200::311^{🇩🇪 ROUTING2a00:17d8::/32 routing.net}
A	213.160.71.18^{🇩🇪 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`
TXT	`v=spf1 include:spf.routing.net ip4:185.26.104.0/22 ~all`
SOA	`ns1.routing.net`hostmaster@routing.net 2026-06-11 #3

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

Subdomains

www.letscom.be

Same first word

letscom.com

letscom.com.br

letscom.com.cn

letscom.be

letscom.fr

letscom.it

Similar names

motcles.fr

scomtel.vn

telosmc.com

mtecsol.com

cosmelt.com

mstelco.org

telscom.co.kr

scmotel.com

telcoms.com

stelcom.com

comtels.de

comtels.net

stelcom.cn

stelcom.ru

telscom.ch

lcseotm.com

cmtelos.com

comtels.ru

comlets.com

elmscot.co.uk

DNS History

19 records (9 active, 10 former)

○NSb.ns.netim.net2015-06-15 → 2021-05-26 · 4 obs

● 2015-06-15 02:44:24
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○NScloud19.netim.net2021-05-26 → 2021-05-26 · 4 obs

○ 2018-05-24 08:28:34
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○NScloud4.netim.net2015-06-15 → 2018-05-24 · 4 obs

● 2015-06-15 02:44:24
● 2018-05-24 08:28:34
○ 2021-05-26 05:20:00
○ 2026-06-15 22:49:42

●NSns1.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●NSns2.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●NSns3.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●MXmx01.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●MXmx02.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●MXmx03.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●MXmxbackup.routing.net2026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

○MXmxl1-cloud.spamora.net2015-06-15 → 2021-05-26 · 4 obs

● 2015-06-15 02:44:24
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○MXmxp1-cloud.spamora.net2015-06-15 → 2021-05-26 · 4 obs

● 2015-06-15 02:44:24
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○MXmxv1-cloud.spamora.net2015-06-15 → 2021-05-26 · 4 obs

● 2015-06-15 02:44:24
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○MXmxv2-cloud.spamora.net2015-06-15 → 2021-05-26 · 4 obs

● 2015-06-15 02:44:24
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○MXmxv3-cloud.spamora.net2015-06-15 → 2018-05-24 · 4 obs

● 2015-06-15 02:44:24
● 2018-05-24 08:28:34
○ 2021-05-26 05:20:00
○ 2026-06-15 22:49:42

○A185.26.106.1652021-05-26 → 2021-05-26 · 4 obs

○ 2018-05-24 08:28:34
● 2021-05-26 05:20:00
○ 2026-02-23 03:17:32
○ 2026-06-15 22:49:42

○A185.26.106.412015-06-15 → 2018-05-24 · 4 obs

● 2015-06-15 02:44:24
● 2018-05-24 08:28:34
○ 2021-05-26 05:20:00
○ 2026-06-15 22:49:42

●A213.160.71.182026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

●A2a00:17d8:200::3112026-02-23 → 2026-06-15 · 3 obs

○ 2021-05-26 05:20:00
● 2026-02-23 03:17:32
● 2026-06-15 22:49:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
be	a.nsset.be, c.nsset.be, b.nsset.be, d.nsset.be...	-
letscom.be	ns1.routing.net, ns2.routing.net, ns3.routing.net	-

✅ Authoritative Response

Server:194.50.113.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for letscom.be (unsigned zone)

⏱️ Timing

Total: 671ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`213.160.71.18`
AAAA	1	`2a00:17d8:200::311`
NS	3	`ns1.routing.net, ns2.routing.net...`
MX	4	`mx02.routing.net (pri: 10), mxbackup.routing.net (pri: 20)...`
TXT	1	`v=spf1 include:spf.routing.net ip4:185.2`
SOA	1	`ns1.routing.net hostmaster.routing.net`

Analysis

Hierarchy

www.letscom.be is a subdomain of letscom.be.

IP Addresses

letscom.be points to the IP addresses 213.160.71.18 and 2a00:17d8:200::311

Two other host names, along with iconemali.com, hansford.org and flingfilmfestival.co.uk, also share IP numbers with letscom.be.

Name Servers

The authoritative name servers for letscom.be are ns1.routing.net, ns2.routing.net and ns3.routing.net — three in total.

The name servers of letscom.be overlap at least partially with those of other domains — among them architekturbuero-wellmann.de, my-etgroup.com, schnurz.de and two more.

ns1.routing.net, ns2.routing.net and ns3.routing.net all resolve to exactly two IP numbers apiece: ns1.routing.net → 134.0.30.178 and 2a03:2900:3:1::2; ns2.routing.net → 194.50.113.2 and 2001:4d8f:2::2; ns3.routing.net → 194.126.196.2 and 2a03:2902:3:1::2.

Mail Servers

The four mail servers for letscom.be are mx01.routing.net, mx02.routing.net, mx03.routing.net and mxbackup.routing.net.

There is at least a partial MX overlap between letscom.be and other domains, including nsu-team-moehnsen.de, digitalisierungskompass.info, stb-schmitt-nsu.de and two others.

mx01.hosting.de, mx02.hosting.de, mxbackup.hosting.de and mx03.hosting.de are mail servers that frequently appear together with these mail servers.

DNS names with 6 IP addresses:

Hostname mx03.routing.net directs to 134.0.30.165, 134.0.30.166 and 134.0.30.167 along with 3 other IP addresses.

Host names that resolve to four IP numbers:

mx01.routing.net resolves to 134.0.28.13, 134.0.28.14, 2a03:2900:1:a::13 and 2a03:2900:1:a::14.

mx02.routing.net resolves to 134.0.30.163, 134.0.30.164, 2a03:2900:1:a::15 and 2a03:2900:1:a::16.

mxbackup.routing.net resolves to 194.126.196.21, 194.126.196.22, 2a03:2902:4:1::a and 2a03:2902:4:1::b.