🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`odersteig.de`

DNSSEC	⚠️ Not signed
A	2001:bf0:c000:a::2:132^{🇩🇪 IN-BERLIN-AS2001:bf0:c000::/35 Individual Network Berlin e.V.}
		PTR	`virtualhost.in-berlin.de`
A	217.197.80.132^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
NS	`ns1.in-berlin.de` ⭐
		A	2001:67c:1400:1010::42:26^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`okapi.in-berlin.de`
		A	192.109.42.26^{🇩🇪 IN-BERLIN-AS192.109.42.0/24 Individual Network Berlin e.V.}
			PTR	`okapi.in-berlin.de`
NS	`ns2.in-berlin.de`
		A	2001:67c:1400:1010::34^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`letschwe.in-berlin.de`
		A	217.197.80.34^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
			PTR	`letschwe.in-berlin.de`
NS	`ns3.in-berlin.de`
		A	2001:67c:1403:1010::4^{🇩🇪 IN-BERLIN-AS2001:67c:1403::/48 Individual Network Berlin e.V.}
			PTR	`vechur.in-berlin.de`
		A	193.29.188.4^{🇩🇪 IN-BERLIN-AS193.29.188.0/24 Individual Network Berlin e.V.}
			PTR	`vechur.in-berlin.de`
NS	`ns4.in-berlin.de`
		A	130.133.8.36^{🇩🇪 DFN130.133.0.0/16 FUB}
			PTR	`methan3.in-berlin.de`
MX	`mx1.in-berlin.de` ⭐
		A	2001:67c:1400:1010::23^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
		A	2001:67c:1400:1010::42:28^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	2001:67c:1403:1010::9^{🇩🇪 IN-BERLIN-AS2001:67c:1403::/48 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	130.133.8.35^{🇩🇪 DFN130.133.0.0/16 FUB}
			PTR	`methan2.in-berlin.de`
		A	192.109.42.28^{🇩🇪 IN-BERLIN-AS192.109.42.0/24 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	193.29.188.9^{🇩🇪 IN-BERLIN-AS193.29.188.0/24 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	217.197.80.23^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
MX	`mx2.in-berlin.de`⁽²⁰⁾
		A	2001:67c:1400:1010::23^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
		A	2001:67c:1400:1010::42:28^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	2001:67c:1403:1010::9^{🇩🇪 IN-BERLIN-AS2001:67c:1403::/48 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	130.133.8.35^{🇩🇪 DFN130.133.0.0/16 FUB}
			PTR	`methan2.in-berlin.de`
		A	192.109.42.28^{🇩🇪 IN-BERLIN-AS192.109.42.0/24 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	193.29.188.9^{🇩🇪 IN-BERLIN-AS193.29.188.0/24 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	217.197.80.23^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
MX	`mx3.in-berlin.de`⁽³⁰⁾
		A	2001:67c:1400:1010::23^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
		A	2001:67c:1400:1010::42:28^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	2001:67c:1403:1010::9^{🇩🇪 IN-BERLIN-AS2001:67c:1403::/48 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	130.133.8.35^{🇩🇪 DFN130.133.0.0/16 FUB}
			PTR	`methan2.in-berlin.de`
		A	192.109.42.28^{🇩🇪 IN-BERLIN-AS192.109.42.0/24 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	193.29.188.9^{🇩🇪 IN-BERLIN-AS193.29.188.0/24 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	217.197.80.23^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
MX	`mx4.in-berlin.de`⁽⁴⁰⁾
		A	2001:67c:1400:1010::23^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
		A	2001:67c:1400:1010::42:28^{🇩🇪 IN-BERLIN-AS2001:67c:1400::/45 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	2001:67c:1403:1010::9^{🇩🇪 IN-BERLIN-AS2001:67c:1403::/48 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	130.133.8.35^{🇩🇪 DFN130.133.0.0/16 FUB}
			PTR	`methan2.in-berlin.de`
		A	192.109.42.28^{🇩🇪 IN-BERLIN-AS192.109.42.0/24 Individual Network Berlin e.V.}
			PTR	`tamarau.in-berlin.de`
		A	193.29.188.9^{🇩🇪 IN-BERLIN-AS193.29.188.0/24 Individual Network Berlin e.V.}
			PTR	`bubalus.in-berlin.de`
		A	217.197.80.23^{🇩🇪 IN-BERLIN-AS217.197.80.0/20 Individual Network Berlin e.V.}
			PTR	`mindoro.in-berlin.de`
TXT	`v=spf1 include:_spf.in-berlin.de ~all`
SOA	`ns1.in-berlin.de`domain@in-berlin.de 2022-03-19 #13

`de`

	DNSSEC	🔒 Signed (DS record present)
	NS	`f.nic.de` ⭐
	NS	`a.nic.de`
	NS	`l.de.net` ⚠️ Not in parent delegation
	NS	`n.de.net` ⚠️ Not in parent delegation
	NS	`s.de.net` ⚠️ Not in parent delegation
	NS	`z.nic.de`
	SOA	`f.nic.de`dns-operations@denic.de serial=1793969475

Same first word

odersteig.de

Similar names

Previous names

Next names

DNS History

10 records (10 active, 0 former)

●NSns1.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●NSns2.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●NSns3.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●NSns4.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●MXmx1.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●MXmx2.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●MXmx3.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●MXmx4.in-berlin.de2026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●A2001:bf0:c000:a::2:1322026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

●A217.197.80.1322026-10-17 → 2026-11-06 · 2 obs

● 2026-10-17 04:59:04
● 2026-11-06 13:17:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	f.nic.de, a.nic.de, z.nic.de	-
odersteig.de	ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de	7 records

✅ Authoritative Response

Server:192.109.42.26

NS records: ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 478ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.197.80.132`
AAAA	1	`2001:bf0:c000:a::2:132`
NS	4	`ns1.in-berlin.de, ns4.in-berlin.de...`
MX	4	`mx1.in-berlin.de (pri: 10), mx4.in-berlin.de (pri: 40)...`
TXT	1	`v=spf1 include:_spf.in-berlin.de ~all`
SOA	1	`ns1.in-berlin.de domain.in-berlin.de`

📌 Glue Records Collected

Total: 7

Out-of-bailiwick: 7 (ns1.in-berlin.de, ns1.in-berlin.de, ns2.in-berlin.de...)

Analysis

IP Addresses

odersteig.de resolves to the IP addresses 217.197.80.132 and 2001:bf0:c000:a::2:132

Two other host names, along with toni.in-berlin.de, mporemski.in-berlin.de and neels.in-berlin.de, also share IP numbers with odersteig.de.

Name Servers

The NS records for odersteig.de point to four name servers: ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de and ns4.in-berlin.de.

odersteig.de partially shares its NS delegation with several other domains, including wem-gehoert-moabit.de, hoschmi.net, tiesel.berlin and two others.

These name servers often co-occur with the name servers hmo.in-vpn.de.

Host names that have two IP addresses:

ns1.in-berlin.de points to 192.109.42.26 and 2001:67c:1400:1010::42:26.

ns2.in-berlin.de points to 217.197.80.34 and 2001:67c:1400:1010::34.

ns3.in-berlin.de points to 193.29.188.4 and 2001:67c:1403:1010::4.

Host names that point to one IP address:

ns4.in-berlin.de points to 130.133.8.36.

Mail Servers

odersteig.de has four mail servers: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

There is at least a partial MX overlap between odersteig.de and other domains, including jasmin-touati.de, goepel.tv, code-fu.de and two others.

DNS names with 7 IP addresses:

mx1.in-berlin.de resolves to 130.133.8.35, 192.109.42.28, 193.29.188.9 and 4 other IP addresses.

mx2.in-berlin.de resolves to 130.133.8.35, 192.109.42.28, 193.29.188.9 and 4 other IP addresses.

mx3.in-berlin.de resolves to 130.133.8.35, 192.109.42.28, 193.29.188.9 and 4 other IP addresses.

mx4.in-berlin.de resolves to 130.133.8.35, 192.109.42.28, 193.29.188.9 and 4 other IP addresses.

These host names all point to 2001:67c:1400:1010::23: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 2001:67c:1400:1010::42:28: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 2001:67c:1403:1010::9: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 130.133.8.35: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 192.109.42.28: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 193.29.188.9: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.

These host names all point to 217.197.80.23: mx1.in-berlin.de, mx2.in-berlin.de, mx3.in-berlin.de and mx4.in-berlin.de.